-
Notifications
You must be signed in to change notification settings - Fork 26
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
[FEATURE] Add "failOnEmptyTestPage" option #228
Conversation
@matz3 can you review this change? |
@shahzeb79 thanks for the changes. Main change is that now an error is also logged even when to option is not enabled. With v3.0 we should enable this option by default. |
@matz3 thanks alot for your changes. Will it be available in v2.2.2 or some else? |
v2.3.0, as it's a new feature. We'll do a release once this PR is reviewed and merged. |
PR #228 did not fail because the SauceLabs API key (or any other secure variable) is not available in builds that are triggered from a fork.
PR #228 did not fail because the SauceLabs API key (or any other secure variable) is not available in builds that are triggered from a fork.
#226
Hi colleagues,
In S4 if some team has qunit and opa tests defined and loaded but OPA tests contains no tests or assertion, than runner should fail with error of "Suite with no tests should be removed". This happened when someone comment out testfiles in Alljourneys and runner still loads Alljourney but than reports no tests. In this case we see low coverages and team complains about it. So we want to configure runner so that we centrally can define some parameter in karma conf file to enable or disable failure in case of no tests.
Thanks