Closed AsaAyers closed 7 years ago
I'm not sure whether this works with tape, but for qunit & mocha this launcher in your testem.json
prints all your tests:
"launchers": {
"SL_chrome": {
"exe": "./node_modules/.bin/saucie",
"args": [
"-b", "chrome", "--at", "--u"
],
"protocol": "browser"
}
}
If you can help point me to how saucie passes the results back to testem, I can help make it work with the tap
protocol. Maybe I'm missing something, but it seems like it only cares about passed
or failedCount
https://github.com/johanneswuerbach/saucie/blob/master/lib/sauce-update-job-status.js#L34-L39
Saucie isn't returning the results back to testem, but is actually collecting them itself when running with protocol: browser
.
You can find a basic example here: https://github.com/airportyh/testem/blob/master/views/taprunner.mustache#L11-L16
I'm using saucie through testem to run tape tests on SauceLabs.
Using my workaround in https://github.com/johanneswuerbach/saucie/issues/5#issuecomment-147855384 I have been able to make my tests run and provide a pass/fail. When this runs I just have a pass/fail for the whole browser:
Is there any way to get this to report the actual tests?