Cucumber scenarios must be decoupled and independent of each other, hence it must make no difference in what order they will run. If you have scenarios that depend on previously executed ones, I suggest to review your design.
Cucumber features/scenarios are run in Alphabetical order by feature file name.
If you still in a particular order-
if you specifically specify features, they should be run in the order as declared. For example:
Yes. Changing the order of the items in the CucumberOptions had no effect on order of execution, annoyingly. Renaming the tests so that they were alphabetically ordered did the trick, as I mentioned. Interestingly, the alphabetical ordering must be by ascii.
It’s unpleasant and hacky, but it gets the job done.