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

Implement user flow for e2e smoke test for Sender Settings Page #15905

Closed
1 task done
chris-kuryak opened this issue Sep 17, 2024 · 1 comment · Fixed by #15998
Closed
1 task done

Implement user flow for e2e smoke test for Sender Settings Page #15905

chris-kuryak opened this issue Sep 17, 2024 · 1 comment · Fixed by #15998
Assignees
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team

Comments

@chris-kuryak
Copy link
Collaborator

chris-kuryak commented Sep 17, 2024

Problem statement

We need to create an e2e test that mimics a user flow.

What you need to know

For example: https://staging.reportstream.cdc.gov/admin/orgsendersettings/org/ignore/sender/ignore-empty/action/edit

Feel free to use the Ignore org on staging

Acceptance criteria

  • For a Sender on IGNORE org, Name, Format, Topic, Customer Status, Processing Type all populate with some type of non-error data
@chris-kuryak chris-kuryak added engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team labels Sep 17, 2024
@chris-kuryak chris-kuryak changed the title Copy of Implement user flow for e2e smoke test for Org Settings Edit Page Implement user flow for e2e smoke test for Sender Settings Page Sep 17, 2024
@chris-kuryak chris-kuryak removed the needs-refinement Tickets that need refinement from the team label Sep 17, 2024
@penny-lischer penny-lischer self-assigned this Sep 22, 2024
@chris-kuryak
Copy link
Collaborator Author

Per Penny, may be closed by end of sprint.
Will get back to Mikaelah by end of day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants