Replace the flaky features run script with a proper executable
ClosedPublic

Authored by ervin on Feb 15 2016, 10:21 PM.

Details

Summary

This way we can properly wait for the cuke steps server to show up
before launching cucumber which removes the race (and thus random
failure) we were seeing on the acceptance tests.

I had to adjust cucumber-cpp a bit so that it doesn't quit after the
first connection attempt.

Diff Detail

Repository
R4 Zanshin
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
ervin updated this revision to Diff 2314.Feb 15 2016, 10:21 PM
ervin retitled this revision from to Replace the flaky features run script with a proper executable.
ervin updated this object.
ervin edited the test plan for this revision. (Show Details)
ervin added reviewers: bensi, franckarrecot, dfaure.
dfaure accepted this revision.Feb 15 2016, 10:33 PM
dfaure edited edge metadata.
dfaure added inline comments.
tests/features/features-run.cpp
75

You could add a waitForStarted(), to increase the chances that the first waitForConnected() succeds? Just an idea. Might also help with error handling in case the process fails to start (e.g. segfault, binary not found, missing lib etc.).

78

I'm surprised that you need this Q_UNUSED (and the one for app above), is that for a compiler or an IDE? They should both accept the RAII pattern ;)

This revision is now accepted and ready to land.Feb 15 2016, 10:33 PM
ervin updated this revision to Diff 2316.Feb 16 2016, 6:06 AM
ervin edited edge metadata.

Address dfaure's comments

ervin marked 2 inline comments as done.Feb 16 2016, 6:07 AM
bensi accepted this revision.Feb 16 2016, 8:22 AM
bensi edited edge metadata.
This revision was automatically updated to reflect the committed changes.