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 }}
This repository has been archived by the owner on Oct 10, 2021. It is now read-only.
After tried many time, I have found the reason. Here is the reason from saucelabs' documentation:
All you have to do is add either markdown or HTML code to your GitHub README or project site that references your Sauce Labs username and access key, and annotate your tests with the REST or WebDriver API.
What we need here is to use saucelabs api to update the job with an 'passed' field to indicate whether the test has passed on client site and it must be updated explicitly during a separate API call.
And here is how karma-runner module did it:
The text was updated successfully, but these errors were encountered:
dzcpy
changed the title
Update saucelabs job info with annotation after test ( for makeing saucelabs badge work)
Need to update saucelabs job info after test otherwise saucelabs won't work
Jun 12, 2016
Currently if we use zuul + saucelabs to test, regardless if all tests pass or not, saucelabs always show an unknown barge.
See this project to prove:
https://github.com/algolia/faux-jax
After tried many time, I have found the reason. Here is the reason from
saucelabs
' documentation:What we need here is to use saucelabs api to update the job with an 'passed' field to indicate whether the test has passed on client site and it must be updated explicitly during a separate API call.
And here is how
karma-runner
module did it:The text was updated successfully, but these errors were encountered: