We are developing the next version of CrazyEngineers. If you wish to receive latest updates and early access, click the link below.
Matrix Model For Test Processes
Trends in software testing always changes with the introduction of new technologies. Testers are required to do not only plain testing but be more technical and process oriented.
In this tutorial you will get in-depth understanding of Testing Processes used in different organisations to streamline the testing activities.
Testing is always considered to be a process than a single activity. Testing must start from requirement gathering for the project and should always run in parallel with the project execution.
It must be planned and required discipline to act upon.
Test process is a systematic process to determine how the testing is progressing in the actual scenario. It is moreover an Audit or Review of documented processes which an organisation implements.
Test Processes plays major role in defining quality and effectiveness of software testing being conducted in the project.
Following Matrix Model will show you how Test Processes should be implemented in large scale projects:
Set and agree
for the system.
Prioritize business requirements; identify those that are essential and those that are optional.
For a given delivery date, filter out, reprioritize, or renegotiate unrealistic system expectations.
Specify requirements that are testable. Remove or firm up ambiguous requirements.
Define acceptance criteria that are meaningful to the business.
Define relevant industry standards or competitive benchmarks.
Ensure that stakeholders agree to a capacity plan for the system with measurable capacity requirements.
Define a test strategy.
Formulate and document a test strategy; relate it to the test quality plan.
Identify high-risk zones early on; mark these for early testing and keep them away from the project's critical path.
Identify all aspects of the system that require testing; in each case, indicate the level and form of testing.
Identify relevant testing tools that can help automate or document elements of the test process.
Plan the testing
Estimate required resources, such as tools, people, hardware and software infrastructure, test location, and so on.
Define roles and responsibilities; identify a suitably qualified test manager and test team.
Draw up and agree to a detailed test plan with the client; define test milestones and test deliverables.
Plan a pre-release simulation period where the system can be observed under simulated business usage.
Set up the test environment
Set up the physical test environment—for example, the hardware and
Prepare test material such as detailed test plans, test scripts, and test data.
Prepare test materials with reuse in mind.
Set up the defect-tracking system; decide on the form of defect reporting
And any test metrics to use.
Define test standards and procedures; educate individuals on the use of
Standards and procedures.
Acquire and prepare the necessary test tools; ensure that the test team
Receives relevant training.
Conduct appropriate quality reviews, such as code reviews and walk-through’s.
Conduct testing, whether at the unit, integration, system, or use-
Execute tests and collate test results; record results and incidents in the
Analyze test results; monitor areas with a high incidence of defects and
Track and manage defect resolution.
Where appropriate, repeat the test and reuse test materials to expedite
Stage a pre-live simulation period; test the system under the expected
Business usage and observe results.
Manage the decision to go live based on testing results; consider if the
System has achieved a release standard.
Monitor system performance using relevant monitoring tools; use
Performance reporting to guide performance-tuning activities.
Capture any residual defects; assess their priority and, if serious, consider
a rectification plan.
Gather feedback and problem reports from users; analyze these to
Identify future improvements.
Capture and prioritize new business requirements; assess their impact on
the system before committing to them.
Fix outstanding and residual defects.
Plan the system's next release; agree to a release plan with relevant
Ensure a smooth transition from the current release to the new release.