provide list of scenarios to run in the travisfile (expected: scenario in development + any dependencies)
We have experienced a few paint points with travis tests including:
-waiting on other tests
-getting other tests to pass with reruns
-tests having to be excluded altogether
-tests eating into our limited credit balance (usually only a problem if a lack of local testing is abused)
Usually we are uninterested in our test matrix of 17-odd tests, which have been proven to work at time of latest development. Our code changes often shouldnt affect these.
The only reason I see for keeping things this way is as a way to check that the web dependencies in our roles still work as expected. This can be handled through user issues.
romakarol
commented
2 years ago 
Test new travisfile. Want to check that:
We have experienced a few paint points with travis tests including: -waiting on other tests -getting other tests to pass with reruns -tests having to be excluded altogether -tests eating into our limited credit balance (usually only a problem if a lack of local testing is abused)
Usually we are uninterested in our test matrix of 17-odd tests, which have been proven to work at time of latest development. Our code changes often shouldnt affect these.
The only reason I see for keeping things this way is as a way to check that the web dependencies in our roles still work as expected. This can be handled through user issues.