O'Reilly logo

Continuous Integration, Delivery, and Deployment by Sander Rossel

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Selenium tests

Next, are the Selenium tests. This is really just a batch command on the Windows slave. We can unstash 'Everything' and run npm install again, but we can also just save one from our tests. While not all tests can use the same workspace, it is perfectly fine to give them their own workspaces. Since we are already using the Test Chrome node to publish our reports, let's build that one in a workspace that we can also use for our Selenium tests:

[...] "Test Chrome": {            node(label: 'windows') {              ws(dir: 'web-shop-pipeline') {                gitlabCommitStatus(name: 'Test Chrome') {[...]

After that, it is just a matter of running the batch. We are going to run the script a little different than before though. First, for clarity, we will just run ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required