🧪 Testing - Introduce new tests to cover new Azure-based flow after outdated tests have since been removed

Cc: @suiyangqiu @yaqi-lyu @calumjs @joshbermanssw
Hi Tiger team

▶️ Watch the video (28 sec)

Pain

Our existing E2E/automation coverage no longer validates the current sign-in/onboarding path because the old test scripts were removed due to outdated logic. This risks regressions in the new Azure-based flow going unnoticed.

Suggested Solution

Add new automated tests (and any required test helpers/fixtures) to cover the new Azure-based flow used by SSW.Tiger.

Acceptance Criteria

Acceptance Criteria defines the requirements that must be met for the story to be completed. This is WHAT must be done.

See https://www.ssw.com.au/rules/acceptance-criteria.

1. New automated tests exist that validate the Azure-based flow end-to-end.
2. Tests run successfully in CI.
3. Legacy/outdated test logic is not referenced by the new tests.

Tasks

Tasks help developers to track small bits of work needed to meet the ACs. This is HOW the work will be done.

- [ ] Identify the new Azure-based flow steps that require automated coverage
- [ ] Add new test files to cover the Azure-based flow
- [ ] Implement any required test utilities/mocks/fixtures for the Azure-based flow
- [ ] Update the CI pipeline config to execute the new tests
- [ ] Run the tests in CI and fix any failures

More Information

The old test scripts were removed because their logic was outdated; we still need coverage for the new Azure-based flow.

Screenshots

Thanks!

Start by identifying the current Azure-based sign-in and onboarding flow, then find the CI configuration and any remaining test entry points after the outdated scripts were removed. Define the required end-to-end steps and add the necessary tests, helpers, mocks, or fixtures. Done means the new tests cover the flow, avoid legacy logic, and pass in CI.