Skip to main content

Test Report Preparation: A Detailed Guide

Just as effective software testing is important, test reporting is equally valuable in overall QA activities. Test report or test summary report is prepared at the end of every QA cycle. This report highlights facts, risks, accomplishments and important events of the QA cycle. In this post, we will explore about effective test report preparation.

\\\

Test summary report is the component that informs key project stakeholders of the critical aspects of the project’s status. It also outlines if current test cycle is successful of not. Test report typically contains below components.
Project Name: Name of the project.
Release Number: This should contain release/build number for which the test summary report is being prepared. Typically it is same as the release number received in current cycle’s release note.
Tested Items: This section contains items which are tested as part of test execution cycle. List down all the modules which have been released in current build and which are tested in QA cycle.
Status of Project: Present current status of project. It should contain total number of test cases executed in each browser, passed/failed/pending test cases, total number of defects reported in current test cycle. Also, provide classification of issues as per their priority/severity (Eg. Major, Critical etc.), issue status(Eg. Open, Resolved etc.) and their types(Eg. Bug, Improvement etc.). You can also cover some charts which shows defect distribution, defect detection rate and current state of testing in overall project duration.
Risks: Provide details about risks which may arise during testing activities in project. This could be too many number of unresolved issues, many Blocker/Critical/Major issues, untested feature, limited testing time etc. Be comprehensive in detailing risks so that preventive measures can be taken at project level by team members.
Project Health: Highlight overall project health in context of testing. Color coding can be used here to mark overall project health(Red/Orange/Green).
Conclusion/Remarks: Conclude the report by writing QA decision whether the current build has passed testing.
The above guidelines talks about important aspects of test report preparation. You may extend the test summary report with additional items which you think would be important in project. Do share with us about how do you go about test report preparation in your project.

Comments

Popular posts from this blog

SSO with SAML login scenario in JMeter

SAML(Security Assertion Markup Language) is increasingly being used to perform single sign-on(SSO) operations. As WikiPedia puts it, SAML is an XML-based open standard data format for exchanging authentication and authorization data between parties, in particular, between an identity provider and a service provider. With the rise in use of SAML in web applications, we may need to handle this in JMeter. This step-by-step tutorial shows SAML JMeter scenario to perform login operation. First request from JMeter is a GET request to fetch Login page. We need to fetch two values ‘SAMLRequest’ and ‘RelayState’ from the Login page response data. We can do this by using  Regular Expression Extractor . These two values need to be sent in POST request to service provider. Refer below image to see how to do this. We will get an HTML login page as a response to the request sent in 1st step. We need to fetch values of some hidden elements to pass it in the next request. We can do this b

Reading data from text file in SoapUI using groovy script

How to read data from text file in SoapUI. SoapUI Pro has some advance feature which is not in SaopUI as data fetching from external sources so in SoapUI we use Groovy script for that. Following are the peace of groovy script code for reading data from text file. 1. Reading all data from text file. //reading all txt file at once File file = new File("E://TestData.txt") fileContent = file.getText()                  log.info fileContent 2. Reading data line by line from text file. //reading text line by line File file1 = new File(" E://TestData.txt ") List textLine = file1.readLines() log.info textLine 3. Reading data randomly of any line from text file. //reading text randon line number File file2 = new File(" E://TestData.txt ") List textLine2 = file2.readLines() rowIndex  =  Math.abs(new Random().nextInt() % 4 + 1) log.info textLine2[rowIndex]

VBScript Code - Function to convert CSV file into excel and viceversa in QTP using VBScript

We at times are required to convert excel files into csv to read as flat files and sometime require to convert a csv file into excel file to use excel features on the data.   Below function shows how to convert an csv file into excel file and vice versa. We can also convert to other formats based on constants Here constant value 23 is used to create a csv file and constant -4143 to save a file as xls file. Once the destination file is created, we can delete the source file as shown below.  In case of any issue in understanding the code, please add in comment section Call func_ConversionCSVExcel("E:\Test.csv", "E:\Test_converted.xls", "csvtoexcel") Public Function func_ConversionCSVExcel(strSrcFile, strDestFile, Conversion) on error resume next Set objExcel = CreateObject("Excel.application") set objExcelBook = objExcel.Workbooks.Open(strSrcFile) objExcel.application.visible=false objExcel.application.displayalerts=