-
Notifications
You must be signed in to change notification settings - Fork 38
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
Fix intermittent test failures #368
Fix intermittent test failures #368
Conversation
9b7c06d
to
7ec9626
Compare
7ec9626
to
982ae30
Compare
This change adds checks to ensure that this.$sticky exists and it is visible before trying to access its methods. Further information at #368
69626bd
to
7d6a9cc
Compare
I have re-run the tests 10 times and they have consistently passed each time. |
Thanks for doing this @marcotranchino, the tests failing are a real problem for merging changes at the moment. Forgive me if I'm wrong but reading the changes to So I'm not sure how testing the truthyness of I might also just be missing something obvious :) What do you think? |
Following a PR review[1], this commit changes the test on this.$sticky, in order to verify if the object actually contains any elements. Further details in the PR[2]. [1] #368 (comment) [2] #368
I have made the suggested change, @tombye, thanks! |
Also this PR can be merged into your branch, @kr8n3r |
This change adds checks to ensure that this.$sticky exists and it is visible before trying to access its methods. Further information at #368
Following a PR review[1], this commit changes the test on this.$sticky, in order to verify if the object actually contains any elements. Further details in the PR[2]. [1] #368 (comment) [2] #368
This change adds checks to ensure that this.$sticky exists and it is visible before trying to access its methods. Further information at #368
Following a PR review[1], this commit changes the test on this.$sticky, in order to verify if the object actually contains any elements. Further details in the PR[2]. [1] #368 (comment) [2] #368
This change adds checks to ensure that this.$sticky exists and it is visible before trying to access its methods. Further information at #368
Following a PR review[1], this commit changes the test on this.$sticky, in order to verify if the object actually contains any elements. Further details in the PR[2]. [1] #368 (comment) [2] #368
This change adds checks to ensure that this.$sticky exists and it is visible before trying to access its methods. Further information at #368
Following a PR review[1], this commit changes the test on this.$sticky, in order to verify if the object actually contains any elements. Further details in the PR[2]. [1] #368 (comment) [2] #368
This change adds checks to ensure that this.$sticky exists and it is visible before trying to access its methods. Further information at alphagov#368
Following a PR review[1], this commit changes the test on this.$sticky, in order to verify if the object actually contains any elements. Further details in the PR[2]. [1] alphagov#368 (comment) [2] alphagov#368
With this change, we are fixing the intermittent test failures by
updating the tests' setups and afterEach instructions and also by
updating some modules in order to prevent access to properties that
have not yet been initialised properly.