Search results

Page title matches

• INDEPENDENT TEST CASES
  ......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]]</span> <span style="font-size: 16px">Make each automated test case self-contained</span>
  4 KB (660 words) - 15:54, 21 August 2018
• TEST AUTOMATION OWNER
  .................[[Main Page]] / Back to [[ Management Patterns]] / Back to [[Test Automation Patterns]]</span> <span style="font-size: 16px">Appoint an owner for the test automation effort. If there is already a "champion" give him or her public
  3 KB (467 words) - 14:51, 21 August 2018
• TEST AUTOMATION BUSINESS CASE
  .................[[Main Page]] / Back to [[Management Patterns]] / Back to [[ Test Automation Patterns]]</span><br /> ...siness case as for any other project, but provide also factors typical for test automation</span>
  7 KB (1,159 words) - 14:51, 21 August 2018
• TEST THE TESTS
  .....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 16px">Test the scripts just as you would test production code.</span>
  7 KB (1,072 words) - 14:43, 21 August 2018

Page text matches

• RIGHT TOOLS
  ..................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span> ...long as a tool is workable in your context. The other factors involved in test automation are usually much more important and influential than the choice
  9 KB (1,425 words) - 14:49, 21 August 2018
• TEST SELECTOR
  ........................[[Main Page]] / Back to [[Design Patterns]] Back to [[Test Automation Patterns]]</span> ...turn on various selection criteria for whether or not you include a given test in an execution run.</span>
  6 KB (823 words) - 15:59, 21 August 2018
• KILL THE ZOMBIES
  .....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[Test Automation Patterns]]</span> ...style="font-size: 16px">Regularly delete or archive test cases, scripts or test data that are not used. Make sure that tests are actually testing something
  4 KB (636 words) - 14:38, 21 August 2018
• MANAGEMENT SUPPORT
  ..................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 16px">This pattern is applicable when test automation is intended to be used by many people within an organisation.</s
  7 KB (1,034 words) - 14:47, 21 August 2018
• SET CLEAR GOALS
  ..................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span> ...ou need to know what your objectives and goals are when you first consider test automation, when an automation initiative is getting started, when your aut
  9 KB (1,283 words) - 14:50, 21 August 2018
• DATA-DRIVEN TESTING
  ......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]]</span> <span style="font-size: 16px">Write the test cases as scripts that read their data from external files</span>
  7 KB (1,030 words) - 15:52, 21 August 2018
• SPECIFIC COMPARE
  ......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]]</span><br /> ...case so changes to objects not processed in the test case don't affect the test results</span>
  3 KB (505 words) - 15:58, 21 August 2018
• GOOD DEVELOPMENT PROCESS
  ....................[[Main Page]] / Back to [[ Process Patterns]] / Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 16px">Use a good development process for test code; the same as developers (should) use for production code.</span>
  7 KB (1,103 words) - 10:27, 24 February 2019
• Management Issues
  ...ary support or resources to the automation team or team members are new to test automation. Problems can also be caused by unrealistic expectations. The ta | <span style="font-size: 16px">Management wants to maximize ROI from the test automation project, but is not prepared to invest adequately</span><br />
  5 KB (779 words) - 13:01, 30 April 2018
• GOING FOR THE NUMBERS
  ...eam is pushed into automating as many tests as possible while disregarding test robustness</span><br /> <br /> <span style="font-size: 16px">This failure p ...t can get to the point that more time is wasted on analyzing and debugging test results than would have been invested in just running the tests manually. <
  6 KB (1,043 words) - 13:17, 4 July 2018
• References
  ...team, they learn to solve their problems (most of them) through using the test automation patterns. As we get to know the people on the team, we see how t <span style="font-size: 16px">For unit-level test automation patterns, see xUTP below and http://xunitpatterns.com</span><br
  7 KB (1,043 words) - 15:58, 23 October 2022
• MAINTAIN THE TESTWARE
  .....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 16px">Maintain test automation scripts and test data regularly and from the very beginning.</span>
  5 KB (847 words) - 10:48, 8 January 2019
• TEST AUTOMATION BUSINESS CASE
  .................[[Main Page]] / Back to [[Management Patterns]] / Back to [[ Test Automation Patterns]]</span><br /> ...siness case as for any other project, but provide also factors typical for test automation</span>
  7 KB (1,159 words) - 14:51, 21 August 2018
• Process Issues
  ...16px">Process issues list the test automation problems that occur when the test automation process has not yet been established or hasn’t yet reached the ...font-size: 16px">Testers don’t know what automation could deliver and the test automation team doesn’t know what testers need </span><br /> <span style=
  5 KB (717 words) - 13:00, 30 April 2018
• Test Manager
  ...ng and test automation</span><br /> <br /> <span style="font-size: 16px">A test manager is responsible for:</span><br /> * <span style="font-size: 16px">the master test plan</span>
  3 KB (348 words) - 07:24, 5 May 2018
• DOCUMENT THE TESTWARE
  ....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[ Test Automation Patterns]]</span> <span style="font-size: 16px">Document the automation scripts and the test data.</span>
  5 KB (662 words) - 17:35, 19 September 2018
• WHOLE TEAM APPROACH
  .....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[Test Automation Patterns]]</span> ...16px">Testers, coders and other roles work together on one team to develop test automation along with production code.</span>
  5 KB (716 words) - 15:42, 2 February 2019
• VISUALIZE EXECUTION
  ...................[[Main Page]] / Back to [[Execution Patterns]] / Back to [[Test Automation Patterns]]</span> <span style="font-size: 16px">When running tests display which test case is currently executing</span>
  3 KB (439 words) - 16:06, 21 August 2018
• TOOL-DRIVEN AUTOMATION
  .......................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span> ..."font-size: 16px">Test cases are automated using “as is” the features of a test automation tool </span>
  4 KB (548 words) - 09:23, 26 June 2018
• Main Page
  ...r: #000080;font-size: 38px;margin-bottom: 20px;display: block;">Welcome to Test Automation Patterns Wiki</span> ===<span style="font-size: 20px">About the Test Automation Patterns Wiki:</span>===
  6 KB (879 words) - 10:28, 24 October 2022

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)