Test Summary Report - Software Testing Help

1 Allrights Summary ReportSample Test Summary Report Created and published by: Summary of Testing Environment & , Acronyms, and Allrights Summary document explains the various activitiesperformed as part of Testing of ABCD transport system Overview ABCD transport system is aweb based Bus ticket booking forvarious buses can be booked using the online time passengerinformationis received from a Central repository system , which will be referred before booking are several modules like Registration, Booking, Payment and Reportswhich are integrated to fulfill the Scope<This section explains about the functions/modules in scope & out of scope for Testing ;Any items which are not tested due to any constraints/ :A functionality verification which needs connectivity to a third partyapplication cannot be tested, as the connectivity could not be established due to sometechnical limitations. This section should be clearly documented, else it will be assumedthat Testing covered all areas of the application>a)In ScopeFunctional Testing for the following modules are in Scope of Testing Registration Booking Paymentb)Out of ScopePerformance Testingwasnot done for this )Items not testedVerificationofconnectivitywith thethird partysystem Centralrepository system was nottested, as the connectivity could not beestablished due to some technical can be verified duringUAT (User Acceptance Testing ) where the connectivity is availableor canbe established.

2 Allrights Summary <Metrics will help to understand the test execution results, status of test cases & defectsetc. Required Metrics can be added as necessary. Example: Defect Summary -Severitywise; Defect Distribution-Function/Module wise;Defect Ageing Charts/Graphs canbe attached for better visual representation>d)No. of test cases planned vs executede)No. of test cases passed/failedTest casesplannedTest casesexecutedTCsPassTcsFailed8075705f)No of defects identifiedand their Status & SeverityCriticalMajorMediumCosmeticTotal Closed251520060 Open0005565 Allrights Summary Reportg)Defects distribution module wiseRegistrationBookingPaymentReportsTot alCritical675725 Major452415 Medium682420 Cosmetic12115 Total-->1722101665 Allrights Summary of Testing performeda)Smoke TestingThis Testing wasdone whenever a Build is received(deployed into Testenvironment)for Testingto make sure the major functionalities areworking fine, Build can be accepted and Testing can )System Integration Testing This is the Testing performed on the Application under test, toverify the entire application works as per the requirements.

3 Critical Business scenarios were tested to make sure importantfunctionalities in the application works as intended without )Regression Testing Regression Testing was performed each time a new build isdeployed for Testing which contains defectfixes and newenhancements, if any. Regression Testing is being done on the entire application and notjust the new functionalities and Defect fixes. This testingensuresthat existing functionalities works fine afterdefect fix and new enhancements are added to the existingapplication. Test cases for new functionalities are added to the existing testcases and executed.<Describe the various types of Testing performed for the Project. This will make sure theapplication is being tested properly thro Testing types agreed as per Test Strategy> Environment & Tools<Provide details on Test Environment in which the Testing is carried out. Server,Database, Application URL etc. If any Tools were used like Quality Center (now HP ALM)for logging defects>Application 12gHP Allrights Summary Learnt<This section is used to describe the critical issues faced and their solutions (how theywere solved during the Testing ).

4 Lessons learnt will help to make proactive decisionsduring the next Testing engagement, by avoiding these mistakes or finding a suitableworkaround > facedSolutions1 Smoketesting testcasesrequired to be executedmanually each test cases were automatedand the scripts were run, which ranfast and saved ,Few testers were nothaving rights to change defectstatus in HP QC/ALM. Test leadneed to perform this were obtained from Client, byexplaining the <Any workaround or suggestions can be mentioned here.> Admin control for defect management tool can be given to Offshore Testlead/manager for providing access to Testing team. Each time the onsite Admin neednot be contacted for requests whenever theyarise, thereby saving time due to the geographical time zone Practices<There will be lot of activities done by the Testing team during the project. Some of themcould have saved time, some proved to be a good & efficient way to work, etc. These canbe documented as a Value Add to show case to the :A repetitive task done manually every time was time consuming.

5 This task wasautomated by creating scripts and run each time, which saved time and resources. Smoke test cases were automated and the scripts were run, which ran fast andsaved time. Automation scripts were prepared to create new customers, where lot ofrecords need to be created for Testing . Business critical scenarios are separately tested on the entire application whichare vital to certify they works fine. Allrights Summary Criteria<Exit Criteria is defined as a Completion of Testing by fulfillingcertain conditions>a)All test cases should be executed Yesb)All defects in Critical, Major, Medium severity should be verified andclosed )Any open defects intrivialseverity Action plan prepared with expected datesof :No Severity1 defects should be OPEN ; Only 2 Severity2 defects should be OPEN ; Only 4 Severity3 defects should be OPEN . Note:This may vary from projectto project. Plan of Action for the Open defects should be clearly mentioned withdetails on when & how they will be addressed and closed.

6 > Off<This section will mention whether the Testing team agrees and gives a Green signal forthe application to Go Live or not, after the Exit Criteria was met. If the application doesnot meet the Exit Criteria, then it can be mentioned as The applicationis notsuggested to Go Live .In this scenario,It will be left with the decision of SeniorManagement and Client and other Stakeholders involved to take the call on whether theapplication can Go Live or not.>As the Exit criteria was met and satisfied as mentioned in Section 10, this application issuggested to Go Live by the Testing team. Appropriate User/Business acceptancetesting should be performed before Go Live . , Acronyms, and Abbreviations<This section mentions the meanings ofAbbreviated terms used in this document andany other new definitions>**Sample Test Summary Report Created and published by.