Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flaky spec: Booth Display single booth for any number of polls #1203

Closed
3 tasks
bertocq opened this issue Feb 4, 2018 · 2 comments
Closed
3 tasks

Flaky spec: Booth Display single booth for any number of polls #1203

bertocq opened this issue Feb 4, 2018 · 2 comments

Comments

@bertocq
Copy link

bertocq commented Feb 4, 2018

Warning!

This spec probably only fails between 00:00 and 02:00 am Madrid time

What

Tests that fail randomly are called "flakies", this one seems to be one:

Randomized seed: 19087

Failure:

    2) Booth Display single booth for any number of polls
     Failure/Error: expect(page).to have_content 'Choose your booth'
       expected to find text "Choose your booth" in "Validate document Total recounts and results Language: English Español Français Nederlands Português Valencià How to help Menu Decide Madrid Polling Polling officers Notifications You don't have new notifications My activity My account Sign out Admin menu Validate document Total recounts and results × You don't have officing shifts today Poll officing Here you can validate user documents and store voting results"
     # ./spec/features/officing/booth_spec.rb:82:in `block (2 levels) in <top (required)>'

How

  • Explain why the test is flaky, or under which conditions/scenario it fails randomly
  • Explain why your PR fixes it
  • Create a backport PR to consul/consul when the fixing PR is approved

Tips for flaky hunting

Random values issues

If the problem comes from randomly generated values, running multiple times a single spec could help you reproduce the failure by running at your command line:

for run in {1..10}
do
  bin/rspec ./spec/features/budgets/investments_spec.rb:256
done

You can also try running a single spec in Travis:
Add option :focus to the spec and push your branch to Github, for example:

scenario 'Show', :focus do

But remember to remove that :focus changes afterwards when submitting your PR changes!

Test order issues

Running specs in the order they failed may discover that the problem is that a previous test sets an state in the test environment that makes our flaky fail/pass. Tests should be independent from the rest.

After executing rspec you can see the seed used, add it as an option to rspec, for example:
bin/rspec --seed 55638 (check Randomized seed value at beginning of issue)

Other things to watch for

@bertocq
Copy link
Author

bertocq commented Feb 6, 2018

@javierm
Copy link

javierm commented Sep 19, 2018

Closed via consul#2712 and #1625.

@javierm javierm closed this as completed Sep 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants