Closed Marketionist closed 4 years ago
Steps to reproduce
concurrency
{ "browsers": "chrome", "src": ["tests/**/*.js", "tests/**/*.feature"], "screenshots": { "path": "tests/screenshots/", "takeOnFails": true, "pathPattern": "${DATE}_${TIME}/test-${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.png" }, "quarantineMode": false, "stopOnFirstFail": true, "skipJsErrors": true, "skipUncaughtErrors": true, "concurrency": 2, "selectorTimeout": 3000, "assertionTimeout": 1000, "pageLoadTimeout": 1000, "disablePageCaching": true }
gherkin-testcafe
Actual result Setting "concurrency" in .testcaferc.json does not summon several browser instances - it executes feature files one after another
Note: launching the tests with gherkin-testcafe --concurrency 2 still works ok and summons 2 browser instances
gherkin-testcafe --concurrency 2
Sorry, my bad - forgot to place .testcaferc.json to the root folder. Now works ok, closing the issue.
.testcaferc.json
Steps to reproduce
concurrency
there - for example:gherkin-testcafe
Actual result Setting "concurrency" in .testcaferc.json does not summon several browser instances - it executes feature files one after another
Note: launching the tests with
gherkin-testcafe --concurrency 2
still works ok and summons 2 browser instances