[#502] experimental test harness using a single container#508
[#502] experimental test harness using a single container#508d-w-moore wants to merge 13 commits intoirods:mainfrom
Conversation
korydraughn
left a comment
korydraughn
left a comment
There was a problem hiding this comment.
Please explain what this PR does?
Are there plans to leverage the consortium test hook and the testing environment?
Seems this PR is part of the 2.0.0 milestone after all, so maybe we try to leverage those somewhere in a later release? |
d-w-moore
force-pushed
the
502.m
branch
2 times, most recently
from
fedbf73 to
858374b
Compare
|
Rebasing atop 518.m , and I may leave it that way to save time. After un-drafting, we'll decide if #518 gets its own pull request |
d-w-moore
force-pushed
the
502.m
branch
3 times, most recently
from
8109fec to
00e9cc2
Compare
|
let's not mention 281 in the first part of the commit lines, we can reference it in the body if helpful/needed. |
Yes, will correct that. |
d-w-moore
force-pushed
the
502.m
branch
2 times, most recently
from
2d19eac to
bc07343
Compare
d-w-moore
force-pushed
the
502.m
branch
2 times, most recently
from
65a4bee to
a9c2d75
Compare
d-w-moore
changed the title
Basically there are a bunch of tests which demand unique setup or otherwise unique running conditions. This PR is part of a plan to run each of those - automatically is the hope. Inclusion is the idea, preventing regression. And it's easy to set up conditions for such tests within a Dockerfile. |
d-w-moore
changed the title
|
SKIP_IINIT_FOR_PASSWORD documented (currently in 7d75ae9) |
d-w-moore
force-pushed
the
502.m
branch
2 times, most recently
from
7d75ae9 to
b4f6592
Compare
testuser universal for all containers login_auth*.py adjustments [__502] scriptdir [__502] patch for consistency in starting document SKIP_IINIT_FOR_PASSWORD "funcs" include file renamed to "test_support_functions" remove fail.sh to scripts dir
|
Once all the conversations above are resolved, my plan is to cancel this PR and integrate the changes herein (the addition of a single-docker-container test harness that is well suited for testing via BATS scripts and other test modules requiring custom setup) into a new Pull Request dealing with the wider goal of testing PRC under Github Actions. |
|
or you can just push the changes here - so the conversation is in one place? up to you. of course, link back here in any new PR so the archaeologists can find it. |
|
we can close this, as the work has been merged. |
|
@d-w-moore has stated that this PR is no longer needed. It is superseded by work for #772. Closing. |
3 participants
Automatic launch of specific test scripts in their own container.