Difference between revisions of "NO INFO ON CHANGES"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Topic titles in capital letters) |
||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span> | ||
| − | =<span style=" | + | =<span style="font-size: 16px">'''Issue summary'''</span>= |
| − | + | <span style="font-family: Arial; font-size: 16px">Development changes are not communicated to the test automators, or not in good time.</span> | |
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
| − | + | <span style="font-size: 16px">Process</span> | |
| − | =<span style=" | + | =<span style="font-size: 16px">'''Examples'''</span>= |
| − | + | <span style="font-family: Arial; font-size: 16px">The following changes in the SUT can have very negative impact on the current automation if they are not communicated timely:</span><br /> | |
| − | |||
# <span style="font-family: Arial; font-size: 16px">new development environment</span> | # <span style="font-family: Arial; font-size: 16px">new development environment</span> | ||
# <span style="font-family: Arial; font-size: 16px">new programming language</span> | # <span style="font-family: Arial; font-size: 16px">new programming language</span> | ||
| Line 14: | Line 13: | ||
# <span style="font-family: Arial; font-size: 16px">database structure</span> | # <span style="font-family: Arial; font-size: 16px">database structure</span> | ||
# <span style="font-family: Arial; font-size: 16px">database triggers</span> | # <span style="font-family: Arial; font-size: 16px">database triggers</span> | ||
| − | + | =<span style="font-size: 16px">'''Questions'''</span>= | |
| − | =<span style=" | + | <span style="font-family: Arial; font-size: 16px">Who is in charge of the changes?</span><br /> <span style="font-family: Arial; font-size: 16px">Who should be notified? Do the developers know it?</span><br /> |
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>= | ||
| − | |||
| − | |||
* <span style="font-family: Arial; font-size: 16px">[[SHARE INFORMATION]]: apply this pattern to get rid od this issue once and for all</span> | * <span style="font-family: Arial; font-size: 16px">[[SHARE INFORMATION]]: apply this pattern to get rid od this issue once and for all</span> | ||
* <span style="font-family: Arial; font-size: 16px">[[SHORT ITERATIONS]]: With short feedback-cycles eventual problems can be found out earlier and more efficiently</span> | * <span style="font-family: Arial; font-size: 16px">[[SHORT ITERATIONS]]: With short feedback-cycles eventual problems can be found out earlier and more efficiently</span> | ||
* <span style="font-family: Arial; font-size: 16px">[[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</span> | * <span style="font-family: Arial; font-size: 16px">[[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</span> | ||
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span></div> | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 09:34, 2 May 2018
.................................................................................................................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