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.
Labels:

Comments

Post a Comment

Popular posts from this blog

JMeter Exceeded Maximum Number of Redirects Error Solution

While running performance test, JMeter allows maximum 5 redirects by default. However, if your system demands more than 5 redirects, it may result in JMeter exceeded maximum number of redirects error. In this post, we have listed down steps to overcome this error. Actual error in JMeter: Response code: “Non HTTP response code: java.io.IOException” Response message: “Non HTTP response message: Exceeded maximum number of redirects: 5” This error is noticed because  JMeter  allows maximum 5 redirects by default and your system may be using more than 5 redirects. You need to increase this count to more than 5 in jmeter.properties file. Follow below steps to achieve this. Navigate to /bin directory of your JMeter installation. Locate jmeter.properties file and open it in any editor. Search for “httpsampler.max_redirects” property in opened file. Uncomment the above property by removing # before it. Change to value to more than 5 Eg. 20. Save the file and restart JMeter. If
Post a Comment
Read more

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
Post a Comment
Read more

A Tutorial to Send Email using JMeter

Sending email is a mundane activity in any professional’s life. It’s a common medium for communication nowadays. Therefore performance testing of email server is not only important but necessary for an organization. JMeter can be helpful to perform load testing in such scenarios. In this tutorial, we will see how JMeter can be used to send email. We will use SMTP Sampler of JMeter to send an email. JavaMail API is needed to enable email functionality in JMeter. Download it from  here  and paste the jar in JMeter’s lib folder. Now, perform below steps to configure SMTP Sampler. Add a new Thread Group under Test Plan. Right click on Thread Group and select Add–>Sampler–>SMTP Sampler. We need to populate SMTP server’s details in this sampler. We will use GMail for sending an email. For this, enter these values in SMTP Sampler fields. Server: smtp.googlemail.com, Port: 587. Provide values in Email Address From and To fields of Mail Settings section to specify sender and reci
Post a Comment
Read more