This session will cover the important points of getting started with Test Automation before you even select the tool(s) to implement it with. For example, determining why you’re going to automate and what you expect from it; defining what to automate and the different levels and types of tests to automate for the need to be considered. We will talk about the need to evaluate your existing test artifacts and processes. Are test cases written in a clear and consistent manner, are they organized/categorized and prioritized? It is necessary to determine if they are in good enough shape to be used as a guide for the automation work. We will discuss using a project plan for the tool evaluation process and eventual automation implementation and determine what skills/knowledge you need to do this type of work, or how to find someone who has those skills. We will consider such points as to how to ensure the person knows what they are doing and whether he or she will be worth the money you pay them. We will talk about how to work with development to build in ‘testability’ for the system under test and how it helps with implementing automation. And finally, we will discuss how to gain management understanding and buy-in to this process.
The whole discussion will help you to “put the horseback in front of the cart”.
- Things to consider before starting an automation implementation and/or project. What are the pieces of the puzzle you need to put together first?
- How to define what it is you’re going to automate, and how to classify and organize it efficiently. Why are you going to automate and what do you expect from it?
- How and what to plan for to implement the automation project. What are the tasks, resources (people, equipment and data) and timelines for a project plan?
- How to find and recruit people who have the skills/knowledge to do this type of work. How to ensure the person you hire knows what they are doing and will be worth the money you will pay for them.
- How to work with development to build in ‘testability’ to the system under test (SUT). What needs to be done to make the system automation-ready?
- How to convince management that you’re doing the right things in the right order.
Please Note: The presentations are intended for attendees only. The presentations page is password protected – contact firstname.lastname@example.org for verification of attendance and the password to access the presentation.
Jim Hazen – Consultant
Jim Hazen is a veteran of the software testing trenches, and has over twenty five years of experience testing applications. Jim has been involved with the startup of testing at multiple companies and has done consulting work for the last 15 years. He has helped clients implement tools for functional automation, performance testing and test management. He has worked with companies to achieve efficiency gains and financial benefits associated to testing.
Jim Hazen – Consultant
LinkedIn: Jim Hazen
Past Events: STPCon, Software Quality Association of Denver (SQuAD)