Photo by on Chunlea Unsplash True stories about quality and false solutions. Cet article est également disponible en français . Far be it from me to disavow the usefulness of test automation. Yet, too often the topic is discussed from the wrong angle. Here are some examples! I am a strong advocate of test automation. We need help to get started with test automation! A team seeks my advices as a . They don’t control regressions. They come to me so that I can help them to define a test automation strategy. Test Facilitator What do I recommend to them? After having discussed with them to understand the situation, my recommendations are mostly about processes: To be considered valid, a bug fix must come with an automated test which fails without the bug fix. (a unit test can be enough) They suffer from long-lived branches, taking way too much time before merging. Either they switch to another , or they thoroughly review their current branching model and strictly follow it. branching model Their releasing process is not clear and, most of all, they are not really assuming it. When do they check that there is no regression? How? They need to formalize their process and strictly follow it. will we start talking about test automation. … and only when they will have taken care of these essential problems, Automated tests are the answer to all our problems! Ah! I have heard this sentence so many times… Come on we really gotta automate these tests! All our problems will be gone after that. Indeed, , automating these non-regression tests would be a wonderful idea. By the way, this is such a good idea that I’m wondering: why isn’t it done already? yes Still I’m saddened to say you that, , automating tests won’t magically solve all of your problems. no Even with a great non-regression test harness, you’ll have to keep challenging the product. Test automation is awesome. But it’s no silver bullet. Test automation has not marked the demise of manual testing. Even worse, with test automation you are still required to , to set up a , to the product. think strategy use Rigor is enough to fix most problems Hell yes! Nobody cares. Why are we bothering? How boring processes are. Ouch. Yet processes — and following them! — are . As I like to put it: key to a well running team Agile requires to be extremely rigorous. _… And stop behaving like heroes!_hackernoon.com Stop doing Agile under perfusion! And when I’m talking about processes, I am not expecting complex decision diagrams lost into the corporate intranet. No, processes can be simple, visual, understandable… Most of all, . it must fit with how the team works _Comment faire pour que vos process soient plus qu’une doc !_jp-lambert.me Un process est un outil, pas une contrainte Processes > Test Automation Let’s keep it brief. People like talking to me about test automation because they think it is a silver bullet. Unfortunately, it isn’t. Well, would have been a better choice. You should know better by now: silver bullets simply don’t exist. “unsurprisingly” What’s a good automated test? You’re not even close to know if you don’t already know what makes a good manual test. Automating tests cost so much! Where should we start? Well, why not starting with the most critical scenarios… I’m guessing you know them, right? We’re scared of regressions! We have to automate tests. Why are you scared of regressions? If you don’t trust your non-regression test scenarios, automating them will do no good. Have you defined those test scenarios? If you are not running the non-regression test scenarios by hand, then obviously regressions are not that a big deal. Are you sure you’re scared? We don’t have time to automate the tests! If you were wasting your time running the non-regression test scenarios by hand, you would find the time. Calculating the return on investment would be trivial and straightforward. Thus, the situation doesn’t look that bad… Overall, this is what happens: People ask me guidance about quality and non-regression, people want to be told about test automation, my answer is about process and rigor. Just start by reviewing thoroughly your processes, . You can get incredibly far with just that! Take for instance this team that I have helped: and follow them strictly _It was upon a time a team that struggled to release…_jp-lambert.me Our recipe for Daily Releases Liked this article? Show it! 👏 Please clap and share the article! It is because of you that I put my heart and soul into writing. And follow me on my blog to be notified when I publish new articles! Thank you so much!

Quality and test automation: don’t underestimate processes

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Stop doing Agile under perfusion!

The Noonification: The Future of DeFi - Emerging Evolution (11/3/2022)

10 Ways PMs Can Earn The Respect and Trust of Their Team

10 Terms Every Engineer Must Know

10 Subtle Superpowers of DevOps

10 Product Development Traps

Stop doing Agile under perfusion!

The Noonification: The Future of DeFi - Emerging Evolution (11/3/2022)

10 Ways PMs Can Earn The Respect and Trust of Their Team

10 Terms Every Engineer Must Know

10 Subtle Superpowers of DevOps

10 Product Development Traps

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps