The Quality Assurance and Testing is a seven step process.

Step 1: Define Test Strategy

Define testing strategy in collaboration with the customer tied to the product's release, sign-off criteria, and its business objectives.

• Define project scope & commitments
• Set customer expectations
• Tie together the business objectives of the project with the release/sign off criterion and associated testing activity
• Integrate the quality processes with development lifecycle
• Partition the problem into manageable test plans
• Identify key dependencies and trade-offs, test coverage, metrics etc.
• Identify which features/components will be tested manually, which will be tested via automation, and what kind of automation tool is required (script-based, GUI-based, proprietary, off-the-shelf, etc.)
• Release Planning

Step 2: Test Planning

The next step is Test Planning which involves:

• Define release criteria including start and complete
• Outline and prioritize the testing effort
• Determine test automation requirements
• Identify resource requirements at various stages of testing
• Set up calendar-based activity plan
• Establish communication model
• Configure team including number, type, and seniority of resources and length of time required, mapped each resource onto the activity plan
• Define test cycles - how many test cycles are to be run.
• Define Test Types to be run - White box, Black box, security, performance, regression, usability, compatibility etc..

Step 3: Test Execution

Although each project has different requirements, execution usually follows this process:

• Prepare comprehensive test cases for each type of testing
• Prepare test data and test logs
• Set up the test environment so that all operations can be completed promptly, accurately, and efficiently
• Execute Error/Trap tests to ensure testers accuracy
• Execute tests as described, noting where test cases require revision and updating

Step 4: Defect Management

Report all bugs in the manner agreed upon with the customer, following defect management protocols, informing customer of current status, monitoring and driving to resolution all outstanding issues, and ensuring that communication between all parties is complete and accurate.

Step 5: Test metrics

We identify or develop, collect and regularly report metrics. These metrics are not historical data. These metrices help the stakeholders of the project including project managers and top management to understand the health of the project and make timely decisions with regard to quality of software.

Step 6: Release

At project completion, review all aspects of the project and submit a Project Close-out report to the customer that objectively evaluates the project's execution and results

Step 7: Post release Testing

We help you to test the software during the maintenance phase.