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

Add automated, post-deployment sanity tests #490

Open
malini opened this issue Jun 14, 2024 · 3 comments · May be fixed by #792
Open

Add automated, post-deployment sanity tests #490

malini opened this issue Jun 14, 2024 · 3 comments · May be fixed by #792
Assignees
Labels
enhancement New feature or request M: Appointment Beta 3 testing Issues specific to automated testing

Comments

@malini
Copy link
Contributor

malini commented Jun 14, 2024

Is your feature request related to a problem? Please describe.
We should add automated tests that run post deployment to ensure that things are hooked up correctly. This is in response to issues we found during deployment.

Describe the solution you'd like
We should be able to achieve these using webdriver tests (wdio/playwright/etc).
A starting list of tests:

  • a test to check if the splash page loads successfully. Requires no test user accounts.
  • tests to confirm we can access a booking link and can successfully schedule something. Requires a test user account to have set up a booking link. We should test both long urls and short urls here.
  • a test that checks the basic login flow. Requires a test user account's credentials.

We'll need test accounts in fxa, so we should create creds for these test accounts and store them in 1password for our own historical logging, and also put them in a secrets manager or similar so automation can read them.

@rwood-moz
Copy link
Contributor

Before starting the E2E tests complete #780 (add data-testid attributes).

@rwood-moz rwood-moz added the testing Issues specific to automated testing label Dec 2, 2024
@rwood-moz
Copy link
Contributor

Note that this post-deployment E2E 'sanity' test will run in BrowserStack when run in CI.

@rwood-moz
Copy link
Contributor

Splitting this issue into two parts, this issue is for landing the splash screen appearance and basic sign in / out flows; I created #787 to expand the test suite further and add tests to actually schedule an appointment via the booking link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request M: Appointment Beta 3 testing Issues specific to automated testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants