Running a large set of tests, the number of tests executed differs between test runs. This probably happens because setup failed and skipped some tests. But it also confusing.
I believe this is because x-unit and scripted test handles skipped tests differently.
@mikeduskis writes, "I’ve looked at this several times before and think I see a solution now: on suite error, load the suite python file as plain text and produce a test_skipped event for each test context that starts after the line number where the error occurred. Maybe I’m missing some important obstacle."
Running a large set of tests, the number of tests executed differs between test runs. This probably happens because setup failed and skipped some tests. But it also confusing.
I believe this is because x-unit and scripted test handles skipped tests differently.
@mikeduskis writes, "I’ve looked at this several times before and think I see a solution now: on suite error, load the suite python file as plain text and produce a test_skipped event for each test context that starts after the line number where the error occurred. Maybe I’m missing some important obstacle."