Analyzing Popularity of Software Testing Careers in Canada

Software testing is critical to prevent software failures. Therefore, research has been carried out in testing but that is largely limited to the process and technology dimensions and has not sufficiently addressed the human dimension. Even though there are reports about inadequacies of testing professionals and their skills, only a few studies have tackled the problem. Therefore, we decided to explore the human dimension. We started with the basic problem that plagues the testing profession, the shortage of talent, by asking why do students and professionals are reluctant to consider testing careers, what can be done about that, and is the problem specific to locales or spread across the globe? This paper focusses on these questions. The study was carried out in one college in Canada and its findings are compared with a college in India. Studies in more colleges is required to develop acceptable national views. It also may help to study this phenomenon in more countries and develop global perspectives on the issue. However, the study certainly offers useful insights and helps educators and industry leaders to come up with an action plan to change the outlook towards testers in industry and in computer science and software engineering programs, and put the software testing profession under a new light. That could increase the number of software engineers deciding on testing as a career of their choice, could increase the quality of software testing, and improve the overall productivity, and turnaround time of software development activity.

💡 Research Summary

The paper tackles the persistent shortage of software testing professionals by examining the human dimension of the problem, specifically the reluctance of students and practitioners to pursue testing careers. Building on a prior Indian study, the authors conduct a comparative survey in Canada, targeting senior undergraduate students (n = 85) and recent alumni (n = 20) from a well‑accredited software engineering program. The questionnaire mirrors the Indian instrument and asks respondents to (1) indicate their likelihood of choosing a testing career on a five‑point scale (Certainly Yes, Yes, Maybe, No, Certainly Not) and (2) list perceived pros and cons of testing, providing brief rationales.

The research adopts a mixed‑methods design: quantitative analysis of the Likert‑scale responses and qualitative coding of open‑ended pros/cons. Frequencies are computed, and an attempted weighting scheme (5, 3, 1.5 for first, second, third items) proved unnecessary because weighted and unweighted counts were virtually identical; thus, simple frequencies are reported. Reliability and validity are addressed through triangulation of rationales with pros/cons, member checking, and thick description, following Lincoln & Guba’s trustworthiness criteria.

Key findings reveal a stark lack of enthusiasm for testing. Among students, only 2 % selected “Certainly Yes” and 7 % “Yes”; 33 % were ambivalent (“Maybe”), while 27 % chose “No” and 31 % “Certainly Not,” yielding a 58 % overall disinclination. Professionals showed a similar pattern: 25 % expressed willingness (Yes/Certainly Yes) and 45 % rejected the path (No/Certainly Not), with 30 % ambivalent. The most frequently cited pros for both groups include learning opportunities, job security/abundance, ease of tasks, and exposure to diverse domains and technologies. Notably, “learning opportunities” ranked highest among professionals (34 %) but fourth among students, suggesting a perception gap regarding the depth of knowledge gained through testing.

Conversely, the dominant cons revolve around the perceived tedium and repetitiveness of testing, limited creativity, the “second‑class citizen” stigma (testers viewed as having little decision‑making authority and lower status than developers), and stress stemming from tight schedules, overtime, and high responsibility for product quality. These negative perceptions are echoed across both cohorts, indicating systemic cultural issues rather than isolated misconceptions.

The authors acknowledge several limitations: the sample is confined to a single Canadian university, limiting external validity; self‑reported data may suffer from social desirability bias; and qualitative coding inevitably involves researcher subjectivity. They recommend expanding the study to multiple institutions and countries, and complementing surveys with in‑depth interviews or ethnographic observation to refine the understanding of testing career perceptions.

From a practical standpoint, the paper proposes actionable interventions. In academia, curricula should integrate testing as a strategic, business‑oriented activity, offering students hands‑on exposure to full product life‑cycle projects, industry‑partnered internships, and case studies that highlight testing’s impact on quality and risk management. Such experiences could shift the perception of testing from a “easy, low‑skill” role to a knowledge‑intensive, career‑advancing pathway. In industry, organizations should elevate testers’ status by involving them early in requirements and design discussions, granting them decision‑making authority, and recognizing their contributions through career ladders (e.g., Test Lead, Quality Architect) and competitive compensation. Addressing the “second‑class citizen” narrative is essential for improving job satisfaction and retention.

In conclusion, the study provides empirical evidence that negative attitudes toward software testing are prevalent among both aspiring engineers and current professionals in Canada, mirroring findings from India. By highlighting the specific pros and cons that shape these attitudes, the paper offers a foundation for educators and industry leaders to design targeted strategies aimed at enhancing the attractiveness of testing careers, thereby alleviating the talent shortage and ultimately improving software quality worldwide.