Enrolment And Access UAT Journeys
Purpose
Use these journeys when a change may affect sign-in, session handling, seller profile details, user defaults, or admin access management.
Preconditions
- You know which user account to test with.
- For admin checks, the account has administrator access.
- For non-admin checks, use a normal active account.
Sign-In And Session Smoke
Steps
- Open Glovelly.
- Sign in with the test account.
- Open Clients, Gigs, and Invoices.
- Refresh the page.
- Confirm the same workspace data returns without a new sign-in prompt.
- Sign out.
Expected Results
The user can sign in, navigate through the core workspaces, refresh without losing the session, and sign out cleanly.
Seller Profile And Defaults
Steps
- Open seller profile.
- Add or edit seller name, address, email, and payment details.
- Save.
- Generate or redraft an invoice.
- Download the PDF.
Expected Results
The invoice PDF reflects seller profile and payment details. Missing profile details produce helpful UI notices rather than broken invoices.
User Settings
Steps
- Open user settings.
- Change default invoice or mileage settings.
- Save.
- Create a new client or gig that uses defaults.
- Generate an invoice where those defaults should apply.
Expected Results
Saved defaults are reused in later client, gig, or invoice workflows where expected. Existing records are not unexpectedly overwritten.
Admin Access
Steps
- Open Admin as an administrator.
- Create or edit a user record.
- Toggle active state or role.
- Save.
- Confirm the user list updates.
Expected Results
Admin changes persist and non-admin users cannot access admin workflows.
Inactive User Deletion
Steps
- Select an active user.
- Confirm the
Delete userbutton is red and disabled. - Edit that user, mark the account inactive, and save.
- Confirm
Delete useris enabled. - Click
Delete userand decline the confirmation prompt. - Confirm the user remains in the list.
- Click
Delete useragain and accept the confirmation prompt.
Expected Results
Only inactive users can be deleted. Active users, including the current administrator account, cannot be deleted.
Notes
Access changes can lock testers out of an environment. Confirm the target user before changing active state or administrator role.