Can we use analytics cookies? They count visits and form use. We run no ads.

AQA Virtual Summit/MeetupsTest Automation ToolsTypes of Automation Testing

Anastasios Daskalopoulos – An Easy Approach to Continuous Testing In DevOps

Published 2 March 2022. Updated with a short answer, key takeaways and a FAQ; the talk text is unchanged. Published by Zapple.Tech, founded by the founders of CodeceptJS and Codeception, open-source testing frameworks.

Watch on YouTube
Short answer

In this talk, Anastasios Daskalopoulos, a software tester with 19 years of experience, describes how quality assurance has changed and a simple approach to continuous testing in DevOps. He answers common objections to QA and argues that QA should stay independent.

Key takeaways
  • How the face of QA has changed
  • The constant goals of QA
  • Answers to common objections to QA
  • Continuous testing integration with development
  • Why QA should stay independent

Anastasios Daskalopoulos, a software tester/QA specialist with 19 years of experience, talks about recent changes in software quality assurance and a simple approach to continuous testing in DevOps.

The Changing Face of QA

Simple approaches to quality assurance are the trend today. They are applied by all companies, even those that do not work with DevOps. The main goal of QA is to test a project as thoroughly as possible. It can be made after deployment or even during development.

So what has changed?

  • Testing teams have become smaller. The format of work, in which 40 people work in a small room, is a thing of the past.
  • QA engineers are no longer at the bottom of the development team hierarchy.
  • Testers should now have the skills of developers, and developers should know how to write good tests, not just shift their responsibilities to others.
  • Testers and developers cooperate more.
  • Testing phases can last weeks or even months.
  • The Agile approach has become prevalent.
  • DevOps corporate policy has turned QA from a whim of project managers into an essential stage of development.

The-Changing-Face-of-QA

Despite all these changes, QA has always had the same goals:

  • eliminate or at least minimize bugs in the production environment;
  • evaluate all the risks that may occur in the released software;
  • organize and be responsible for creating test cases;
  • be responsible for communications regarding the system’s quality.

The importance of QA. Obvious or not?

It would seem that the need for professional testing is obvious. But not for everyone. We often face objections to QA. Below we will consider all the most common objections and immediately refute them.

QA takes too long

With continuous testing integration, QA is maintained simultaneously with development without delaying the team.
Time is money (you have to pay for testing)

The-importance-of-QA.

Fixing bugs during development is much cheaper than fixing them after the product release.

“Bugs still appear, so why worry about testing?”
This problem can be solved by risk-based testing, which allows you to identify and eliminate most defects.

“I don’t want to do this. If the end-user reports a problem, we will fix it.”
Poor software is the biggest blow to a company’s credibility.

Conclusion

To summarize, let’s draw attention to 2 points. First, do not neglect automated testing: a well-trained automated testing engineer can find and fix problems better and faster than a regular tester. According to statistics, 10-33% of all problems are detected with automated testing.

And secondly, QA must be independent and maintained solely by QA engineers. After all, developers have their core tasks to solve, so performing all the work on their own does not make any sense.

Questions about this talk

How has QA changed?

Anastasios Daskalopoulos says testing teams have become smaller, QA engineers are no longer at the bottom of the hierarchy, testers and developers cooperate more, and each needs some of the other's skills. Agile has become prevalent, and DevOps policy has made QA an essential stage of development.

How do you answer the objection that QA takes too long?

In his talk, Anastasios Daskalopoulos says that with continuous testing integration, QA runs alongside development without delaying the team. On cost, he argues fixing bugs during development is much cheaper than after release, and he suggests risk-based testing to catch most defects.

Should developers do all the testing?

No, according to Anastasios Daskalopoulos. He concludes that QA must be independent and maintained by QA engineers, since developers have their own core tasks. He also says not to neglect automated testing, citing a statistic that 10 to 33 percent of problems are detected by it.

Request a QA audit quote

Tell us what you ship and what worries you.

What happens after you send this

  1. You send the form: your situation and what you need tested, then your name and work email.
  2. Within one business day, we reply with a suggested first step, its scope, timeline and a quote.
  • Fixed scope
  • You decide after each step
  • The tests live in your repository
  • An NDA signed before access

“They helped us to close the positions and consult our team how to proceed further. High-quality quick feedbacks with the deep checking of the required tasks, professional approach, great understanding of the company's technologies and product, detailed reports.”

Kristina Lavrentieva, Manager at keepgo.com, Israel
  • Rated 4.9 out of 5 on Clutch, from 7 client reviews
  • 42 completed test automation and infrastructure projects
  • Founded by the founders of CodeceptJS and Codeception, open-source testing frameworks

Request a QA audit quote

    What is closest to your situation?
    Optional. The product, the platforms, how often you release, what broke last.

    You decide after our reply whether to go ahead.

    Prefer to talk first? Book a call

    One-week QA audit · written report

    Request a QA audit quote