Skip to content

Conversation

@aedwardg
Copy link
Collaborator

@aedwardg aedwardg commented Sep 3, 2023

What github issue is this PR for, if any?

Resolves #5176

What changed, and why?

Previous test was relying on factory sequences, but alphabetization of numerical strings can have unexpected results.

For example:
image

This PR updates the test to use hard-coded names for the case contacts so that alphabetization will always return the same result.

How will this affect user permissions?

  • Volunteer permissions: N/A
  • Supervisor permissions: N/A
  • Admin permissions: N/A

How is this tested? (please write tests!) 💖💪

The change is a test 🙂

Screenshots please :)

Feelings gif (optional)

alphabetized

Feedback please? (optional)

We are very interested in your feedback! Please give us some :) https://forms.gle/1D5ACNgTs2u9gSdh9

@github-actions github-actions bot added ruby Pull requests that update Ruby code Tests! 🎉💖👏 labels Sep 3, 2023
@aedwardg aedwardg force-pushed the 5176-fix-flaky-contact-type-test branch from 1aa024a to 03ead8c Compare September 3, 2023 08:12
@aedwardg aedwardg changed the title use explicit names in test instead of numerical sequence Fix flaky contact type alphabetization test Sep 3, 2023
@FireLemons FireLemons merged commit ed57931 into main Sep 4, 2023
@FireLemons FireLemons deleted the 5176-fix-flaky-contact-type-test branch September 4, 2023 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ruby Pull requests that update Ruby code Tests! 🎉💖👏

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Flaky Test Failed To Find Contact Types on Page

3 participants