Difference between revisions of "INTERDEPENDENT TEST CASES"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
|||
| (2 intermediate revisions 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 [[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-size: 16px">Test cases depend on each other, that is they can only be executed in a fixed sequence</span | + | <span style="font-size: 16px">Test cases depend on each other, that is they can only be executed in a fixed sequence</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-size: 16px">Test cases must be executed in a fixed sequence because the preceding test cases create the initial conditions for the following ones.</span | + | <span style="font-size: 16px">Test cases must be executed in a fixed sequence because the preceding test cases create the initial conditions for the following ones.</span> |
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | ||
| − | <span style="font-size: 16px">Who designed the test cases, and for what purpose? Are manual test cases being automated "as is"?</span><br /> <br /> <span style="font-size: 16px">If so, this can cause problems, because what makes sense for manual testing may not be the most appropriate solution for automated tests, particularly the dependencies of tests on each other. If one of a sequence of manual tests fails, the tester can usually find a way to continue testing, possibly by inserting the data that should have been produced by the failing test. But the tool will simply be "stopped in its tracks" by a failing test - it's not possible or practical to anticipate all possible ways that all tests can fail so that an automated solution can be implemented.</span><br /> <br /> <span style="font-size: 16px">See also ''[[MANUAL MIMICRY]]'' - an issue describing what happens when you try to automate manual tests too literally.</span | + | <span style="font-size: 16px">Who designed the test cases, and for what purpose? Are manual test cases being automated "as is"?</span><br /> <br /> <span style="font-size: 16px">If so, this can cause problems, because what makes sense for manual testing may not be the most appropriate solution for automated tests, particularly the dependencies of tests on each other. If one of a sequence of manual tests fails, the tester can usually find a way to continue testing, possibly by inserting the data that should have been produced by the failing test. But the tool will simply be "stopped in its tracks" by a failing test - it's not possible or practical to anticipate all possible ways that all tests can fail so that an automated solution can be implemented.</span><br /> <br /> <span style="font-size: 16px">See also ''[[MANUAL MIMICRY]]'' - an issue describing what happens when you try to automate manual tests too literally.</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">Most recommended:</span><br /> | <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | ||
| − | + | * <span style="font-size: 16px">[[FRESH SETUP]]: use this pattern to initialize each test case independently</span> | |
| − | * <span style="font-size: 16px">[[ FRESH SETUP]]</span> | + | * <span style="font-size: 16px">[[INDEPENDENT TEST CASES]]: this pattern is the best solution for this issue</span> |
| − | * <span style="font-size: 16px">[[ INDEPENDENT TEST CASES]]</span> | + | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span> |
| − | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span | ||
Latest revision as of 16:07, 27 June 2018
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
Issue Summary
Test cases depend on each other, that is they can only be executed in a fixed sequence
Category
Design
Examples
Test cases must be executed in a fixed sequence because the preceding test cases create the initial conditions for the following ones.
Questions
Who designed the test cases, and for what purpose? Are manual test cases being automated "as is"?
If so, this can cause problems, because what makes sense for manual testing may not be the most appropriate solution for automated tests, particularly the dependencies of tests on each other. If one of a sequence of manual tests fails, the tester can usually find a way to continue testing, possibly by inserting the data that should have been produced by the failing test. But the tool will simply be "stopped in its tracks" by a failing test - it's not possible or practical to anticipate all possible ways that all tests can fail so that an automated solution can be implemented.
See also MANUAL MIMICRY - an issue describing what happens when you try to automate manual tests too literally.
Resolving Patterns
Most recommended:
- FRESH SETUP: use this pattern to initialize each test case independently
- INDEPENDENT TEST CASES: this pattern is the best solution for this issue
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues