Support Forum

Hello, We create an HTML report after our automated tests in Jenkins. They tend to provide more context than the stack traces we get with the JUnit report. However, one friction point we've noticed is that errors/failed assertions within nested it/describe blocks are often hidden from view, requirin...

I'll have to give it a shot tomorrow. I don't think I'll have any issue with using the Sauce API but I'm not sure how I'd know which test(s) are run during a particular chunk. I can give them a naming convention like test1, test2, test3 and they'll at least have uniq names. However, from our discuss...

I added faker to the harness page (index.html) and am not using the preload method on the harness. In doing so, it's available in the global scope of the test page.

1. My initial thought is that if information required to use the Sauce Labs REST API were made available from the launcher to the harness, that all the API requests could be either made from within the test run (either while the test is running or in a setup/teardown step). So you might have a test....

Ok thanks! I thought that'd be what I'd want to do. Just for clarification though, when you say on the harness page, you do mean index.html (the same place I'd load Siesta's library)? This is what I've done and faker is available from the test object but it's also in the global scope of the browser ...

What would be the proper/recommended way to add an external library like faker.js to Siesta?

https://github.com/Marak/faker.js

Btw, this may help: https://github.com/danjenkins/node-saucelabs

Hmmm.... ok it looks like this could also be accomplished via Sauce Labs' REST API: https://wiki.saucelabs.com/display/DOCS/Annotating+Tests+with+the+Sauce+Labs+REST+API using PUT /rest/v1/USERNAME/jobs/JOB_ID https://wiki.saucelabs.com/display/DOCS/Job+Methods I'd need the JOB_ID and it looks like ...

This worked, thanks! Though the test setup is slower, we are in progress of parallelizing our test runs. SauceLabs recommends that tests are parallelized and the equivalent of driver.quit() is run at the end of every test. Is there a way that I can set --cap "name=myTestname" on a per test...

How can I run the selenium binding at the end of every test? This is needed so that Sauce Labs will see each test as a separate run and use a new VM per test.

Related, is there a way to run raw selenium code?