Quality Testing

Quality is delighting customers

Test conditions ought to have the capacity to be linked back to their sources in the test premise, this is known as traceability. Traceability can be horizontal through all the test documentation for a given test level (e.g. system testing, through test conditions via test cases right till test scripts) or it can be vertical through the layers of development documentation (e.g. from requirements to components).

After reading this, the next question that would arise in the mind would be why is traceability so vital? To understand its importance, let’s take a look at the following scenarios:

The requirements stated for a given function or feature have altered. A portion of the fields now have diverse ranges that can be input. Which tests were taking a gander at those limits? They now should be changed. What number of tests will really be influenced by this adjustment in the requirements? These questions can be addressed effectively if the requirements can without much of a stretch be tracked to the tests.

An arrangement of tests that has run alright in the past has now begun creating significant issues. What functionality do these tests really exercise? Traceability between the tests and the requirements being tested empowers the functions or components influenced to be distinguished all the more effortlessly.

Before coming up with a new release, we need to know regardless of whether we have tested the greater part of the stated requirements in the requirements specifications. We have the rundown of the tests that have passed – was each requirement tested? That’s the question.

Requirements traceability and its importance:

Requirement Traceability is mapping of test case and requirements. There are two primary traceability: Forward and Backward. It is vital to know whether every one of the prerequisites specified in the Requirements Document have a related test case or not. In the meantime, it is critical to know which prerequisite a specific test case has been composed for. These are vital if there are any adjustments in the requirement, we should know which test cases should be re-written or altered.

Requirements Traceability is the last section of the test plan for measuring to cover all the requirements of the project. It empowers the users for finding the source of each necessity and track every one of the changes which made the prerequisite.

Requirement Traceability ensures that every requirement related to functionality utilized as a part of the advancement matches to those that were composed in the test cases in light of different relics. It guarantees that the team has shrouded every one of the requirements in testing and no functionality is passed up a major opportunity or left untouched. It decides the product dependability.

It’s purpose:

  1. To verify if test cases have been written for each and every requirement.

  2. To make sure that a specific test case is based on one or more requirements stated in the requirements document.

  3. It helps to know how many test cases are affected post a change in the application.

  4. To find out which test cases are written for which requirement.

  5. On the off chance that there emerges any disagreement regarding a bug in which developer states “it is not a bug according to the design”, all things considered the test case can be followed back to the requirement.

That was about requirements traceability and its significance in software testing. Hope that you enjoyed reading the same and got an insight into it.

Views: 44

Reply to This

Replies to This Discussion

As a part of the series on software testing, we would like to introduce you to the concept called as traceability in this article of ours. It would be an addition to your knowledge, as far as software testing is concerned.



TTWT Magazine





© 2017   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service