In this scenario, expected behavior is this output:
Skipped test testFirst, status: 1
End test testFirst, status: 1
Skipped test testSecond, status: 1
End test testSecond, status: 1
However the actual output is:
Skipped test testFirst, status: 1
End test testFirst, status: 1
Skipped test testSecond, status: -1
End test testSecond, status: -1
Ie. even though the addSkippedTest() method gets called, the test status property (getStatus()) of this actual TestCase is not 1 (BaseTestRunner::STATUS_SKIPPED), but -1 (BaseTestRunner::STATUS_UNKNOWN), which seems unexpected and inconsistent.
The text was updated successfully, but these errors were encountered:
OndraM
added a commit
to lmc-eu/steward
that referenced
this issue
Nov 1, 2018
Hi,
we have a test method which is now being skipped using
markTestSkipped()
, and another test method which depends on this (now skipped) test:We utilize custom TestListeners, especially addSkippedTest and endTest methods.
In this scenario, expected behavior is this output:
However the actual output is:
Ie. even though the
addSkippedTest()
method gets called, the teststatus
property (getStatus()
) of this actualTestCase
is not1
(BaseTestRunner::STATUS_SKIPPED
), but-1
(BaseTestRunner::STATUS_UNKNOWN
), which seems unexpected and inconsistent.The text was updated successfully, but these errors were encountered: