AUTOMATED TEST FRAMEWORK ATF
FUNDAMENTALS MICRO CERTIFICATION
COMPREHENSIVE STUDY GUIDE WITH
SOLUTIONS
◉ Development Team Leader.
Answer: The member of staff responsible for leading the team
developing the AUT. Liaises with the test team leader to report on
the progress of the development of the AUT and likely dates for
delivery of AUT for testing purposes.
◉ End Users.
Answer: The members of staff who will use the delivered AUT in
support of their work
◉ Equivalence/Partition Class.
Answer: A set of the component's input or output domains for which
the component's behavior is assumed to be the same from the
component's specification. An equivalence class may also be termed
an equivalence partition.
◉ Equivalence Class Testing.
,Answer: A test case design technique for a component in which test
cases are designed to execute representatives from equivalence
classes. This form of testing may also be termed domain or partition
testing.
◉ Error Guessing/ Experienced Based Testing.
Answer: A test case design technique where the experience of the
tester is used to postulate what faults might be present in a
component or AUT, and to design tests specifically to expose them.
◉ Fault Recovery Testing.
Answer: This form of testing verifies that following an error or
exceptions, the AUT is restored to a "normal" state, such as the initial
state of the AUT when it is first executed. This form of testing may
also be used to verify the successful rollback and recovery of the
data used or manipulated by the AUT.
◉ Functional Requirements.
Answer: Traditionally, those requirements for the AUT that have
been specified within the functional specification document for the
AUT. Also see nonfunctional requirements.
◉ Functional Specification.
Answer: A document that describes in detail the characteristics of
the AUT with regard to its intended capability.
, ◉ Functional Testing.
Answer: The process of testing the AUT to verify that it meets its
functional requirements. These requirements are typically recorded
in a requirements specification document.
◉ Incremental Testing.
Answer: A testing technique used in integration testing, where
untested modules are combined with the module under test
incrementally, with the func¬tionality of the module (plus the added
modules) being tested (retested) as each module is added.
◉ Independent Test Observer.
Answer: A member of staff, who is independent from the
devel¬opment and testing teams, who observes the testing process
and is involved in signing off the test result record forms for each
test case.
◉ Integration/Module/Link Testing.
Answer: Testing performed to expose faults in the interfaces and in
the interaction between integrated components. This testing phase
is used to identify problems with communications between modules
or units, resource contention, and to verify the system design. This
testing phase takes place after unit testing but before system testing
and may also be termed link or module testing.
FUNDAMENTALS MICRO CERTIFICATION
COMPREHENSIVE STUDY GUIDE WITH
SOLUTIONS
◉ Development Team Leader.
Answer: The member of staff responsible for leading the team
developing the AUT. Liaises with the test team leader to report on
the progress of the development of the AUT and likely dates for
delivery of AUT for testing purposes.
◉ End Users.
Answer: The members of staff who will use the delivered AUT in
support of their work
◉ Equivalence/Partition Class.
Answer: A set of the component's input or output domains for which
the component's behavior is assumed to be the same from the
component's specification. An equivalence class may also be termed
an equivalence partition.
◉ Equivalence Class Testing.
,Answer: A test case design technique for a component in which test
cases are designed to execute representatives from equivalence
classes. This form of testing may also be termed domain or partition
testing.
◉ Error Guessing/ Experienced Based Testing.
Answer: A test case design technique where the experience of the
tester is used to postulate what faults might be present in a
component or AUT, and to design tests specifically to expose them.
◉ Fault Recovery Testing.
Answer: This form of testing verifies that following an error or
exceptions, the AUT is restored to a "normal" state, such as the initial
state of the AUT when it is first executed. This form of testing may
also be used to verify the successful rollback and recovery of the
data used or manipulated by the AUT.
◉ Functional Requirements.
Answer: Traditionally, those requirements for the AUT that have
been specified within the functional specification document for the
AUT. Also see nonfunctional requirements.
◉ Functional Specification.
Answer: A document that describes in detail the characteristics of
the AUT with regard to its intended capability.
, ◉ Functional Testing.
Answer: The process of testing the AUT to verify that it meets its
functional requirements. These requirements are typically recorded
in a requirements specification document.
◉ Incremental Testing.
Answer: A testing technique used in integration testing, where
untested modules are combined with the module under test
incrementally, with the func¬tionality of the module (plus the added
modules) being tested (retested) as each module is added.
◉ Independent Test Observer.
Answer: A member of staff, who is independent from the
devel¬opment and testing teams, who observes the testing process
and is involved in signing off the test result record forms for each
test case.
◉ Integration/Module/Link Testing.
Answer: Testing performed to expose faults in the interfaces and in
the interaction between integrated components. This testing phase
is used to identify problems with communications between modules
or units, resource contention, and to verify the system design. This
testing phase takes place after unit testing but before system testing
and may also be termed link or module testing.
