[ISTQB] 2.3 Test types (K2)

A test type is focused on a particular test objective (function, security, reliability..) and could be related to changes done (regression or confirmation testing).

LO-2.3.1 Compare four software test types (functional, non-functional, structural and change-related) by example (K2) 

A good test is "measurable, observable and repeatable"

• functional testing is the "analysis of the specification of the functionality of a component or system". So the system does what's expected and is correct with regards to documentation agreed (requirement/functional/component specification, uses cases) or expert opinion when no documentation exist.
• functional testing are performed upon black box testing techniques and could be also security or interoperability testing.

LO-2.3.2 Recognize that functional and structural tests occur at any test level (K1)

• Functional and structural tests could be based on:
• testing component specification
• testing other documentation that describe functions and features expected
• testing interoperability between specific systems.

LO-2.3.3 Identify and describe non-functional test types based on non-functional requirements (K2) 

• Non functional testing is performed at any level (black box) and is focused on how well the system or component not related to a functionality works such as reliability testing, portability testing, load testing, performance testing, stress testing (asses limits), usability testing, maintainability (how is easy to correct the software).

LO-2.3.4 Identify and describe test types based on the analysis of a software system's structure or architecture (K2) 

• structural testing is performed at any level and is based "on analysis of the internal structure of the component of system" like testing a menu structure and its structure coverage. 

(% component/total component expected has to be stated in the test plan).

• structural testing is a type suitable with component and integration testing and may be based upon the system architecture or hierarchy.

LO-2.3.5 Describe the purpose of confirmation testing and regression testing (K2)

• confirmation testing aims to confirm that a defect has been fixed and no other defects have been introduced (regression). This is all based on risk analysis.