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

Disable application submission in tests #418

Merged
merged 4 commits into from
Jan 3, 2025

Conversation

lukecamelo
Copy link
Contributor

Asana task

We don't want to submit applications in cypress tests anymore, as the submissions appear in the SimpliGov dashboard and this can be confusing.

@lukecamelo lukecamelo requested a review from a team as a code owner December 23, 2024 16:44
@lukecamelo lukecamelo requested a review from Adzz December 23, 2024 16:44
Copy link
Collaborator

@napilla napilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we also remove the enters parental data and submits tests from the applications or will this not populate for the admins to see in prod?

.should('contain', 'Application Submitted');
});
// Disable submission
//it("skips the demographic section and agrees to the rules", function() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: generally not the best idea to keep "dead" code around, because if we tried to introduce it again its more likely to not make sense given other changes that have occurred. I'd say this should just be deleted.

@napilla
Copy link
Collaborator

napilla commented Dec 26, 2024

also, I tired running the tests in simpligov pre-prod, and saw some applications (in review / waiting states) and wondering if this will ultimately still be annoying to admins in prod.
image

I wonder if there is more of a benefit to just stopping the tests in prod instead of trying to run a sub-set of tests in pre-prod.

@napilla
Copy link
Collaborator

napilla commented Jan 3, 2025

also, I tired running the tests in simpligov pre-prod, and saw some applications (in review / waiting states) and wondering if this will ultimately still be annoying to admins in prod. image

I wonder if there is more of a benefit to just stopping the tests in prod instead of trying to run a sub-set of tests in pre-prod.

per discussion at standup, it seems we definitely do not want applications submitted in simpligov prod, but I'm really unsure if we can modify the tests in general to not do that and still have meaningful tests. Therefore, we decided on stopping the tests running in https://github.com/mbta/reduced_fares/actions/workflows/automation-prod.yml and keep this workflow running: https://github.com/mbta/reduced_fares/actions/workflows/automation-preprod.yml

If we learn for some reason we really do need these tests running in prod, but not having them create applications, we should then consider which tests we truly need to run in prod.

Copy link
Collaborator

@napilla napilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we revert the tests we removed?

@lukecamelo lukecamelo merged commit 27cceb2 into main Jan 3, 2025
2 checks passed
@napilla napilla deleted the lfc/feat/halt-automated-tests branch January 3, 2025 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants