We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To reproduce:
Expected result: maintainers can review and merge several features in one go
Actual result: each new test has to change the line that prints 1..50, so they all conflict
1..50
We could perhaps make this better with code like this?
# in libtest-code.sh test_number=0 ok () { test_number=$(( test_number + 1 ) echo "ok $test_number - $*" } done_testing () { echo "1..$test_number" }
# in the test reticulate splines ok "can reticulate splines" ponder meaning of existence ok "implements basic philosophy" done_testing
with the TAP output ending up like this:
ok 1 - can reticulate splines ok 2 - implements basic philosophy 1..2
The text was updated successfully, but these errors were encountered:
(This is the equivalent of ok and done_testing in Perl's Test module, which is where TAP comes from.)
ok
done_testing
Sorry, something went wrong.
Fix MRs conflicting when they add unit tests
15c8b9c
Fixes containers#420 Signed-off-by: Jonathan Wright <[email protected]>
1cba871
Successfully merging a pull request may close this issue.
To reproduce:
Expected result: maintainers can review and merge several features in one go
Actual result: each new test has to change the line that prints
1..50
, so they all conflictWe could perhaps make this better with code like this?
with the TAP output ending up like this:
The text was updated successfully, but these errors were encountered: