You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
Currently, it looks like the summary test results are calculated when test is submitted by the test framework or when test framework guess the test is completed (possibly, without sending test finished event) but actually the test might be not completed yet.
Suppose I have a test executor which doesn't execute test when it submitted, but collects all tests and executes all of them later.
There is total 2 test functions in 2 classes in the example. If run the tests the summary results are:
total tests 2
total success 2
total skipped 1
Why number of skipped tests is 1? Which test has been skipped? All tests have been successfully completed.
So, I propose to calculate the summary results after all tests in the run completed or at least when test finished event is sent.
The text was updated successfully, but these errors were encountered:
Currently, it looks like the summary test results are calculated when test is submitted by the test framework or when test framework guess the test is completed (possibly, without sending test finished event) but actually the test might be not completed yet.
Suppose I have a test executor which doesn't execute test when it submitted, but collects all tests and executes all of them later.
see, such executor on the gist
There is total 2 test functions in 2 classes in the example. If run the tests the summary results are:
Why number of skipped tests is 1? Which test has been skipped? All tests have been successfully completed.
So, I propose to calculate the summary results after all tests in the run completed or at least when test finished event is sent.
The text was updated successfully, but these errors were encountered: