AQA ProcessAQA Virtual Summit/MeetupsTest Automation Tools

Rafael Cintra – How to design Test Automation as a Service through a QA Platform

Published 3 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, Rafael Cintra, a solution architect focused on quality control and DevOps, explains how to design test automation as a service through a QA platform. He covers three cognitive loads, treating the platform as a product, and three stages: where to start, research and execution, and continuous improvement.

Key takeaways
  • Three cognitive loads and how to simplify automation for testers
  • Platform as a product, with self-service catalogs and knowledge bases
  • Benefits for teams and for the business
  • Where to start: team, roles, permissions, success criteria
  • Research and execution through short experimental cycles, then continuous improvement

Rafael Navarro Cintra is a solution architect focusing on quality control & DevOps and a former Scrum master with vast experience in software development for banks and other large financial institutions. He talks about why automated testing is so important and why it should be done first.

Simplifying automated testing: the psychological aspect

How to make automated testing easier? Let’s talk about the psychological aspect of this task — three cognitive loads. We need to:

  • Simplify the internal cognitive load: the test team should not waste time learning how automated testing works. These tests should be simple, like “I press the button, and it all works.”
  • Reduce external cognitive load: your test and QA team should understand that it may be difficult to learn how the test automation framework works, but it will later help them focus on the main thing, i.e., delivering a quality product to users.
  • Maximize Relevant Cognitive Load: You give your team a framework and all the tools that must be easy to use. It allows your workers to focus their efforts on generating innovative ideas and increasing their work efficiency.

Platform as a Product

unnamed-1

A platform includes self-service API catalogs, tools, services, knowledge bases, and support services. It’s a solid product that testers and QAs really want to use. The main idea is not to force testers to automate processes but to convince them to do it voluntarily.

Goals of Simplifying Test Automation

Simplifying automation allows for significant improvements in flexibility, performance, and quality. Profit for teams:

  • Decreased time spent on tasks that help achieve main goals.
  • Reduced downtime.
  • The possibility to anticipate and prevent future problems.

Business Value:

  • Reduced time to complete tasks.
  • Faster product release and troubleshooting.

Automated Testing as a Service

Automated-Testing-as-a-Service

Let’s say you already have a framework, but you want to know where to go next. Here are 3 main steps: Where to start

  • assemble the team and roles of its members;
  • request and validate permissions;
  • adapt;
  • compare mission and goals;
  • define the criteria of success and the ultimate goal.

Research and execution

  • find your customers and their pain points;
  • refine your initial backlog;
  • use a short experimental cycle;
  • compare, refine, experiment (continuous MVPs).

Continuous improvement

  • define a baseline, what to measure and how;
  • determine your goals;
  • use incremental and continuous cycle.

In the end, instead of building and maintaining a massive framework, you will have an easy-to-understand platform that will 100% pay off in the future.

Questions about this talk

What is test automation as a service?

In Rafael Cintra's talk, it is a QA platform built as a product, with self-service API catalogs, tools, services, knowledge bases and support. The idea is that testers choose to automate because the platform is easy to use, rather than being forced to.

How do cognitive loads relate to test automation?

Rafael Cintra names three: simplify the internal load so testers need not spend time learning how automation works, reduce the external load of learning the framework, and maximize the relevant load so the team can focus on delivering a quality product and on new ideas.

How do you start building a QA platform?

According to Rafael Cintra, start by assembling the team and its roles, requesting and validating permissions, comparing mission and goals, and defining the criteria of success and the ultimate goal. Then find customers and their pain points and run short experimental cycles. Finally define a baseline, set goals and improve in incremental, continuous cycles.

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