NO INFO ON CHANGES
Jump to navigation
Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
Issue summary
Development changes are not communicated to the test automators, or not in good time.
Category
Process
Examples
The following changes in the SUT can have very negative impact on the current automation if they are not communicated timely:
- new development environment
- new programming language
- new operating system
- new GUI-components
- sequence of the windows
- database structure
- database triggers
Questions
Who is in charge of the changes?
Who should be notified? Do the developers know it?
Resolving Patterns
- SHARE INFORMATION: apply this pattern to get rid od this issue once and for all
- SHORT ITERATIONS: With short feedback-cycles eventual problems can be found out earlier and more efficiently
- WHOLE TEAM APPROACH: use this pattern if you use an agile development process. If you haven't gone agile yet, check if it would improve development (and of course also test automation) in your context
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues