Difference between revisions of "LONG SET-UP"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
m (empty lines removed) |
||
| Line 1: | Line 1: | ||
| − | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design 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 [[Design 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>= | ||
| − | <span style="font-family: Arial; font-size: 16px">Set-up of the initial conditions for the test cases is long and complicated </span | + | <span style="font-family: Arial; font-size: 16px">Set-up of the initial conditions for the test cases is long and complicated </span> |
=<span style="font-size: 16px">'''Category'''</span>= | =<span style="font-size: 16px">'''Category'''</span>= | ||
| − | <span style="font-size: 16px">Design</span | + | <span style="font-size: 16px">Design</span> |
=<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= | ||
| − | |||
# <span style="font-family: Arial; font-size: 16px">The initial conditions consist in MS Access databases. Since the structure of the tables can change with every release the original databases have to be updated practically before each run. The update can take hours!</span> | # <span style="font-family: Arial; font-size: 16px">The initial conditions consist in MS Access databases. Since the structure of the tables can change with every release the original databases have to be updated practically before each run. The update can take hours!</span> | ||
# <span style="font-family: Arial; font-size: 16px">The insertion of data in the initially empty databases is rendered difficult by all kinds of triggers</span> | # <span style="font-family: Arial; font-size: 16px">The insertion of data in the initially empty databases is rendered difficult by all kinds of triggers</span> | ||
| − | |||
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | ||
| − | + | <span style="font-family: Arial; font-size: 16px">Do the initial conditions have to be set new for every test? Can they be shared between different tests?</span><br /> <span style="font-family: Arial; font-size: 16px">Can the initial conditions be prepared outside of the automated testing suite?</span><br /> <span style="font-family: Arial; font-size: 16px">Are there tools available to allow conditions/data sets to be prepared outside of the automation suite?</span> | |
=<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"> </span | + | <span style="font-family: Arial; font-size: 16px"> </span><span style="background-color: transparent; color: #000000; font-family: arial,helvetica,sans-serif; font-size: 16px; text-decoration: none">Most recommended:</span><span style="font-family: Arial; font-size: 16px"> </span><br /> |
| − | |||
* <span style="font-size: 16px">[[ CHAINED TESTS]]: use this pattern to have previous tests prepare the initial conditions for the following ones</span> | * <span style="font-size: 16px">[[ CHAINED TESTS]]: use this pattern to have previous tests prepare the initial conditions for the following ones</span> | ||
* <span style="font-size: 16px">[[ SHARED SETUP]]: use this pattern to run the setup only once</span> | * <span style="font-size: 16px">[[ SHARED SETUP]]: use this pattern to run the setup only once</span> | ||
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div> | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 17:20, 7 May 2018
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
Issue summary
Set-up of the initial conditions for the test cases is long and complicated
Category
Design
Examples
- The initial conditions consist in MS Access databases. Since the structure of the tables can change with every release the original databases have to be updated practically before each run. The update can take hours!
- The insertion of data in the initially empty databases is rendered difficult by all kinds of triggers
Questions
Do the initial conditions have to be set new for every test? Can they be shared between different tests?
Can the initial conditions be prepared outside of the automated testing suite?
Are there tools available to allow conditions/data sets to be prepared outside of the automation suite?
Resolving Patterns
Most recommended:
- CHAINED TESTS: use this pattern to have previous tests prepare the initial conditions for the following ones
- SHARED SETUP: use this pattern to run the setup only once
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues