Quality Assurance / Testing & Validation
Quality Assurance:
The processes by which USM provides Quality Assurance (QA) services for companies are varied and focused on the particular needs of the customer. Given below is a flowchart that represents our methodology.
For each level of testing, as appropriate, the following activities will be performed:
The followingsection describes the various inputs, outputs, and the processes executed as a part of Various Steps of our QA methodology
Step 1 - Create Test Strategy
Inputs for this process :
Functional and technical requirements of the application (Requirements, Change requests, Technical and Functional design documents).
System Limitations, i.e. requirements that the system cannot provide.
Outputs of this process :
An approved and signed-off test Statement of Work (SOW) that describes the testing strategy, Test plan, Test scenarios, Test conditions, Test cases, and Deliverables.
Required hardware and software components, including Test tools (Test Environment, Test Tool Data), roles and responsibilities of the resources.
Process :
A test strategy is developed for all levels of testing, as required.
The USM Test Team analyzes the requirements, writes the test strategy and reviews the plan with the Quality Assurance Manager and the project team.
Test scenarios includes test conditions and cases, the testing environment, a list of testing related tasks, pass/fail criteria and testing risk assessment.
The test schedule identifies all tasks required for a successful testing effort, a schedule of activities, and resource requirements.
Feasibility study is carried out with the automated testing tool for that specific application.
top
Step 2 - Create Test Scenarios
Inputs for this process :
Automated test ware and previously developed scripts, if applicable (Test Tools).
Test document problems uncovered as a result of testing (Test Document Problems).
Understanding of software complexity and module path coverage derived from General and Detailed Design documents (Software Design, Code, and Complexity Data).
Outputs of this process :
Problems with the design to be fed back to the developers (Software Design, Code Issues).
Approved test scenarios, conditions and scripts (Test Design, Cases, Scripts).
Test data.
Process :
Test scenarios and cases are prepared by reviewing the functional requirements of the release and preparing logical groups of business functions that can be further broken into test scripts.
Tests define test conditions, data to be used for testing, and expected results (database updates, file outputs, report results, etc.).
Test scenarios are designed to represent both typical and unusual situations that may occur in the application.
The Test Team develops test scenarios/cases for GUI & FUNCTIONAL testing with assistance from developers and clients.
The client develops acceptance test cases with help from the project and Test Team.
Test scenarios are executed through the use of test scripts. Scripts define a series of steps necessary to perform one or more test scenarios.
A test script usually represents a transaction or process that can occur during normal system operations.
Test scripts include the specific data that is used for testing the process or transaction.
Test scripts cover multiple test scenarios and include run / execution / cycle information.
Test scripts are mapped back to the requirements and Traceability matrices to ensure each test are within the scope.
Test data is captured and base-lined, prior to testing. This data will serves as the foundation for system testing and is used to exercise system functionality in a controlled environment.
Some output data is also base-lined for future comparisons.
Base-lined data is used to support future application maintenance via regression testing.
A pre-test meeting is held to assess the “readiness” of the application, and the environment and data to be tested.
A test readiness document is created to indicate the status of the entrance criteria of the release..
Step 3 - Execute Test Cases
Inputs for this process :
Approved test documents (Test Plan, Cases, Procedures).
Automated test ware, if applicable and developed scripts (Test Tools).
Changes to the design (Change Requests).
Outputs of this process :
Changes to the code (Test Fixes).
Test document problems uncovered as a result of testing (Test Document Problems).
Problems with the design fed back to the developers and clients (Requirements, Design, Code Issues).
Formal record of test incidents (Problem Tracking - PT).
Base-lined package ready for migration to the next level (Tested Source and Object Code). Log and summary of the test results (Test Report).
Approved and signed-off with revised testing deliverables (Updated Deliverables).
Test data:
Availability of the test and project teams (Project Staff, Test Team).
General and Detailed Design Documents (Requirements, Software Design).
A complete development environment that has been migrated to the test environment via the Configuration/Build Manager.
Test Readiness Document.
Tools Used for Testing:
USM has an expert pool of consultants that are experienced in using various testing tools in different type of project. Some of them are:
Regression test tools - Rational Robot, Silk Test, Win Runner
Performance testing tools - Rational performance test studio, Load runner, Web load
|
