Skip to main content


Agile Methods for Automation and Load Testing

I am travelling in our Detroit office today. I am working with our U.S. team to leverage Scrum for automation and load testing on a current project for a client. Typically, this process includes system testing with waterfall, which cannot include Agile methodology. However, it does work for our current project. And I will share with you what our solution is and how it works.

Automation Testing

My U.S. teammates plan to use automation testing to replace manual testing. So I helped them to create a one-month plan for Phase1 development using Agile since we have one team member from our Global Delivery Center in China to work on it onshore.

Week1: Create a sampler by using the automation tool to cover all components testing, including image, URLs, integration and so on.

Week2: Create common components’ framework for automation scripts and integrate with sample’s testing.

Week3: Finish all common components testing.

Week4: Finish smoke testing by calling different common components.

The final goal for phase1 is to create smoke test scripts and integration test scripts which could be executed and get reliable results. But for every single week, we will have Daily stand up, Demo for deliverables, review activities for next week’s plan and ready automation testing scripts. It will help us to control the issues and risk easily. Even if we have to stop the work for automation during this month, we still have several automation test cases that can be used to reduce our current manual testing effort.

Load Testing

For our load testing team, we have one U.S. colleague designated to work on this project from our Detroit office as a lead and then several team members working offshore at our Global Delivery Center in China. We have couple of requests for load testing enhancement.  I discussed with our team lead all of the enhancement including scope, testing strategy, load testing execution and testing results analysis. We wrote down all user stories and prioritized them according to the impact for the client.

I created one planning board in a wiki  as the following to share all kinds of enhancements for load testing.

Then it is easy for both of our teams to share ideas about user stories, task break down and progress.

Every two weeks, our U.S. team lead and GDC offshore team review a task break down and estimation together. Our team will pick up the user stories and track the status in our daily Scrum meeting. Every week, our offshore team will demo the finished enhancements to the US team lead. Though we are working on enhancements for our load testing, I believe the same method can be adapted for load testing as well.

Download our latest whitepaper on Improving the Efficiency and Effectiveness of Software Testing with Automated Testing.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Follow Us