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: Polls Booth & Website Already voted on booth cannot vote on website #1208

Closed
3 tasks
bertocq opened this issue Feb 5, 2018 · 7 comments
Closed
3 tasks
Assignees

Comments

@bertocq
Copy link

bertocq commented Feb 5, 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: 31908

Failure:

    1) Polls Booth & Website Already voted on booth cannot vote on website
     Failure/Error: select 'DNI', from: 'residence_document_type'
     Capybara::ElementNotFound:
       Unable to find visible select box "residence_document_type" that is not disabled
     # ./spec/support/common_actions.rb:204:in `officing_verify_residence'
     # ./spec/features/polls/polls_spec.rb:462:in `block (3 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

@bertocq
Copy link
Author

bertocq commented Feb 7, 2018

@bertocq
Copy link
Author

bertocq commented Feb 7, 2018

@iagirre
Copy link

iagirre commented Mar 6, 2018

I think that this flaky is related to this one: #1195
Maybe I missed something, but, just for clarification: aren't both tests testing the same thing? 🤔

@iagirre
Copy link

iagirre commented Mar 8, 2018

I'm doing this.

@decabeza
Copy link

Closed by #1342

@raul-fuentes
Copy link

I'll backport this one

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

5 participants