Difference between revisions of "INADEQUATE REVISION CONTROL"

From Test Automation Patterns
Jump to navigation Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................")
 
 
(One intermediate revision by the same user not shown)
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="font-family: Arial; font-size: 16px">Issue Summary</span>=
+
=<span style="font-family: Arial; font-size: 16px">'''Issue Summary'''</span>=
<br /> <span style="font-size: 16px">Test automation scripts are not consistently paired to the correct version of the Software Under Test (SUT)</span>
+
<span style="font-size: 16px">Test automation scripts are not consistently paired to the correct version of the Software Under Test (SUT)</span>
=<span style="font-size: 16px">Category</span>=
+
=<span style="font-size: 16px">'''Category'''</span>=
<br /> <span style="font-size: 16px">Process </span><br /> <br />  
+
<span style="font-size: 16px">Process </span><br />  
=<span style="font-family: Arial; font-size: 16px">Examples</span>=
+
=<span style="font-size: 16px">'''Examples'''</span>=
<br /> <span style="font-size: 16px">There is no revision control for the automated scripts, so that it's not possible to run tests for different versions of the SUT</span><br /> <span style="font-size: 16px">There is no revision control, not even for the SUT</span><br /> <br />  
+
<span style="font-size: 16px">There is no revision control for the automated scripts, so that it's not possible to run tests for different versions of the SUT</span><br /> <span style="font-size: 16px">There is no revision control, not even for the SUT</span><br />  
=<span style="font-family: Arial; font-size: 16px">Questions</span>=
+
=<span style="font-size: 16px">'''Questions'''</span>=
<br /> <span style="font-family: Arial; font-size: 16px">Does development have revision control?</span><br /> <span style="font-size: 16px">Who manages revision control? Development?</span>
+
<span style="font-family: Arial; font-size: 16px">Does development have revision control?</span><br /> <span style="font-size: 16px">Who manages revision control? Development?</span>
=<span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>=
+
=<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>=
<br /> <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br />  
+
<span style="font-family: Arial; font-size: 16px">Most recommended:</span><br />  
 
+
* <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]: Use good development practices for test code; the same as developers (should) use for production code</span>
* <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]</span>
+
* <span style="font-size: 16px">[[SHARE INFORMATION]]: Ask for and give information to managers, developers, other testers and customers</span>
* <span style="font-size: 16px">[[SHARE INFORMATION]]</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 08:04, 27 June 2018

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

Issue Summary

Test automation scripts are not consistently paired to the correct version of the Software Under Test (SUT)

Category

Process

Examples

There is no revision control for the automated scripts, so that it's not possible to run tests for different versions of the SUT
There is no revision control, not even for the SUT

Questions

Does development have revision control?
Who manages revision control? Development?

Resolving Patterns

Most recommended:

  • GOOD DEVELOPMENT PROCESS: Use good development practices for test code; the same as developers (should) use for production code
  • SHARE INFORMATION: Ask for and give information to managers, developers, other testers and customers

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