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 }}
Repository navigation
Update README to callout existing issue with test coverage not being generated when running in CI #422
import{forceModulesToBeLoaded,sendCoverage}from'ember-cli-code-coverage/test-support';importQunitfrom'qunit';if(config.APP.isRunningWithServerArgs){// until Testem is patched, this will fail to POST coverage in CI mode (running tests with -s or --server as an argument)// Ref: https://github.com/testem/testem/issues/1577QUnit.done(asyncfunction(){forceModulesToBeLoaded();awaitsendCoverage();});}else{//eslint-disable-next-line no-undefTestem.afterTests(function(config,data,callback){forceModulesToBeLoaded();sendCoverage(callback);});}
Hello! Possibly a small oversight with this but we noticed that unless you check for test or t you may brick the ability to run tests from visiting /tests while the app is being served.
@cah-john-ryan Thank you for the workaround. I run tests in 6 containers and some of them don't save the coverage file 🤷♂ I typically get a 50:50 success rate - I mean 3 containers fail, 3 succeeds. I got to the point where I understood that there's no "enough time" to save them but I couldn't figure out why. Now I get it.
Activity
malatin3 commentedon Feb 6, 2025
Hello! Possibly a small oversight with this but we noticed that unless you check for
testortyou may brick the ability to run tests from visiting/testswhile the app is being served.tniezurawski commentedon Feb 9, 2025
@cah-john-ryan Thank you for the workaround. I run tests in 6 containers and some of them don't save the coverage file 🤷♂ I typically get a 50:50 success rate - I mean 3 containers fail, 3 succeeds. I got to the point where I understood that there's no "enough time" to save them but I couldn't figure out why. Now I get it.
The workaround works great for me ❤