Blog & articles

A CAPTCHA is a test used on web pages to determine whether the user is human. The intention is to secure your application from bots and avoid automated attacks. When executing unit tests on your website, a captcha will prevent unit tests from working properly. So, how do you keep your site protected with captcha but also pass unit tests?

There’s been an increased demand for several roles related to Quality Assurance (QA) such as Quality Assurance Engineers (QAE), Automation Testers, Software Developers in Test (SDT or SDET), Performance Testers, or hybrid QA Engineers. However, what do these imply job-wise? Perhaps when we look into possibly applying or hiring someone with experience in testing or automation, we’d need to better understand the different roles and responsibilities in software testing teams. At the moment, nearly all companies rely on some kind of test automation as the source of truth for quality verification and, in some cases, quality validation. However, there is still the need for humans to be on the other side of the tools we use for automation. When we adopt a quality mindset and understand every role to identify the best fit for our company we ensure that we can get a team that is talented and aligned with the goals.

Functional testing has been around for so long that most testers are unaware that continuous testing is critical for better and faster results. In addition, this type of testing leaves more time for the QA teams to work on other tasks like exploratory testing. This article will discuss automating your test suite with a continuous integration and continuous delivery pipeline (CI/CD for short). It will introduce four popular CI/CD test automation tools that can integrate easily with some software testing automation tools.

When referring to the crucial functions of any organization to create a culture robust such as diffusion of quality philosophy, quality mindset, and group cohesion, we realize the obstacles in making such a culture.

When we talk about test automation, we should consider it as part of testing itself; we know the existence of functional testers and automation testers (You can read about SDETs, SET, DevTest, and other QA roles in this post).

Have you ever found yourself serving as the only tester on a project? Do you perform functional testing, test automation (frontend and backend), and performance testing? Do you wonder about the value you bring to the organization? Does this sound like a solitary path with many responsibilities?