Datasheet

What Is the Big Deal About Testing? ■ 19
a <LOG IN> button or ENTER on the keyboard, the validation
of username and password should start.”
The acceptance criteria for that requirement could be:
 If a username without a password is entered, an error
message is displayed.
 If the username and the password are a correct combi-
nation, the system shows the flight-search screen.
 If the username and the password are not a valid combi-
nation, an error message is displayed.
Ideally, the business analyst or business user writing the accep-
tance criteria identifies missing information and ambiguities in
the requirements, documents those as defects, and hands them
over to the development team.
Possible quality gates for the Requirements Verification phase
are:
 One hundred percent of the requirements have at least
one documented acceptance criterion (such as the online
flight booking).
 We have divided the application into business functions
and prioritized each business function according to the
quality needed to meet the business goal of allowing the
user to book a flight online.
Unit Test
Unit testing is part of the development lifecycle, so we don’t
make specific recommendations for this phase in our airline
booking example.
However, we need to agree on the quality gates for the Unit
Test, because it defines the quality level we can expect when
the software is handed over. In other words, if the software
does not meet the defined criteria, the test team will not accept
it for the Integration Test.
MQM.book Page 19 Wednesday, May 7, 2008 11:29 AM