As part of the development of tests is the traceability matrix to establish a connection between the test cases and to be tested or required functionality to establish and document the fact that at this level a full coverage exists.
These are usually the requirements to test cases compared in tabular form. Useful tools range from simple office applications (eg MS Excel) to large software development tools (eg Rational Test Manager, Mercury TestDirector). The use of these tools is dependent, inter alia from the demands and complexity of a project.
test team's work is greatly facilitated if the requirements are present well structured. The example can be Rational RequisitePro requirements with record structure, and connect it to the test cases in TestManager. In a separate opinion can represent the traceability matrix in table format. The advantage of this approach is the redundancy compared to the separate maintenance of a table.
suitable for smaller projects, a simpler method by which the coverage is established implicitly. If the requirements are structured appropriately (eg as specifications), can be easily deduced from a naming scheme for the test cases. The comparison of the contents of the specification and the list of test cases provides adequate transparency about the coverage.
I should point out that a full traceability matrix is \u200b\u200bnot sufficient to find all the fault of the software. However, it can ensure that all areas will be tested.
0 comments:
Post a Comment