Using the provided examples (updated for ES6) I am running into a strange error, namely: only the first test that belongs to a group using the built in Nightwatch tag system will run, before the test runner stops and exits. However running the same set of tests locally (without browserstack) will properly run all tests that are tagged with the given tag.
For example, this, using browserstack, will only run the first test that belongs to a tagged group:
Will run and complete the 1st test (on both browsers) which matches the given tag before exiting. I can see the results both in my local console and at browserstack.com/automate.
However running the same command using the built in test runner and without the browserstack config behaves as expected:
nightwatch --tag myTag --env chrome,firefox
Not sure how or why the Browserstack test runner differs exactly but I'm using the one provided. Posting here for clarity:
Using the provided examples (updated for ES6) I am running into a strange error, namely: only the first test that belongs to a group using the built in Nightwatch tag system will run, before the test runner stops and exits. However running the same set of tests locally (without browserstack) will properly run all tests that are tagged with the given tag.
For example, this, using browserstack, will only run the first test that belongs to a tagged group:
./localRunner --tag myTag --env chrome,firefox --config conf/browserstack-parallel-local.conf.js
Will run and complete the 1st test (on both browsers) which matches the given tag before exiting. I can see the results both in my local console and at browserstack.com/automate.
However running the same command using the built in test runner and without the browserstack config behaves as expected:
nightwatch --tag myTag --env chrome,firefox
Not sure how or why the Browserstack test runner differs exactly but I'm using the one provided. Posting here for clarity:
Adding my conf file for clarity too: