PA 3.4 SG 3 – Perform non-functional test analysis and design

During test analysis and design the test approach for non-functional testing is translated into tangible test conditions and test cases.

Introduction

This should be part of the overall approach to test specification and design and should include full traceability back to the requirements and risk assessment.

Although there are specific elements to non-functional test specification, the design and preparation should follow the same, established, processes.

Specific Practices

SP 3.1 Identify and prioritise non-functional test conditions

SP 3.2 Identify and prioritise non-functional test cases

SP 3.3 Identify necessary specific test data

SP 3.4 Maintain horizontal traceability with non-functional requirements

As with all types of testing, a list of requirements should be produced. In this case they are non-functional requirements.

The requirements must drive test design along with the risk analysis, in order to design tests which are prioritised and appropriate.

It is a common problem for non-functional requirements to be poorly conceived.

Deployment notes

• Are the non-functional test conditions and test data specified according to the standard test process and procedures?
• Are the non-functional test assets traceable and aligned to non-functional requirements?
• Are the non-functional requirements prioritised based on risk?
• As with the established process and procedures for overall test specification and preparation, are non-functional features adequately analysed?
• Are test cases, procedures and associated test data, pre- and post requisites defined and documented based on risk?