There’s no denying that the world is in constant flux. Thanks to the web, automation, and the data processing abilities of modern computers, the border between humans and machines has become fuzzy. How does it affect IT and QA testing in particular? And finally, which QA skills make great QA testers well, great?
The ideal set of QA skills
As we become more dependent on AI and automation, the role of QA testers has changed too. Does an ideal QA tester even exist? Probably not. However, here are the QA skills commonly shared by great QA testers:
- Database skills – the ability to check or extract data from databases without anyone’s help
- Coding skills – understanding source code and looking for edge cases more efficiently
- The ability to write automation tests using Geb or RestAssured which allow the tester to assess the user interface as well as the API
- The ability to look through logs, or even use SSH to log in to a server, analyze changes in code, and find the reason why the error occurs. That is not to say testers should be able to analyze problems with transactions or race-condition issues. Still, being able to find a missing exclamation mark in the if statement is definitely a benefit
- The ability to run a business analysis of requirements or perhaps even take responsibility for them
Do monkeys have QA skills?
I’ve heard mixed opinions about the role of manual testers. Some people believe the role could easily be filled by trained monkeys. Others think the job requires a specific set of skills.
Where does the truth lie?
As usual, as with all IT-related things, in the middle.
Some people think that testing can be carried out by your average app users. They believe that hiring 20 junior testers is just as good as using Amazon Mechanical Turk. The question is, can “random” clicking through an app to find problems be effective? I really doubt that. Although it can cover positive paths (as this is how most people use apps), some serious mistakes will likely remain undetected. We could very well ask our kids to do that, right?
QA skills in action
A good QA tester has great, very specific analytical skills. Good testers are inquisitive and look for problems, or nitpick, if you like.
Currently, analysts usually don’t get involved in IT projects. For that reason, some of their responsibilities have been taken over by testers. That’s because QA skills involve being inquisitive about requirements and questioning them all the time.
Let me explain this using a hypothetical conversation between a QA tester, a customer, and a software developer. When looking at a simple requirement, say “free delivery when ordering 5 books,” the software developer sees a simple “if” statement. If the number of books equals 5 or more, set delivery cost to 0. End of story.
A good tester is likely to say: “That’s a very short requirement. It doesn’t even cover most of the scenarios.” And then they start asking uncomfortable questions.
TESTER: “What if only 2 of the books ordered are currently in stock? And the remaining three will be sent in a second parcel? Are both parcels eligible for free delivery?”
CUSTOMER: “Erm, no. A total of five books has to be delivered in one parcel.”
SOFTWARE DEVELOPER: “That’s another “if” right there.”
TESTER: “What if I order a dishwasher and five books? Does my order qualify for free delivery?”
CUSTOMER: “No, of course not. The offer is only valid if you’re ordering books.”
SOFTWARE DEVELOPER: “Excuse me, that’s another ‘if’”
TESTER: “What if I get 4 ebooks and one book?”
CUSTOMER: “The offer is only valid for printed books.”
SOFTWARE DEVELOPER: “I think we might need to do the estimations again.”
As you see, the QA testers and software developers have different mindsets and different skill sets. For that reason, it’s impossible for developers to take over QA in entirety.
Will computers take over QA testing?
It now takes next to no time to go from building a package to taking it to production, as little as a 15 to 60 minutes. This practically rules out a manual quality assessment. In the past, testing large projects took weeks. There’s no way to compress that into a couple of hours unless testing is automated.
How can computers help with testing? Well, all regression tests are repetitive and when it comes to repetitive tasks, computers come with their own benefits. They’re fast, reliable, and consistent. They don’t make mistakes. After all, to err is to be human, right?
Machines don’t have bad days. And they’re never hungover. It’s also easier to estimate how long it will take them to complete a task.
Who should build automated tests?
Automating testing really is the way forward. Therefore, the right question to ask at this point is who should build automated tests? I believe they should be built by testers who have both QA skills and at least basic coding skills, with an emphasis on the former.
In fact, this desirable skill set usually follows a common career path:
Manual tester -> Automation tester -> Software developer
The shift towards software development is often caused by burnout or salary dissatisfaction (which is slowly becoming less of an issue as employers are starting to value good test engineers). That said, I believe the first transition from manual to automated testing is mandatory.
Many testers are able to write queries for relational and non-relational databases. The next step is to learn basic coding skills. There are a number of resources which allow people to learn Python, Java or Groovy. There are free and paid courses, tutorials, conference presentations, books, ebooks… You name it.
Creating a comfortable acceptance testing framework for a project requires many more skills and much more experience than you need to write scenarios with it. Great testers keep learning to expand their perspective and are also naturally inquisitive. This makes them the best people to build the frameworks. It’s that unique combination of skills and qualities which makes them so valuable.
Without a doubt, automation will take over some of the work of QA testers. The important thing though is it will complement humans, not become a substitute for them. In essence, it will free testers so that they can focus on the human (creative) part of the job. This way, they can focus on the overall product quality rather than “just” remove bugs.
Testing QA skills
Tests assessing QA skills are based on a simple principle – the candidates get a fully functional system with a set of business requirements. They need to write tests to prove that the system meets all of these requirements. We then check that those tests are able to catch all potential bugs introduced to the system.
If you want to start testing QA skills, I have great news for you. We’ve just released our tests assessing QA skills. You can find them below and in our catalogo dei test di codifica:
- Competenze testate
- Durata
- 85 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di .NET, .NET Core, ML.NET, QA, Testing, xUnit, NUnit
Lacune nel codice
valutare la conoscenza di NUnit, QA
Attività di programmazione - Livello: Medio
QA | .NET | NUnit | Tests for Document Management System API - Implement an NUnit test that checks business requirements for a Documents API for a Document Management System
- Competenze testate
- Durata
- 64 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di JUnit, QA
Lacune nel codice
valutare la conoscenza di JUnit, JUnit4, QA, JUnit 5, Java
Attività di programmazione - Livello: Medio
QA | JUnit | ATM Service | Authentication and deposit validation - Write test cases to verify the Automated Teller Machine (ATM) software.
- Competenze testate
- Durata
- 66 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di QA, Testing, Unit-Testing, Manual Testing
Lacune nel codice
valutare la conoscenza di JUnit 5, Java, QA
Attività di programmazione - Livello: Medio
QA | JUnit | ATM Service | Authentication and deposit validation
- Competenze testate
- Durata
- 36 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di .NET, NUnit, QA
Lacune nel codice
valutare la conoscenza di NUnit, QA
Attività di programmazione - Livello: Facile
QA | .NET, NUnit | Coffee machine software unit tests - Write thetests in the
NUnitExercise.Tests/CandidateTests.csclass to verify theCoffeeMachineMainclass.
- Competenze testate
- Durata
- 48 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di QA, Selenio, .NET, C#
Lacune nel codice
valutare la conoscenza di Java, QA, Selenio
Attività di programmazione - Livello: Medio
QA | .NET, Selenium | Data extraction - Implement methods in class SeleniumTask.SeleniumExecutor to pass successfully all tests.
- Competenze testate
- Durata
- 51 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di .NET, NUnit, QA
Lacune nel codice
valutare la conoscenza di NUnit, QA
Attività di programmazione - Livello: Difficile
QA | .NET, NUnit | Email service unit tests - Write tests in class NUnitExercise.Tests/CandidateTests.cs to verify Email Service class
- Competenze testate
- Durata
- 52 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di .NET, QA, NUnit, Testing, C#, Selenio
Lacune nel codice
valutare la conoscenza di QA, .NET, NUnit
Attività di programmazione - Livello: Difficile
QA | .NET, NUnit | Business Data Generator Interface - Implement the NUnit tests for the
IDataProcessinginterface into theNUnitDataProcessing.Tests.DataProcessingTestproject that verifies business requirements.
- Competenze testate
- Durata
- 73 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di Java e QA
Lacune nel codice
valutare la conoscenza di Java e QA
Attività di programmazione - Livello: Medio
QA | Java, JUnit | Vending Machine - Write unit tests for the verification of a Vending machine.
- Competenze testate
- Durata
- 39 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di Java
Lacune nel codice
valutare la conoscenza di JUnit 5, Java, QA
Attività di programmazione - Livello: Medio
Java | JUnit | Flight Manager - Implementare le funzionalità mancanti nell'applicazione responsabile della gestione dei dati dei voli.
- Competenze testate
- Durata
- 81 minuti al massimo.
- Valutazione
- Automatico
- Panoramica del test
-
Domande a scelta
valutare la conoscenza di QA, .NET, C#, Selenio
Lacune nel codice
valutare la conoscenza di QA .NET, C#, Selenio
Attività di programmazione - Livello: Difficile
QA | .NET | Selenium, C#, JavaScript | Home Page Testing - Implementare soluzioni basate sulla conoscenza del test dei cookie e dei metodi JavaScript di Selenium utilizzando C# e controllando le schede del browser da Selenium.
When you narrow down the number of candidates you have, you can drill deeper into their skills sets in a skills assessment interview.
TLDR
Are QA testers going extinct? Absolutely not.
Do they need to change to survive? They definitely do.
Can the average software developer substitute for a QA tester? I really doubt that.
What are your thoughts?
