We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, when requiring a test file, if an error gets throw, the error is logged by console.error() and the test-loader will continue to require the next test file. See https://github.com/ember-cli/ember-cli-test-loader/blob/master/addon-test-support/index.js#L71
console.error()
This effectively ignores all the tests that are part of the test file that did not get required, which would cause unexpected missing test coverage.
Was interested in knowing what is the rational in the choice of the current implementation. @rwjblue would you have some context on this?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, when requiring a test file, if an error gets throw, the error is logged by
console.error()
and the test-loader will continue to require the next test file.See https://github.com/ember-cli/ember-cli-test-loader/blob/master/addon-test-support/index.js#L71
This effectively ignores all the tests that are part of the test file that did not get required, which would cause unexpected missing test coverage.
Was interested in knowing what is the rational in the choice of the current implementation.
@rwjblue would you have some context on this?
The text was updated successfully, but these errors were encountered: