As you probably realized from the previous chapters, a test automation project can’t stand on its own. Its life cycle is tightly related to the life cycle of the application that it tests. Like any software project, its existence is only relevant if someone uses it; otherwise it’s worthless. In the case of test automation, the “user” is actually the entire development team. It may seem like the main user is the QA manager or Dev manager, but in fact, they’re not using it themselves for their own good. They may require the fancy reports and tell you what they want you to do (and sometimes ...
© Arnon Axelrod 2018
Arnon AxelrodComplete Guide to Test Automationhttps://doi.org/10.1007/978-1-4842-3832-5_55. Business Processes
Arnon Axelrod1
(1)
Matan, Israel
Get Complete Guide to Test Automation: Techniques, Practices, and Patterns for Building and Maintaining Effective Software Projects now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
