Closed jean-andre-gauthier closed 9 months ago
@marcphilipp could you please double-check if the changes correspond to what you had in mind?
@jean-andre-gauthier @marcphilipp Your initiative and help is appreciated. Thanks! Regarding the test output: I also was wondering why the test suite was started twice. When you un-draft this PR, I will have a look at it right away.
Hi @mmews-n4 @marcphilipp, thanks for your comments.
The wrapping testSuiteStarted/Finished
in the tests is triggered by ParentRunner.run
for XtTestSetupTestMockup
. I've just double-checked, the behaviour hasn't changed there, these callbacks were already being called before my changes. They didn't show up in the tests though, because AbstractXtParentRunnerTest.TestRunSimulator
wasn't tracking them up until now. To make things more explicit, I have added the description to the event key in TestRunSimulator.testSuiteStarted/Finished
.
Please let me know if that looks fine to you?
Thanks again!
This PR replaces calls to
fireTestRunStarted/Finished
byfireTestSuiteStarted/Finished
inXtFileRunner
. According to the JUnit 4 docs,fireTestRunStarted/Finished
are not supposed to be invoked by custom runners, which should usefireTestSuiteStarted/Finished
instead.