4.1.1.1. Test Objectives
The objective of the test is to verify that the functionality of SaFi Mobile App works according to the specifications.
The test will execute and verify the product features, fix and all high and medium severity defects per the entrance criteria, prioritize lower severity defects for future fixing via CR (Change Request).
The final product of the test is twofold:
An EFPS-ready software;
A set of stable test scripts that can be reused for Functional and UAT test execution.
4.1.1.2. Test Assumptions
Key Assumptions
Production like data required and be available in the system prior to start of Functional Testing
In each testing phase, Cycle 3 will be initiated if the defect rate is high in Cycle 2.
General
Exploratory Testing would be carried out once the build is ready for testing.
Performance testing is not considered for this estimation.
All the defects would come along with a snapshot JPEG/MP4 format.
The Test Team will be provided with access to Staging environment.
The Test Team assumes all necessary inputs required during Test design and execution will be supported by the Development team, Project Manager, and Product Owner appropriately.
Test case design activities will be performed by QA team.
Staging environment and preparation activities will be owned by Dev Team
Dev team will provide Defect fix plans based on the Defect meetings during each cycle to plan. The same will be informed to QA team prior to start of Defect fix cycles.
Project Manager/Product Owner will review and sign-off all Test cases prepared by QA Team prior to start of Test execution.
The defects will be tracked through JIRA only. Any defect fixes planned will be shared with QA Team prior to applying the fixes on the Staging environment.
Project Manager/Product Owner will review and sign-off all test deliverables.
The project team will provide test planning, test design and test execution support.
QA team will manage the testing effort with close coordination with the Development team, Project Manager, and Product Owner.
Project team has the knowledge and experience necessary, or has received adequate training in the system, the project and the testing processes.
There is no environment downtime during test due to outages or defect fixes.
The system will be treated as a black box; if the information shows correctly online and in the reports, it will be assumed that the database is working properly.
Cycle 3 will be initiated if there are more critical defects in Cycle 2.
4.1.1.3. Test Principles
Testing will be focused on meeting the business objectives, cost efficiency, and quality.
There will be common, consistent procedures for all teams supporting testing activities.
Testing processes will be well defined, yet flexible, with the ability to change as needed.
Testing activities will build upon previous stages to avoid redundancy or duplication of effort.
Testing environment and data will emulate a production environment as much as possible.
Testing will be a repeatable, quantifiable, and measurable activity.
Testing will be divided into distinct phases, each with clearly defined objectives and goals.
There will be entrance and exit criteria.