pioneer
pioneer copied to clipboard
Cleanup driver commands after scenario
If a step schedules a lot of driver commands, and an early one fails, if the driver is retained (i.e. keep the same driver for all scenarios) it will carry on with those scheduled commands into the next scenario.
By flushing the command queue after each scenario, we ensure that no 'old' commands are run in the wrong steps.
Looks like this is breaking tests in a really odd wait https://travis-ci.org/mojotech/pioneer/jobs/62042409#L412
@samccone that link looks like it goes to a passing test. :confused:
@shoe if you look at that line only 1 integration test was run :grimacing:
So breaking in this case meaning that this code change has the side-effect of canceling all other integration test runs queued up.
@samccone good catch. "Not all that's green is good" I guess.
Maybe we should do it in before scenario rather than after? Haven't looked at that link yet as I'm in a meeting!
Cheers,Tom
On Tue, May 12, 2015 at 3:37 PM, Chris Shoemaker [email protected] wrote:
@samccone good catch. "Not all that's green is good" I guess.
Reply to this email directly or view it on GitHub: https://github.com/mojotech/pioneer/pull/321#issuecomment-101302895