RUNNER SHOULD (OPTIONALLY) KEEP SELENIUM OPEN #155

Closed
jeffbcross opened this Issue Oct 9, 2013 · 4 comments

Comments

Projects
None yet
4 participants
@jeffbcross
Contributor

jeffbcross commented Oct 9, 2013

It would be nice for the Protractor runner to start my selenium server, run my tests, and keep the selenium server open to run my tests again later without having to start up the selenium server, since it takes soooo long to start.

This is achievable right now by starting the selenium server myself, setting the address of the server in protractorConf, and then running Protractor. But it's 2013 and I want everything to happen in one command!

As discussed IRL with @juliemr, here is one way this feature could be implemented:

  • An option in protractorConf that says keepSeleniumOpen (or something better)
  • Hit enter in the shell of the running protractor process to run tests again
@marcorinck

This comment has been minimized.

Show comment
Hide comment
@marcorinck

marcorinck Oct 10, 2013

+1 for the idea in the mentioned ticket that a grunt task can start the selenium server and re-execute tests after changes. Much like karma does already.

+1 for the idea in the mentioned ticket that a grunt task can start the selenium server and re-execute tests after changes. Much like karma does already.

@juliemr

This comment has been minimized.

Show comment
Hide comment
@juliemr

juliemr Oct 16, 2013

Member

Looked into this a bit today - unfortunately, jasmine and minijasminenode (as well as a bunch of Protractor stuff) have a lot of assumptions that they'll only be run once. So, it'll take a little untangling, and will probably be easiest to implement when upgrading to Jasmine 2.0.

edit note: another option would be to have a separate command line which would kick off another process each time the tests are run.

Member

juliemr commented Oct 16, 2013

Looked into this a bit today - unfortunately, jasmine and minijasminenode (as well as a bunch of Protractor stuff) have a lot of assumptions that they'll only be run once. So, it'll take a little untangling, and will probably be easiest to implement when upgrading to Jasmine 2.0.

edit note: another option would be to have a separate command line which would kick off another process each time the tests are run.

@jeffbcross

This comment has been minimized.

Show comment
Hide comment
@jeffbcross

jeffbcross Jan 23, 2014

Contributor

With the advent of the webdriver manager, this is no longer an issue.

Contributor

jeffbcross commented Jan 23, 2014

With the advent of the webdriver manager, this is no longer an issue.

@jeffbcross jeffbcross closed this Jan 23, 2014

@tyrw

This comment has been minimized.

Show comment
Hide comment
@tyrw

tyrw Jan 27, 2015

@jeffbcross can you elaborate on why webdriver manager solves this? I'd also like to keep the browser open between runs.

tyrw commented Jan 27, 2015

@jeffbcross can you elaborate on why webdriver manager solves this? I'd also like to keep the browser open between runs.

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