We start the testing course by developing Requirement Specification document where the functionality requirements are documented.

For Test Coverage, Test Traceability matrix is developed.

Test plan is a document, which describes the scope, process and objective of testing. This is a fairly standard procedure for testing such things, whether it be from https://www.parasoft.com/solutions/compliance/misra/ or from any other company. It describes some of the following steps:

• Describes the functionality to be tested
• Test Deliverables
• Schedules and Resource allocations
• Test Environment Details
• Functionality to be tested
• Identifying the tools to be used

Test planning is carried out on the basis of IEEE Standard for Software Test Documentation (IEEE Std 829-1998) and other industry specifications.

Test Case: -Test Scenario is created for the identified functionality. Then, our Test Analyst will create test cases based on test scenarios. In this document, Input and the Expected Output for functionality will be documented. The test cases are designed based on various Test design techniques.

Unit test case preparation is initiated for program releases in a progressive manner in line with delivery commitments. Integration test cases are written for testing integration between the modules and the overall flow of the project.

Test Data: – Based on the test cases created, we will create Input data before test case execution. Our Testing team is designing the test cases so that it covers all the application functionality but not exceeding cost and time constraint

Test Scripts: – Next step is Identifying the Test for automation. Preparing Test Scenario for the Testers will identify the functionality and create scripts for automating the test. We create the scripts and data for automation and execute the scripts

Test Environment: – Set up of the Test environment this involves the Hardware and Software Installation, Configuration of all Tools and Software.

Test Execution:– Here the test cases are executed. The bugs are tracked and documented. The scripts will be run for the test that needs automation. Various testing methods such as system integration testing and canary deployment may be used to identify and eliminate the maximum number of production bugs in the application.

Test reporting, analysis and Bug fixing management Our QA person will track the bug and report in Bug Tracking Tools. Once the bugs are fixed from development team, Retesting/Regression testing is done to assure that the bugs are closed.

Testing Team will prepare Test Summary report based on the test results. Test Summary report summarizes all the testing activities that were performed during the testing phase. The customers are aware about the testing activities and the status of the project testing. Then the Acceptance testing will be performed by the end Customers.