Datasheet

20 ■ Optimize Quality for Business Outcomes
Possible quality gates for the Unit Test are:
 Statement Coverage — Has each line of the source code
been executed and tested?
 Condition Coverage — Has each evaluation point (such
as a true/false decision) been executed and tested?
 Path Coverage — Has every possible route through a
given part of the code been executed and tested?
Integration Test
During the Integration Test we first look at the implementation
of each business function. After we validate that the business
function is functioning correctly, we can move to the next
phase, the various combinations of business functions.
Business Function Test
We’re testing these business functions in our example applica-
tions:
 Log in
 Log out
 Register
 Flight search
 Flight booking
We test each function independently as soon as it has passed
the Unit Test, using various approaches to complete the func-
tion test. We suggest using equivalence partitioning for the test
case development (we’ll explain more in Chapters 4 and 5).
Regardless of the applied methodology, the quality gates need
to be defined and met.
Possible quality gates for the Business Function Test are:
 All planned test cases have been executed.
 All incidents have been logged as defects.
MQM.book Page 20 Wednesday, May 7, 2008 11:29 AM