QA context from my CV
PMS SaaS Tool is listed as a collaborative tool with role-based access control and real-time sprint tracking. This study focuses on permission boundaries, shared state, status changes, and collaboration reliability.
Risk & proposed scope
The highest risks are unauthorized project access, stale sprint status, conflicting edits, and unclear ownership. The proposed scope uses admin, manager, developer, and viewer accounts across the same project board.
Example test scenarios
- Attempt admin-only actions from lower roles and verify rejection in UI and API.
- Move a task between sprint states from two browser sessions and inspect conflict handling.
- Remove a user from a project and verify immediate access change.
- Create sprint reports after status updates and compare counts.
- Test offline or delayed network behavior for real-time updates.
Evidence & release criteria
Evidence should include account role, project ID, task ID, before/after status, API response, and second-client observation. Release should block permission leaks, lost tasks, and contradictory sprint counts.