Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 2 Preparing for Test Automation (11 Points) [5] (KeyWords…
Chapter 2
Preparing for Test Automation
(11 Points)
[5]
KeyWords
Testeability
interfaces
availability
support testing
enable
control
observation
is
requirement
non-functional
Driver
Level of Intrusion
Stub
Test Execution Tool
Test Hook
TAM
Other
Functional Testing
Apps features
High Level
2.1.1 (K4)[2]
SUT Factors Influencing TA
SUT
interfaces available
recommended
decomposition of SUT
test in different levels
Thrid party software
Level of intrusion
changes required specifically for automated
size and complexity
simple SUT => simple TAS
recommended
start with simple TAS
plans for the future deployment
planning the TAS
before the TUS is available
architecture
may require different TAS
2.2.1 (K4)[1]
Tool Evaluation and Selection
TAM
is the primary responsable
TAE
task
Assessing
test tools
madurity
opportunities
compatibility with SUT components
cost-benefit
Functional test
automation tools
issues
Test tool
Conflict with other systems
Object GUI could not be captured
huge features set
subutilization
Updates
SUT
impact
change in source code
performance
2.3.1 (K2)[2]
Design for Testability
and Automation
consists
SUT
interfaces
Control
Observability
architecture
clearly defined
all levels
is
good test automation approach