Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 6 Transitioning Manual Testing To An Automated Environment (6…
Chapter 6
Transitioning Manual Testing To
An Automated Environment
(6 Points)
[5]
6.1
Criteria for Automation
6.1.2 (K2)[1]
Factors in transitioning
Availability of tools in the test environment for automation
Correctness of test data and test cases
Scope of the test automation effort
Pilot test
Education of test team to the paradigm shift
Roles and responsibilities
Cooperation between developers and TAE
Parallel effort
create a parallel team to automate
Compare manual/automation
Test automation reporting
6.1.1 (K3)[1]
Criteria for automate
Frequency of use
Complexity to automate
Compatibility of tool support (Test Automation Tools/SUT)
Maturity of test process
the process must be structured
Suitability
of test automation for the stage of the product cycle life
not recommended
nearing to end
early stages of software
of the automated test environment
test automation flexibility to change
Controllability of the SUT
KeyWords
Confirmation testing
Test to verify that a defect no longer exists
Regression testing
6.2.1 (K2)[1]
Automate Regression
Testing
Questions?
Execution
Time
Frequency
Tests
Share data
Avoid duplication of data
functional overlap between tests
Dependencies between tests
Preconditions to run tests
Automate also
must be executed successfully
manually to begin the conversion
SUT
% coverage
Large regression test sets
Run only part of the test set
based on
risk analysis (changed lately??)
Factor to Consider When
Implementing Automation
6.4.1 (K2)[1]
Of Confirmation Testing
Can be added to the regression test suite
Ensure that new defects have not been
introduced as side effect of the defect fix
6.3.1 (K2)[1]
New Feature
Evaluate
TAS
changes
TAA
Testware
Testability