Please enable JavaScript.
Coggle requires JavaScript to display documents.
ISTQB TAE 1.2 SUCCESS FACTORS - Coggle Diagram
ISTQB TAE
1.2 SUCCESS FACTORS
Test Automation Architecture
:house:
Align with SUT
Support functional and non-functional requirements
Maintainability
Performance
Learnability
Involve developers in the design
SUT Testability
:computer:
Designed for automated testing
GUI interaction & data to be decoupled from UI appearance
API testing could require more classes/modules/CLI exposed as public
Target easily testable parts of SUT first
Test Automstion Strategy
:pen:
Address maintainability and consistency of SUT
Consider costs, benefits and risks for old & new parts of SUT
Consider automated testing of both GUI and APIs
Test Automation Framework
:frame_with_picture:
TAF should be:
Easy to use
Well documented
Maintainable
Supports a consistent approach to automation
Ideal TAF comes from:
Implement reporting facilities
Enabling easy troubleshooting
Address test environment appropriately/have a dedicated automation test environment
Document automated test cases
Trace the automated test step by step if necessary
Enable easy maintenance
Keep automated tests up to date
Plan for deployment
Retire tests when needed
Monitor and restore the SUT
Code Maintenance
:lower_left_paintbrush:
Maintenance considerations:
Different tools used
Different types of verification used
Different testware items requiring maintenance
Do nots:
Create code sensitive to interfaces
Create automation sensitive to data changes
Create an automation environment sensitive to context (OS date & time, etc) - use stubs