- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-13-2022 10:23 AM
Hello, I am trying to run some UI test suite from Jenkins, and I can see that Jenkins can access the tests and starting to run, but the job failed after some waiting time. When I check the test suite results tab in SNOW, the tests even didn't start yet, just staying in Pending status.
Guessing the issue might be the client runner was not running or accessible. I would be great if any one share some inputs here.
Solved! Go to Solution.
- Labels:
-
Automated Test Framework
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-13-2022 06:07 PM
Hi
yes, you are right. You can either run an ATF suite manually in an opened browser tab with the ATF runner or with the so-called headless approach in case you want to trigger via Jenkins.
See https://docs.servicenow.com/en-US/bundle/sandiego-application-development/page/administer/auto-test... for more information.
Kind regards
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-13-2022 06:07 PM
Hi
yes, you are right. You can either run an ATF suite manually in an opened browser tab with the ATF runner or with the so-called headless approach in case you want to trigger via Jenkins.
See https://docs.servicenow.com/en-US/bundle/sandiego-application-development/page/administer/auto-test... for more information.
Kind regards
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2022 11:19 AM
Thanks for the reply.
I am wondering is there any other way to run the tests from Jenkins without headless browser mode. Appreciate the help.
Right now, I am launching the Scheduled Client Test Runner manually and keep it open so if my Jenkins job triggered, it will pickup the runner and run the UI test.
Alternatively, planning to automate these steps (Launch the browser, login and open the Scheduled Client Runner) before my test suite runs using some test frameworks like selenium, so the test will use that runner.
As compared to the steps involved in setting up the environment for headless mode, seems this is very easy option for me.