Let us reflect together on everyday situations where everything is done with foresight, care and attention, but when we take it to our work in software development or other sectors, all this is overshadowed by haste, budgets and sloppiness.
Exploratory testing is probably one of the most confusing topics in the world of testing.
The most widely used definition of exploratory testing says that it is an approach to software testing that is often described as simultaneous learning, test design, and execution.
This approach is the perfect complement to performing any other type of testing and is, so to speak, the antithesis of automation. While automation focuses on checking, exploratory testing focuses on learning, experimenting, searching for improvements and more complex points of failure. This does not mean that automation cannot be used when conducting an exploratory testing session.
We are convinced that we have captured your attention with such a captious title, but the truth is that we have not been able to find a better way to describe what, in our view, is happening with one of the most classic roles in software quality. I recommend at this point, for further contextualisation, to go to one of our last posts: “The evolution of the titles of the roles related to testing and quality”.
In the dynamic world of technology and development, roles related to testing and quality assurance are not just undergoing a radical transformation, but also witnessing the emergence of new job titles to describe, in many cases, the same responsibilities. In some instances, the change in context necessitates a shift in the job titles, leading to what can be termed as “title inflation” in the job market. In this blog post, we delve into the fascinating journey of how job titles in testing and quality assurance have evolved, exploring beyond the labels to understand the real responsibilities they entail.