-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
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
If a specific section is specified, actually two test runs are carried out #1394
Comments
I agree, that shouldn't happen by default. Is section "sa" failing? (basically, does it run into the same problem #1389 does?) |
No, section "sa" is not failing. (I saw issue #1389 before I opened this new issue and, at first sight, it seemed similar. But because "sa" was not failing I thought this would be something different.) |
Then this is a bug, the first run should provide all the information we need to avoid doing a second one. |
…ion is selected
fix #1394: avoid superfluous re-run when specific section is selected
Description
If I like a test in a specific section to be run, I can do this with this command:
./MyExe Test -c sa
Surprisingly, this causes two test runs:
Is there a reason for the second empty test run? In my application where the initialisation for the test case is lengthy this behaviour is inconvenient.
Steps to reproduce
Put some log output in the test case "Test" outside any sections.
The text was updated successfully, but these errors were encountered: