Monday, March 31, 2014

What is Traceability Matrix?

In software testing, an important document is called Traceability Matrix (TM) or Requirements Traceability Matrix (RTM). This is the document that connects the requirements to the test cases. The connection or mapping of the requirements to test cases is many-many. This means that one requirement is tested by one or more test cases. Conversely, it is possible to have one test case addressing one or more requirements.

If you don't understand the RTM, view the video, Requirements Traceability Matrix that explains the RTM with an example.

Next, let us see some useful points about the Requirement Traceability Matrix.

Wednesday, March 19, 2014

Example Test Strategy

Test strategy is the plan (that may exist at any level like project, program, department or organization level) that describes how the test objectives would be met effectively with the help of the available resources. If you have a test strategy, it is easier to focus effort on the most important test activities at the time. Moreover, a test strategy provides clarity on the test approach to the project stakeholders.

Having said that, my earlier post, How to create a powerful test strategy, is well read. According to web analytics, its readership has been among the top five articles of this blog for quite some time. However, many readers asked for example software testing strategy document that I could not share at the time. Therefore, I requested Varsha, who is a senior member of the Software Testing Space community, to create an example test strategy for a hypothetical agile project. Below is the resulting sample test strategy document. The sections contain much information. Additional guidelines are given in italics. I hope that this sample test strategy document helps you create a really effective test strategy for your own project. First, view the video, Example Agile Test Strategy, Agile Test Plan. Then read on.