Difference between revisions of "VISUALIZE EXECUTION"
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 [[Execution Patterns]] / Back to [[Test Automation Patterns]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]] / Back to [[Test Automation Patterns]]</span> | ||
| − | =<span style="font-size: 16px">Pattern Summary</span>= | + | =<span style="font-size: 16px">'''Pattern Summary'''</span>= |
<span style="font-size: 16px">When running tests display which test case is currently executing</span> | <span style="font-size: 16px">When running tests display which test case is currently executing</span> | ||
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
<span style="font-size: 16px">Execution</span> | <span style="font-size: 16px">Execution</span> | ||
| − | =<span style="font-size: 16px">Context</span>= | + | =<span style="font-size: 16px">'''Context'''</span>= |
<span style="font-size: 16px">This pattern is helpful when running unattended tests </span> | <span style="font-size: 16px">This pattern is helpful when running unattended tests </span> | ||
| − | =<span style="font-size: 16px">Description</span>= | + | =<span style="font-size: 16px">'''Description'''</span>= |
<span style="font-size: 16px">When executing long-running automated tests it is quite useful to be able to see at a glance which test case is currently executing. To achieve this you should display the test case Id somewhere on the screen </span> | <span style="font-size: 16px">When executing long-running automated tests it is quite useful to be able to see at a glance which test case is currently executing. To achieve this you should display the test case Id somewhere on the screen </span> | ||
| − | =<span style="font-size: 16px">Implementation</span>= | + | =<span style="font-size: 16px">'''Implementation'''</span>= |
<span style="font-size: 16px">Some suggestions:</span><br /> | <span style="font-size: 16px">Some suggestions:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">If you are testing windows in which you have to insert text that is inconsequential for the test case, simply insert the test case id.</span> | * <span style="font-size: 16px">If you are testing windows in which you have to insert text that is inconsequential for the test case, simply insert the test case id.</span> | ||
* <span style="font-size: 16px">If your test tool or [[TEST AUTOMATION FRAMEWORK]] supports it, write the test case information to some otherwise unused screen area. </span> | * <span style="font-size: 16px">If your test tool or [[TEST AUTOMATION FRAMEWORK]] supports it, write the test case information to some otherwise unused screen area. </span> | ||
<br /> | <br /> | ||
| − | =<span style="font-size: 16px">Experiences</span>= | + | =<span style="font-size: 16px">'''Experiences'''</span>= |
<span style="font-family: Arial; font-size: 16px">from Seretta: One of the applications we test automatically is our portfolio management for insurance policies. Whatever test case we designed, we always needed a partner name as the policy holder, so as a rule the partner’s name is identical with the unique test case id. In this way just glancing at the screen tells us how far the suite has been executed.</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]] / Back to [[Test Automation Patterns]]</span></div> | <span style="font-family: Arial; font-size: 16px">from Seretta: One of the applications we test automatically is our portfolio management for insurance policies. Whatever test case we designed, we always needed a partner name as the policy holder, so as a rule the partner’s name is identical with the unique test case id. In this way just glancing at the screen tells us how far the suite has been executed.</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]] / Back to [[Test Automation Patterns]]</span></div> | ||
Revision as of 09:03, 30 April 2018
.................................................................................................................Main Page / Back to Execution Patterns / Back to Test Automation Patterns
.................................................................................................................Main Page / Back to Execution Patterns / Back to Test Automation Patterns
Pattern Summary
When running tests display which test case is currently executing
Category
Execution
Context
This pattern is helpful when running unattended tests
Description
When executing long-running automated tests it is quite useful to be able to see at a glance which test case is currently executing. To achieve this you should display the test case Id somewhere on the screen
Implementation
Some suggestions:
- If you are testing windows in which you have to insert text that is inconsequential for the test case, simply insert the test case id.
- If your test tool or TEST AUTOMATION FRAMEWORK supports it, write the test case information to some otherwise unused screen area.
Experiences
from Seretta: One of the applications we test automatically is our portfolio management for insurance policies. Whatever test case we designed, we always needed a partner name as the policy holder, so as a rule the partner’s name is identical with the unique test case id. In this way just glancing at the screen tells us how far the suite has been executed..................................................................................................................Main Page / Back to Execution Patterns / Back to Test Automation Patterns