How a Manual QA Team Automated 200 Test Cases Without Writing Code

How a Manual QA Team Automated 200 Test Cases Without Writing Code

A small QA team at a logistics software company shows how to automate testing without coding.

A small QA team at a logistics software company recently demonstrated how they could automate a significant portion of their testing process without writing any code.

The Team and Their Challenge

Neha, Tom, and Arun made up the entire QA department. They were tasked with managing 214 test cases documented in their wiki. However, they were only able to automate 9 of these cases, while running 205 manually for each release. Their release cycle took 11 days. The situation was tough, especially when the CTO stated, "We can't hire an automation engineer. The budget is gone, and the good ones take five months to find."

Reframing the Problem

Instead of focusing on how to learn coding or automation frameworks, Neha reframed the question: What knowledge makes their tests valuable? They realized that the information was already documented in their test cases and did not necessarily need to be coded. Each test case included detailed steps and expected outcomes, which could be transformed into automated scenarios.

Prioritizing Test Cases

Before diving into automation, the team audited their 214 test cases. They found that about 60 of these cases accounted for most of the manual testing effort and business risk. This insight led them to focus on automating these high-priority cases first.

Choosing the Right Tool

The team wrote down their requirements for a testing tool before evaluating options. They needed a tool that:

  • Allowed tests to be authored in plain English (no coding required).
  • Covered UI, API, and database checks.
  • Integrated with Continuous Integration (CI) for developer feedback.
  • Maintained itself with minor UI changes.
  • Produced readable reports for non-engineers.

After a short evaluation, they decided to run a pilot using a tool that met these criteria. The setup took only an afternoon, which was much quicker than the months it would take to train on a coding framework.

Automating Test Cases

The team converted their manual test cases into automated scenarios with minimal changes. For example, one test case about reassigning a delayed shipment was transformed from a manual format into a plain-language scenario:

Feature: Shipment reassignment
  Scenario: Dispatcher reassigns a delayed shipment
    Given I am logged in as a Dispatcher
    When I filter the shipment list by "Delayed"
    And I select shipment "SH-2041"
    And I reassign it to a driver with available capacity
    Then the shipment should show the new driver
    And the previous driver's route should no longer include "SH-2041"
    And the customer should receive a delay notification

This approach allowed the testers to automate without needing developers to write code.

Rollout Plan

The team implemented their automation in a phased manner:

  1. Week 1: Audit the 214 cases and pick the top 60.
  2. Week 2: Convert 10 cases and validate against manual runs.
  3. Week 3: Convert 20 more and share a report with developers.
  4. Week 4: Convert 30 more and connect to CI.
  5. Week 5+: Retire manual runs for converted cases and continue converting in batches of 20.

They ensured that each automated test ran alongside its manual counterpart before retiring the manual version.

Lessons Learned

The team faced some challenges along the way:

  • Vague expected results: They learned to specify observable outcomes in their scenarios.
  • Copying manual steps: They realized that automated scenarios should express intent rather than just replicate clicks.
  • Ownership issues: They assigned a rotating role for test triage to ensure accountability.
  • Test data planning: They added steps to ensure necessary data was available for tests.

Results

After implementing their automation, the team saw significant improvements:

  • Automated test cases increased from 9 to 187.
  • Manual regression effort per release dropped from about 5 days to just 1 day.
  • The release cycle time decreased from 11 days to 4 days.
  • They found bugs earlier in the process, which helped improve product quality.

Most importantly, team morale improved. The testers spent less time on repetitive tasks and more time on exploratory testing, which allowed them to find valuable bugs.

Conclusion

This small QA team successfully automated a significant portion of their test cases without writing code. By focusing on their existing knowledge and choosing the right tools, they turned a challenging situation into an opportunity for improvement.

Merits

  • Increased efficiency in testing processes.
  • Reduced manual effort and time spent on regression testing.
  • Improved product quality through earlier bug detection.
  • Enhanced team morale and job satisfaction.

Demerits

  • Initial setup and learning curve for the new tool.
  • Potential challenges in maintaining automated tests as the application evolves.

Caution

This article is educational, and any placeholder values must be replaced with real data. Readers should verify claims against the original source before relying on them.

Frequently asked questions

  • What is manual QA? — Manual QA involves testers executing test cases without automation tools to verify software functionality.
  • How can a small QA team automate tests? — A small QA team can automate tests by using tools that allow them to write tests in plain language without coding.
  • What are the benefits of test automation? — Test automation can increase efficiency, reduce manual effort, and improve product quality by catching bugs earlier.
  • What challenges do QA teams face in automation? — Common challenges include resource constraints, tool selection, and maintaining automated tests.
  • How do you prioritize test cases for automation? — Test cases can be prioritized based on their impact, frequency of use, and associated business risk.
  • What tools can be used for test automation? — Various tools exist that allow for automation without coding, focusing on user-friendly interfaces and integration capabilities.

Tags

#qa #automation #testing #softwaretesting #qualityassurance #testautomation #devops #logistics #teamwork #efficiency

Free field guide

Kubernetes Security Checklist

Harden cluster access, workload identity, pod security, network boundaries, software supply chain, secrets, and operational monitoring.