INADEQUATE TECHNICAL RESOURCES

From Test Automation Patterns

Revision as of 07:05, 5 May 2018 by Seretta (talk | contribs) (Flaky tests in italics)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Jump to navigation Jump to search

................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues

Issue Summary

The technical resources for test automation are insufficient or not appropriate or both

Category

Management

Examples

Sharing machines, databases or network with development or testing causes your automated tests to fail unpredictably (FLAKY TESTS)
The network is so slow that your automated tests take too long to run
You cannot run your tests on the same environments as your customers

Questions

Who is in charge of the technical side of test Automation?

Resolving Patterns

Most recommended:

DEDICATED RESOURCES for example 1
GET ON THE CLOUD for examples 2 and 3

................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues

Retrieved from ‘https://huddletalk.wpengine.com/wiki/index.php?title=INADEQUATE_TECHNICAL_RESOURCES&oldid=648’