Search results

Page title matches

Test Automation Issues Mind Map
Back to [[Test Automation Issues]] [[Image:Test_Automation_Issues.jpeg|800px|Test Automation Issues|link=https://testautomationpatterns.org/wiki/images/thumb

343 bytes (48 words) - 15:39, 27 March 2019
PT-Test Automation Issues
...estão relacionados ao modo de trabalho, como '[[LATE TEST CASE DESIGN|LATE TEST CASE DESIGN(ESPECIFICAÇÃO TARDIA DOS CASOS DE TESTE)]]'', ou quando a aut O [[Test Automation Issues Mind Map|Test Automation Issues Mind Map(Mapa Mental de Problemas de Automação de Teste

4 KB (703 words) - 19:55, 14 March 2021
Improve or revive test automation
...ize: 16px">[[ Lack of specific knowledge]] (how to test the Software Under Test (SUT), use a tool, find out how the automation actually works, write mainta # [[ Expectations for automated test execution not met ]](scripts unreliable or too slow, tests cannot run unatt

2 KB (282 words) - 15:44, 11 March 2019
TEST DATA LOSS
.......................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]] Test data isn’t secured so that it has to be generated again and again.

3 KB (377 words) - 09:36, 30 April 2018
Testers think that the Software Under Test is too complex for automation
...don't realize that even automating only a small area of the Software Under Test (SUT) would take away some of their load

890 bytes (138 words) - 14:30, 25 June 2018
Creation or maintenance of test data

608 bytes (84 words) - 14:26, 30 June 2018
Test automators need training

684 bytes (105 words) - 14:01, 24 April 2018
Test Manager
...ng and test automation A test manager is responsible for: * the master test plan

3 KB (348 words) - 07:24, 5 May 2018
Expectations for automated test execution not met
...n style="font-size: 16px">Please select how the expectations for automated test execution have not been met: ...style="font-size: 16px">The current tools cannot drive the Software Under Test (SUT) reliably. See issue ''[[INADEQUATE TOOLS]]'' for help.

924 bytes (131 words) - 10:57, 3 August 2018
LATE TEST CASE DESIGN
.......................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]] ...utomated test cases are designed and written only after the Software Under Test (SUT) has been implemented. There

3 KB (404 words) - 09:44, 2 May 2018
INTERDEPENDENT TEST CASES
........................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]] Test cases depend on each other, that is they can only be executed in a fixed se

2 KB (339 words) - 16:07, 27 June 2018
UNAUTOMATABLE TEST CASES
........................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]] Existing test cases are “unautomatable”

3 KB (366 words) - 14:20, 1 May 2018
Test Automation Patterns
...sentence in a gratuitous sequence, but you must follow rules, so also with test automation patterns you have to follow their natural hierarchy.<br / =Typical test automation patterns:=

6 KB (824 words) - 11:18, 6 July 2018
Test Automation Patterns Mind Map
...lass="wiki" style="display: block">Back to [[Test Automation Patterns]] [[Image:Test_Automation_Patterns.jpeg|800px|Test Automation Patterns|link=https://testautomationpatterns.org/wiki/images/thu

347 bytes (45 words) - 15:34, 27 March 2019
Test Automation Issues
...task that has to be done when automating and for this case there are also test automation patterns to help execute the task as efficiently as possible.</s ='''Typical test automation issues'''=

3 KB (519 words) - 01:51, 11 March 2021
NO PREVIOUS TEST AUTOMATION
...................[[Main Page]] / Back to [[Management Issues]] / Back to [[ Test Automation Issues]] ...tart automating tests, but neither you nor your team has any experience in test automation and it hasn’t ever been implemented in the company, or it was

4 KB (627 words) - 16:44, 7 May 2018
UNATTENDED TEST EXECUTION
...................[[Main Page]] / Back to [[Execution Patterns]] / Back to [[Test Automation Patterns]] In order to support unattended test execution you must set up a supporting infrastructure. Some suggestions:</s

4 KB (518 words) - 16:05, 21 August 2018
TEST SELECTOR
........................[[Main Page]] / Back to [[Design Patterns]] Back to [[Test Automation Patterns]] ...turn on various selection criteria for whether or not you include a given test in an execution run.

6 KB (823 words) - 15:59, 21 August 2018
TEST AUTOMATION FRAMEWORK
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] Use a test automation framework.

5 KB (689 words) - 15:59, 21 August 2018
TEMPLATE TEST
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] ...e a template test case as a standard from which you can drive all kinds of test case variations.

3 KB (366 words) - 15:58, 21 August 2018

Page text matches

ONE-CLICK RETEST
...................[[Main Page]] / Back to [[Execution Patterns]] / Back to [[Test Automation Patterns]] Retesting a specific test case should be as easy as one mouse click

14 KB (1,827 words) - 16:04, 21 August 2018
MODEL-BASED TESTING
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] ...rom a model of the Software Under Test (SUT), typically using an automated test case generator.

10 KB (1,593 words) - 15:56, 21 August 2018
THE NIGHT TIME FALLACY
...ts and don’t have to be that diligent about what tests to add and how much test time these tests take. This beh ...e tests are added to the Nightly Run. Eventually, you run out of night and test runs continue into the day, the next night etc.

10 KB (1,643 words) - 16:17, 21 August 2018
AUTOMATION ROLES
................[[Main Page]] / Back to [[ Management Patterns]] / Back to [[ Test Automation Patterns]] Test automation needs many different skills, and people to take different roles.

7 KB (1,091 words) - 14:45, 21 August 2018
SET STANDARDS
.....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[Test Automation Patterns]] ...tes: the names should convey what kind of test cases are contained in each test suite.

12 KB (1,762 words) - 14:41, 21 August 2018
FRESH SETUP
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] Before executing, each test prepares its initial conditions from scratch. Tests don’t clean up afterw

8 KB (1,256 words) - 09:40, 4 October 2018
TOOL MUSHROOMING
...39;sans-serif'; font-size: 16px">A small test tool evolves into a full test framework without ever going through proper scoping and architecture phases ...style="font-size: 16px">Look out for this failure pattern when you develop test tools in-house

15 KB (2,308 words) - 16:17, 21 August 2018
Design Patterns
...lock">Design patterns show how to design the test automation testware so that it will be efficient and easy to maintain. Capture a manual test with an appropriate tool and replay it to run the test again. 

8 KB (1,150 words) - 13:05, 30 April 2018
AUTOMATE WHAT'S NEEDED
.....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[Test Automation Patterns]] ...e it means the same lines of code get executed thousands of times, and the test suite takes so long that it doesn’t get used) – the aim should be to ma

16 KB (2,442 words) - 10:19, 24 February 2019
Discussions and Challenges
...Apr 2013?) by Gerard Meszaros, author of "xUnit Test Patterns: Refactoring Test Code" (see [[References]]), and some email discussion that followed. ...s on all these kind of issues and it wouldn’t be much help for testers and test automators to look for answers in lots of different books.

8 KB (1,408 words) - 14:21, 26 April 2018
SHARED SETUP
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] ...and other conditions are set for all tests before beginning the automated test suite.

7 KB (1,030 words) - 15:57, 21 August 2018
TEST THE TESTS
.....................[[Main Page]] / Back to [[Process Patterns]] / Back to [[Test Automation Patterns]] Test the scripts just as you would test production code.

7 KB (1,072 words) - 14:43, 21 August 2018
RIGHT INTERACTION LEVEL
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] ...aware of the interaction level of the test approach on the Software Under Test (SUT) and its risks (intrusion) 

6 KB (947 words) - 15:57, 21 August 2018
TESTWARE ARCHITECTURE
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] ...ed to be made known to the tools, for example, when tests are to be run or test results are reported. This makes the job of interacting with the tools simp

6 KB (1,014 words) - 15:59, 21 August 2018
COMPARISON DESIGN
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] Design the comparison of test results to be as efficient as possible, balancing Dynamic and Post-Executio

5 KB (749 words) - 10:19, 22 February 2019
INDEPENDENT TEST CASES
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] Make each automated test case self-contained

4 KB (660 words) - 15:54, 21 August 2018
ONE CLEAR PURPOSE
......................[[Main Page]] / Back to [[Design Patterns]] / Back to [[Test Automation Patterns]] Each test has only one clear purpose

5 KB (707 words) - 15:56, 21 August 2018
EXPECTED FAIL STATUS
....................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]] ...n you have lost the value of the automated tests. Setting up an additional Test Status (not just Pass or Fail) gives additional benefit from automation and

4 KB (663 words) - 16:03, 21 August 2018
ABSTRACTION LEVELS
.....................[[Main Page]] / Back to [[ Design Patterns]] / Back to [[Test Automation Patterns]] ...d. Another advantage is that you can reuse the technical scripts for other test automation efforts.

7 KB (1,011 words) - 12:08, 7 February 2019
MANUAL MIMICRY
........................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]] ...ound the time and boredom limitations of a human. Just simply taking these test cases and automating them is wasting a huge opportunity to use automation p

7 KB (1,131 words) - 16:10, 27 June 2018

Search results

Page title matches

Page text matches

Navigation menu

Search