NO INFO ON CHANGES

From Test Automation Patterns
Jump to: navigation, search
.................................................................................................................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:

  1. new development environment
  2. new programming language
  3. new operating system
  4. new GUI-components
  5. sequence of the windows
  6. database structure
  7. 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