Skip to content

Commit bbe8504

Browse files
pmarchinipmarchini
committed
test_runner: move --test-only diagnostic warning tests to separate file
1 parent 52d8766 commit bbe8504

11 files changed

+414
-679
lines changed

‎test/fixtures/test-runner/output/dot_reporter.snapshot

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
..XX...X..XXX.X.....
22
XXX.....X..X...X....
33
.....X...XXX.XX.....
4-
.XXXXXXX...XXXX.....
5-
..............X
4+
.XXXXXXX...XXXXX
65

76
Failed tests:
87

‎test/fixtures/test-runner/output/junit_reporter.snapshot

Lines changed: 9 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -504,38 +504,6 @@ should loosely deep-equal
504504
}
505505
</failure>
506506
</testcase>
507-
<testsuite name="should NOT print --test-only diagnostic warning - describe-only-false" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
508-
<testcase name="only false in describe" time="*" classname="test"/>
509-
</testsuite>
510-
<testsuite name="should NOT print --test-only diagnostic warning - it-only-false" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
511-
<testcase name="only false in the subtest" time="*" classname="test"/>
512-
</testsuite>
513-
<testsuite name="should NOT print --test-only diagnostic warning - no-only" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
514-
<testcase name="no only" time="*" classname="test"/>
515-
</testsuite>
516-
<testsuite name="should NOT print --test-only diagnostic warning - test-only-false" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
517-
<testcase name="only false in parent test" time="*" classname="test"/>
518-
</testsuite>
519-
<testsuite name="should NOT print --test-only diagnostic warning - t.test-only-false" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
520-
<testcase name="only false in subtest" time="*" classname="test"/>
521-
</testsuite>
522-
<testsuite name="should NOT print --test-only diagnostic warning - no-only" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
523-
<testcase name="no only" time="*" classname="test"/>
524-
</testsuite>
525-
<testsuite name="should print --test-only diagnostic warning - test-only-true" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
526-
<testcase name="only true in parent test" time="*" classname="test"/>
527-
</testsuite>
528-
<!-- 'only' and 'runOnly' require the &#45;&#45;test-only command-line option. -->
529-
<testsuite name="should print --test-only diagnostic warning - t.test-only-true" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
530-
<testcase name="only true in subtest" time="*" classname="test"/>
531-
<!-- 'only' and 'runOnly' require the &#45;&#45;test-only command-line option. -->
532-
</testsuite>
533-
<testsuite name="should print --test-only diagnostic warning - 2 levels of only" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
534-
<testsuite name="only true in parent test" time="*" disabled="0" errors="0" tests="1" failures="0" skipped="0" hostname="HOSTNAME">
535-
<testcase name="only true in subtest" time="*" classname="test"/>
536-
<!-- 'only' and 'runOnly' require the &#45;&#45;test-only command-line option. -->
537-
</testsuite>
538-
</testsuite>
539507
<testcase name="invalid subtest fail" time="*" classname="test" failure="test could not be started because its parent finished">
540508
<failure type="parentAlreadyFinished" message="test could not be started because its parent finished">
541509
Error [ERR_TEST_FAILURE]: test could not be started because its parent finished
@@ -546,16 +514,16 @@ Error [ERR_TEST_FAILURE]: test could not be started because its parent finished
546514
}
547515
</failure>
548516
</testcase>
549-
<!-- Error: Test "unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:73:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
550-
<!-- Error: Test "async unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:77:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from async unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
517+
<!-- Error: Test "unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:72:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
518+
<!-- Error: Test "async unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:76:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from async unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
551519
<!-- Error: A resource generated asynchronous activity after the test ended. This activity created the error "Error: uncaught from outside of a test" which triggered an uncaughtException event, caught by the test runner. -->
552-
<!-- Error: Test "immediate throw - passes but warns" at test/fixtures/test-runner/output/output.js:81:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from immediate throw fail" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
553-
<!-- Error: Test "immediate reject - passes but warns" at test/fixtures/test-runner/output/output.js:87:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from immediate reject fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
554-
<!-- Error: Test "callback called twice in different ticks" at test/fixtures/test-runner/output/output.js:252:1 generated asynchronous activity after the test ended. This activity created the error "Error [ERR_TEST_FAILURE]: callback invoked multiple times" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
555-
<!-- Error: Test "callback async throw after done" at test/fixtures/test-runner/output/output.js:270:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from callback async throw after done" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
556-
<!-- tests 92 -->
557-
<!-- suites 3 -->
558-
<!-- pass 51 -->
520+
<!-- Error: Test "immediate throw - passes but warns" at test/fixtures/test-runner/output/output.js:80:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from immediate throw fail" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
521+
<!-- Error: Test "immediate reject - passes but warns" at test/fixtures/test-runner/output/output.js:86:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from immediate reject fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
522+
<!-- Error: Test "callback called twice in different ticks" at test/fixtures/test-runner/output/output.js:251:1 generated asynchronous activity after the test ended. This activity created the error "Error [ERR_TEST_FAILURE]: callback invoked multiple times" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
523+
<!-- Error: Test "callback async throw after done" at test/fixtures/test-runner/output/output.js:269:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from callback async throw after done" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
524+
<!-- tests 76 -->
525+
<!-- suites 0 -->
526+
<!-- pass 35 -->
559527
<!-- fail 25 -->
560528
<!-- cancelled 3 -->
561529
<!-- skipped 9 -->

0 commit comments

Comments
 (0)