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

Auto reset/create test accounts in dev and stage #838

Closed
we-ai opened this issue Dec 5, 2023 · 3 comments
Closed

Auto reset/create test accounts in dev and stage #838

we-ai opened this issue Dec 5, 2023 · 3 comments
Assignees
Labels
CCC Priority 1 Issues to be addressed in the current release

Comments

@we-ai
Copy link
Collaborator

we-ai commented Dec 5, 2023

Test accounts need to be reset/created for each round of testing various scenarios in dev and stage. The account reset/create functionality can be implemented in SMDB. Below are tentative requirements:

  • Authenticated SMDB users are allowed to do it
  • Multiple accounts can be reset/created in a single UI page
  • Provide options to reset/create an account to a specific stage: brand new, verified, consent forms submitted, etc

Note:

  • When doing account resets, need to check whether account age (creation time) affects account behaviors in PWA, and update it if so.
@brotzmanmj
Copy link
Collaborator

Undecided if will reset test accounts or create code to generate new test accounts. Putting on hold for later discussion among the team.

@we-ai we-ai changed the title Reset test accounts in dev and stage Auto reset/create test accounts in dev and stage Dec 5, 2023
@we-ai
Copy link
Collaborator Author

we-ai commented Dec 5, 2023

Updated issue title and description, based on discussions today: undecided regarding resetting existing accounts or creating new accounts for a new round of tests.

@sonyekere
Copy link
Collaborator

sonyekere commented Jul 31, 2024

Per the DevOps meeting on 7/31: Automated testing won’t be fully integrated into the August release but will be useful for ongoing work. The plan moving forward is to reset existing test accounts rather than create new ones.

@amber-emmes will start by investigating automatic account resetting

High Level Summary of Approach:

  • Begin with simple automated tests and expand based on initial findings
  • @Davinkjohnson Create GitHub issues to track test cases and progress
  • Ensure testing covers both front-end interactions and back-end data integrity
  • Reuse existing code where possible to streamline future updates

@sonyekere sonyekere added the CCC Priority 1 Issues to be addressed in the current release label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCC Priority 1 Issues to be addressed in the current release
Projects
Development

No branches or pull requests

6 participants