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

Performance Testing in the Cloud with JMeter & AWS

JMeter is a wonderful tool  to stress test your website and  your application architecture , however if you are trying to simulate many users (>1000) one JMeter instance (=pc) will not be sufficient. You will have to set up a JMeter cluster with multiple machines. JMeter is capable or running  distributed tests , but it comes with limitations. Since most of us don’t have multiple servers laying around somewhere, we usually go to cloud service providers like  AWS , spin up a couple of  EC2 instances  and turn them off whenever we’re done. Here is the problem, JMeter uses  Java RMI (Remote Method Invocation)  to communicate to its slaves, but these connections require all machines to be on the same subnet and this is not feasible with EC2 instances. Below, I explain how to get around this problem using a 3 node configuration in AWS to execute tests. I assume that you have a written the test already and have the .jmx file r...
Post a Comment
Read more

Difference Between Redirect Automatically and Follow Redirects in JMeter

In this post, we will highlight important difference between Redirect Automatically and Follow Redirects options. These options are found in HTTP Request sampler of JMeter. Knowing the difference will help you decide your performance test strategy. When you check Redirect Automatically option, JMeter will not consider redirect as separate HTTP request. This in turn may result as lower response time in your overall performance test. Whereas Follow Redirect option will consider each redirection as separate requests. This may result in comparatively higher response time. This only has any effect if “Redirect Automatically” is not enabled. To see the difference between these two, record a sample script and run it by checking Redirect Automatically and Follow Redirects option. The second option will generate more requests in your result listener. As you can see from the above post, knowing the difference between Redirect Automatically and Follow Redirects option makes difference i...
Post a Comment
Read more