Since upgrading to 2.0 our cucumber tests no longer run in any discernible order as they once did on 1.0.
I understand that 2.0 tries to balance out the tests evenly by the looking at previous runs. But as the occasional test will fail and re-run, this doesn’t work very well for the purposes of testing. Worst of all, the same test will often run multiple times across multiple containers and other tests will not run at all.
In Circle 1.0 they ran in the order they were in our folder. In our case, in alphabetical order. So we always knew that test “A” would always be the first test in container 0 for example.
Has anyone any idea how we can get back to something like this. Where the same tests will always run in same container every time we do a run. Other than creating a folder for each set of tests and setting up all new test suites. Also possibly how to disable the test balancer.