Testing Roles & Responsibilities
Assignment of testing responsibilities for Project Peregrine and Project Buzzard features.
Categories:
Testing Roles and Responsibilities
To ensure thorough testing of both the ongoing maintenance of Project Buzzard and the development of Project Peregrine, the following roles and responsibilities are defined.
General Testing Principles
- Feature Branch Testing (Peregrine): Developers are responsible for basic testing of their own feature branches before creating a Pull Request. Internal builds created via EAS Feature Builds should be distributed to designated testers for validation.
- Regression Testing: Before major releases or merges, dedicated regression testing should be performed on both platforms.
- Issue Reporting: All bugs or unexpected behavior should be reported promptly via [Specify Issue Tracker, e.g., Linear or GitHub Issues]. Include clear steps to reproduce, expected vs. actual results, device information, and build version.
Role Assignments
(Note: Please update names and specific assignments as needed)
| Role / Responsibility | Assigned To | Project Focus | Key Tasks |
|---|---|---|---|
| Lead QA / Test Coordinator | [Name / TBD] | Both | Oversee test planning, assign testing tasks, manage bug triage, coordinate regression testing efforts. |
| Peregrine Feature Tester (iOS) | [Name(s)] | Peregrine (iOS) | Test new features on iOS via EAS builds, perform targeted regression testing on iOS. |
| Peregrine Feature Tester (Android) | [Name(s)] | Peregrine (Android) | Test new features on Android via EAS builds, perform targeted regression testing on Android. |
| Buzzard Maintenance Tester (iOS) | [Name(s)] | Buzzard (iOS) | Verify fixes and updates delivered by ABCloudz on iOS, perform regression testing on Buzzard iOS builds. |
| Buzzard Maintenance Tester (Android) | [Name(s)] | Buzzard (Android) | Verify fixes and updates delivered by ABCloudz on Android, perform regression testing on Buzzard Android builds. |
| User Acceptance Testing (UAT) | [Stakeholder(s)] | Both (Pre-Release) | Validate features meet business requirements and user expectations before public release. |
Testing Device Pool
- Maintain a list of physical test devices (iOS and Android) covering target OS versions and hardware profiles.
- Ensure testers have access to necessary devices.
- Collect Device UDIDs for iOS testers.
(Add links to specific test plans or checklists if available)
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.