New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[test-suite] It would be nice to be able to start and stop the test suite gracefully #1662

alhambrav opened this Issue Dec 1, 2017 · 0 comments


2 participants

alhambrav commented Dec 1, 2017

Expected behavior

It would be nice to be able to start and stop the tests gracefully, so that when you stop the script, the webdriver/selenium is also stopped OR sites created by the test are not left behind in Studio.
I'm not sure how best to do this, but something like ./gradlew test start, then give back the prompt to the user and maybe have the output displayed on another window? (or something like that), then when the user stops the test in the middle ./gradlew test stop, cleanup can be performed if it's possible?

Actual behavior

When running the tests, if you want to stop it in the middle, you have to terminate the test script, which leaves the webdriver/selenium test still running OR, leaves sites created by the test in Studio

Steps to reproduce the problem

  • On the command line, run
gradlew.bat test
  • Let the test run for a few minutes, then stop the test by pressing <ctrl> + c
  • Notice that in Windows, the webdriver is still running after terminating the script, in OS X, the webdriver stops running, but sometimes there are leftover sites created by the test in Studio after you stop the test in the middle.

Log/stack trace (use

Specs: version, OS, browser, etc.

OS X OS, Windows OS - Chrome browser

@sumerjabri sumerjabri added this to the Crafter CMS v3.1.0 milestone Dec 1, 2017

@sumerjabri sumerjabri added this to Backlog in Crafter CMS v3.1.x via automation Aug 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment