SUT REMAKE

From Test Automation Patterns
Revision as of 14:29, 1 May 2018 by Seretta (talk | contribs) (Topic titles in capital letters)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues

Issue Summary

Substantial changes are being made to the SUT or it is to be rewritten from scratch

Category

Management

Examples

Changes to the SUT can be for instance:

  1. New development technology
  2. Substitution of known components with new ones
  3. Changed navigation
  4. Changed database structure
  5. Localization

Questions

Are the current tools still usable?
Does development communicate what is being changed?

Resolving Patterns

Most recomended:

  • DO A PILOT: Use this pattern to find out if the current tools and automation strategies are still valid (recommended if your issue is similar to Example 1).
  • WHOLE TEAM APPROACH: If you have to automate a completely new SUT (Example 1) and the development team has adopted an agile process this is the pattern of choice.
  • ABSTRACTION LEVELS: if you have to substantially rework your scripts, use this pattern on all the scripts you have to touch: you will have much less work when such changes happen again.


Other useful Patterns:

  • LEARN FROM MISTAKES: this pattern helps you learn from your current experience how to do better.
  • MANAGEMENT SUPPORT: Apply this pattern to get the support you need in order to use other patterns.
  • SHARE INFORMATION to learn what will be changed and to inform development when changes disrupt automation scripts

................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues