Software Testing Situation Documentation
One of the key deliverables of any software testing project is the status report. The report or document provides the summary data that the project uses to gauge progress and judge the amount of effort remaining. A well written report helps provide credibility for the QA team and enables the manager to argue for more resources when they are needed. Without the status document there is no possibility to compare planned activities against actual work. There is no real evidence that your test team is carrying out the work they should be.
All of this of course depends on what your software testing document contains. If you’re reporting on the wrong facts then this is probably worse than having no report at all. After all if you are making your management decisions based on the wrong data then you can rest assured that you’re making the wrong decisions. With the right facts you stand a far better chance of guiding your team to deliver the results required. More chance of finding the product defects before release. And more chance releasing the right product on time.
All of this depends on listing the right facts in your software testing status document. At a minimum that data should include the following information.
Trending: This is the essential information about the number of written tests. It also includes the list and results of the ones that have been done. It usually covers a period of about 2 to 3 weeks.
Owner: This provides the details of the tests and the persons they are assigned to. This is more explanatory if the status is indicated. This makes it easy to discover problems with the allocation.
Traceability: shows which requirements may be lacking in coverage. Helps identify holes in the testing and to a certain extend helps people see where the effort is being focused.
Automation Runs: This makes available different graphs for manual and automated software testing trials. The results of these tests can be very important. It enables the confirmation of the importance of automation tools.
Feature: This is a valuable break down of results in comparison with the product’s features. It clearly shows where efforts are being directed. It also shows the areas that are not getting enough attention.
Whilst the content of the software testing report is important, so is the way in which you present that data in the document. The following tips should help you construct your report and get your information across to the people that matter.
1. Let your format be consistent. You should maintain the same format every week. Individuals who look at the document weekly for important details will not like to waste precious time trying to find the details that they want to see. Using a consistent format makes it easy for individuals to locate what they are interested in.
2. Have a regular distribution. The software testing report should be given out regularly. Regular distribution of the bulletin will help to build credibility. When team members get a status report early on Monday, they will be able to direct their resources throughout the week in line with the provided data.
3. Let your circulation be wide. Don’t limit the details to a small number of people. More readers will give attention to the details of the report if they are aware that their senior managers have been given the same document. The software testing status document should be given to anyone who has a part in the project.
4. Keep it short. Pages and pages of facts won’t get read. If you can keep it to one page then managers and team members will be more likely to read and digest the information. The key is keeping the information on that one page that is useful and remove the information that is not useful. The only way to find that out is to ask the people that are reading the report. Perhaps start off with three pages, solicit responses on the information on that and remove what people don’t need.
5. Use an attractive design. Documents that are badly arranged will not attract much readership. We all have the habit of judging documents that are presented to us with a quick glance. You have to make the printed page very attractive so that a quick glance will convince your readers that it deserves to be read.
6. Target people. You should create alternative reports if you have different groups of readers. Each group may be interested in different aspects of the report. Senior managers do not require extensive details on certain issues. It is better to present graphs and charts to them. It is however necessary for the software testing group members to see the details of the five main issues in their copy of the report.
7. Delivery. The way the report is delivered to the readers is important. If the report is placed in the body of the email, it will have a higher likelihood of being read than if it is sent as an attachment. Similarly, more attention will be attracted if the document is printed and given physically to the targeted people. A printed document easily stands out from the numerous emails that are received everyday.
It is important for every project to generate and distribute a report regularly with a uniform set of data. It is a very good way for your test team to see their accomplishments and to stay motivated on the project. From the perspective of the software testing team, a well written status report helps to show the remaining project members and the company that the team deserves attention and investment.
Visit our site to learn all there is to know about software testing status reports, now. You can also find information about essential software testing tools at http://www.softwaretesting.net today.
July 21, 2011 | Posted by Godfrey Leyborne
Categories:
Tags:
Recent Comments