The test-requirements cross-reference matrix demonstrates how each requirement is listed within software requirements specification. In some cases it can be represented in a form of a table.

The general approach to defining test cases involves using tables that enumerate the possible input data and actions that will be applied to the test cases. Each of these pairs (input data / actions) is the basis for the test case or test methodology, if additional information is required to fully define the test. The naming convention for test cases varies from project to project. When using the naming convention, the tests in test case matrix are classified into the corresponding groups. Additional information can be obtained using the notes. An asterisk indicates that the test ID appears several times in the table. For individual test cases or test methods it is very appropriate to implement several functions. You can use an indent to indicate priorities, distribution of tests, test pass or other relevant information. Software testing consulting is a reliable way to know how to maximize your return on investment and promote the adoption of effective testing strategy into your company.

The advantage of the cross-reference matrix is ​​that it performs the role of a short guide to a wide range of test sets, indicating the results of particular tests. Such a table also serves as an index computed for a set of descriptions of test cases, which details are written elsewhere in the form of a page in the array of the test case documents or as a separate file on the disk. In some large test sets, this type of matrix can be used instead of TOCs that function as an online pointer to a test case file, where each test case is saved as a separate file on the network. By the way, it is possible to improve productivity and quality of your mobile app by using mobile application testing service.

The difference between the traceability matrix and the cross-reference matrix is ​​barely perceptible. The main difference is that in the traceability matrix, each test requirement is assigned a unique identifier. Depending on the terminology used in each organization, or if in the product specification each requirement is already marked with a unique identifier these two types of matrices can be considered identical. The task here is to structure the tables in such a way as to maximize the distribution of information. Usability testing companies verify the ease with which user interface can be used. They also reveal whether or not the customer feels comfortable with a given application.