DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 967,611 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Cover image for Ebook - Scaling functional test automation for happy teams
Mathilde Lelong for Agilitest

Posted on

Ebook - Scaling functional test automation for happy teams

1. From manual to automated tests

a. The organization of manual tests teams – V-cycle
For many years, software was mainly developed with a V-cycle methodology. As a reminder, the V-cycle is a project organization model that is characterized by a flow of activity that details the product until its realization and a flow that assembles the product by checking its quality.

Image description

In this model, the further upstream the steps are, the later the validation of the step. This observation was made by experts who wanted to implement β€˜Shift Left’, which is used to detect anomalies as early as possible, by implementing processes such as reviews. As a reminder, reviews are processes for verifying written deliverables that can be adapted to a wide range of subjects such as code, specifications, scripted tests…

In addition to late testing, the V-Cycle offers other problems. The delivery cycles are long and thus limit the number of deliveries per year (often between one and four). The specific test β€˜phases’ also take place in a very punctual manner. Another issue arises with SUTs (System Under Test) that have many changes to test, with many requirements, leading to test campaigns that can last several weeks.

This V-cycle method gives the advantage to manual testing. Testing teams working in V-cycle spend a lot of time preparing a campaign with design and test writing phases. After that, the testing campaign can begin, after the software has been delivered. As this test campaign can be long, a follow-up is regularly set up to have intermediate assessments. At the end of the campaign, the test team moves on to another topic, such as preparing a new campaign for a different SUT.

The test loads on a particular SUT are therefore not at all smoothed out with the V-cycle method. However, a good understanding of the business, the ability to understand the specifications and to design the tests are a must. In V-Cycle, there is much less room for error compared to the Agile method, where a new version can be delivered very quickly.

This methodology has trained testers to be highly skilled in the art of understanding the business, implementing strategies around RBT (Risk Based Testing) and designing quality tests. Testers who are used to the V-cycle have not generally been asked to work on test automation. Indeed, there are few campaigns that are regularly enough executed to be considered repetitive and require automation.

b. Challenges faced by manual tests
Download and read this book for free here.


In this book

Contents

  1. From manual to automated tests
    a. Organizations of team doing manual tests - V-cycle
    b. Challenges faced by manual tests
    c. How to reorganize teams to allow test automation

  2. From test automation to smart test automation
    a. Identify which tests to automate
    b. How to implement continuous testing
    c. What you can achieve by testing frequently (happy teams)

  3. Finding the right tools
    a. How to find the right test automation tool
    b. Next steps: building your test automation strategy

Top comments (0)

🌚 Friends don't let friends browse without dark mode.

Sorry, it's true.