Automate Acceptance Test Checklist in SBS CI #2466

New issue

Open

opened 2026-06-23 15:14:37 +00:00 by EricvanSchaik · 0 comments

EricvanSchaik commented

2026-06-23 15:14:37 +00:00

(Migrated from github.com)

Description

As a TPM, I want to have less manual acceptance testing work so that I can focus on more innovative stuff, and have the acceptance test be more reliable as well.

Acceptance testing happens manually now before deploying to production. There is an acceptance testing checklist that the TPM goes through step by step, and it can be expected that many of those steps can be automated with Playwright.

We now have two types of Playwright tests: one that tests our client/server/db stack in the SBS repo, and one that also spins up many peripheral services, such as ldap and mailpit, in the SRAM-deploy repo. The first is used for finegrained integration tests, and the latter is used for essential E2E tests. This issue is scoped to the first type of Playwright test, and therefore some parts of the testing checklist need to be mocked.

Task Overview

Acceptance Criteria

Everytime a mail is supposed to be sent, verify it in the activity log (/system/activity).
Everytime a user is supposed to login, use the proxy_authz endpoint to check (see https://github.com/SURFscz/SRAM-deploy/blob/main/e2e-tests/helpers/callSramApi.ts).
MFA testing is skipped here.
For every test flow, impersonate a user with the lowest possible role who has permission to perform the flow.
LDAP is skipped here.

Definition of Done

Notes

No response

### Description As a TPM, I want to have less manual acceptance testing work so that I can focus on more innovative stuff, and have the acceptance test be more reliable as well. Acceptance testing happens manually now before deploying to production. There is an [acceptance testing checklist](https://confluence.ia.surf.nl/spaces/coininfra/pages/209412036/SRAM+ACC+Testing+Checklist+Template) that the TPM goes through step by step, and it can be expected that many of those steps can be automated with Playwright. We now have two types of Playwright tests: one that tests our client/server/db stack in the SBS repo, and one that also spins up many peripheral services, such as ldap and mailpit, in the SRAM-deploy repo. The first is used for finegrained integration tests, and the latter is used for essential E2E tests. This issue is scoped to the first type of Playwright test, and therefore some parts of the testing checklist need to be mocked. ### Task Overview - [ ] ### Acceptance Criteria - [ ] Everytime a mail is supposed to be sent, verify it in the activity log (/system/activity). - [ ] Everytime a user is supposed to login, use the proxy_authz endpoint to check (see https://github.com/SURFscz/SRAM-deploy/blob/main/e2e-tests/helpers/callSramApi.ts). - [ ] MFA testing is skipped here. - [ ] For every test flow, impersonate a user with the lowest possible role who has permission to perform the flow. - [ ] LDAP is skipped here. ### Definition of Done ### Notes _No response_

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

eric/SBS#2466

No description provided.

Rows
Columns