July 2024 Summaries

The evolving role of Quality Assurance (QA) in the tech industry is marked by a tension between the perceived decline in its importance and its continued value in adapting to new technological and workflow changes. Despite predictions of its demise, QA remains crucial, as seen in the aftermath of Indeed's layoffs and Figma's QA oversight issues. Historically, technological advancements like ATMs and eReaders, and methodologies like Agile and DevOps have not eliminated roles but transformed them, illustrating the concept of "creative destruction." The QA role has similarly evolved, with a shift towards automated testing and the integration of QA tasks into development processes, leading to a more dispersed and concentrated role. This evolution has enabled QA engineers to focus on higher-level work and exploratory testing, enhancing software quality beyond routine checks. As the industry continues to shift left, integrating more testing responsibilities into development, the value of QA is not diminished but redefined, ensuring that QA professionals can leverage new tools and technologies to maintain high standards of quality assurance.

The recent CrowdStrike incident, which resulted in operational disruptions such as canceled flights and widespread computer crashes, highlights the risks associated with modular software updates without thorough testing. Despite CrowdStrike's comprehensive testing claims for its main app, a bug in the module's verification process led to a critical failure, demonstrating a lack of attention to the modularization's potential pitfalls. The financial impact is estimated to be around $5.4 billion for Fortune 500 companies, and the situation underscores the importance of rigorous testing protocols, especially for loadable modules. CrowdStrike's response, involving planned improvements in testing and deployment strategies, indicates an acknowledgment of their oversight but also suggests a prior decision to minimize costs in testing, possibly leading to greater reputation damage. The company's management, particularly CEO George Kurtz, who has faced similar issues in the past, is critiqued for a lack of accountability, echoing broader concerns about leadership responsibility in quality assurance practices.

Over a billion people globally are disabled, yet accessibility in events remains inadequate, particularly for those with physical disabilities and neurodiversity. Rease Rios and Jenna Charlton from Qase highlight the importance of accessibility education, emphasizing that disabilities can be invisible and vary in visibility and impact. They advocate for comprehensive event planning that includes ADA-compliant venues, accessible hotels, trained staff, and pre-event information sharing. They stress the need for auditory, visual, and general accessibility accommodations, such as ASL interpreters, CART services, assistive listening devices, and varied seating options. The authors argue that accessibility should be a fundamental aspect of event planning to ensure inclusivity and comfort for all attendees, with continuous improvements being vital.

On July 19, 2024, a global IT outage caused significant disruptions across various sectors, including banks, airlines, and hospitals, primarily due to a software update from the cybersecurity firm CrowdStrike. While the incident prompted a flurry of technical analyses and reports, it also inspired a wave of humor on social media, with memes and jokes highlighting the chaos and confusion caused by the outage. The humorous reactions, which included parody songs and creative graphics, served as a coping mechanism for those not directly affected, while acknowledging the hard work of IT and development professionals in addressing the crisis. Despite the lighthearted responses, the situation underscored the vulnerability of critical systems and the widespread impact of such technological failures.

Tiara Swain, a Global Career and Corporate Consultant, offers insights on navigating the competitive QA job market through strategic resume crafting, LinkedIn optimization, and effective networking. Emphasizing the importance of a well-structured resume, she advises tailoring it to be ATS-compatible by integrating relevant keywords and clear headings. Swain highlights the significance of showcasing technical skills like proficiency in tools such as Qase, API testing, Selenium, and Jira, while quantifying achievements to demonstrate impact. She underscores the role of LinkedIn in maintaining professional consistency and visibility, advising on crafting engaging profiles with industry-relevant keywords. Active engagement with QA communities and strategic networking, including informational interviews, are pivotal in understanding industry trends and expanding professional connections. Swain stresses that standing out in the QA field requires not only meeting technical qualifications but also demonstrating passion and commitment, positioning oneself effectively for roles that align with career goals in this evolving industry.

Stress testing is a crucial aspect of software testing that evaluates the stability and reliability of a system under extreme load conditions, ensuring that applications can withstand real-world demands. By simulating scenarios such as sudden increases in users or data volumes, stress testing identifies bottlenecks, memory leaks, and potential failures, thereby allowing developers to optimize performance and improve system resilience. Unlike load and performance testing, which focus on typical operating conditions, stress testing pushes systems beyond their normal limits to reveal weaknesses. This testing is essential for critical software systems and helps prevent costly downtime by addressing issues before deployment. Various types of stress testing, including application, transaction, and system stress testing, target different aspects of system operation, while metrics such as throughput, response times, and error rates provide insights for improvement. Overall, stress testing enhances the reliability and efficiency of software, ultimately boosting user satisfaction by ensuring applications remain robust under high-stress conditions.

Exploratory testing is highlighted as an essential technique for both automated and manual testers, offering a unique approach that emphasizes discovery and experimentation over traditional scripted testing methods. Unlike ad hoc testing, which lacks structure, exploratory testing is structured, time-boxed, and session-based, with defined objectives to uncover unknown unknowns—issues that cannot be anticipated through automated testing. It involves simultaneously designing and executing tests to learn about a system, using insights from one experiment to inform the next, and is particularly valuable for identifying gaps between features or bugs that occur under specific conditions. The process is described as a blend of art and science, requiring continuous learning and adaptation, with an emphasis on crafting a charter to guide testing sessions, setting time limits, and documenting findings. Post-testing, a debriefing session is crucial for sharing insights and planning future experiments, underscoring the continuous learning aspect of exploratory testing. This introductory guide is part of a larger series aimed at delving deeper into the methodology, exploring its integration with other testing strategies, and further examining its benefits and challenges.

Qase has introduced several new features and updates aimed at enhancing team collaboration, productivity, and the quality of products released by testing teams. These updates include the Get Started Dashboard, which provides an overview of team activities and allows for customization through widget management and data filtering. New assignment capabilities enable test cases to be distributed evenly among team members or based on complexity, while features like Muted Tests and enhanced widget filtering support focused and efficient testing processes. Bulk deletion of test runs and plans streamlines workspace management, and QQL widgets offer advanced query search capabilities for comprehensive monitoring. The company also emphasizes the integration of CI/CD tools, making it easier to incorporate Qase into various testing workflows, and highlights its commitment to developing user-driven features by actively incorporating customer feedback from platforms like Canny.

Canary testing is a software deployment strategy that involves releasing new functionality to a small subset of users to manage risk and detect potential issues before a full rollout. This practice, named after the use of canaries in coal mines to detect toxic gases, allows development teams to monitor the performance and stability of new releases by observing operational metrics such as error rates and system performance in a live environment. Unlike A/B testing, which focuses on user behavior and preference, canary testing is primarily concerned with ensuring the new release does not introduce critical issues. It is often compared to blue-green deployments but differs by gradually exposing users to the new environment. The strategy provides early detection of problems, allowing developers to roll back changes if necessary, thus minimizing disruption and enhancing user satisfaction. While the approach offers significant benefits, such as minimizing widespread issues and gathering real-world feedback, it also presents challenges, including selecting a representative test group and effectively managing rollbacks. Canary testing is particularly valuable for deployments involving significant architectural changes or new features, helping to balance innovation with system stability and user satisfaction.

Quality assurance (QA) is a complex and subjective field where measuring quality definitively is challenging, as illustrated by the analogy of a family road trip where success is not solely based on reaching the destination but also on the experience along the way. Quality is defined by standards like ISO 9000 and ISO 25000 as the ability of a product to fulfill stated and implied needs, yet it remains subjective, relying heavily on client perceptions and experiences. Proxy metrics such as Net Promoter Score (NPS), Customer Satisfaction Score (CSAT), and Customer Effort Score (CES), while useful for indicating areas needing further analysis, do not directly measure quality and are influenced by biases and external factors. Quality metrics, both external (client satisfaction) and internal (code sustainability), serve as signals rather than finite measurements, requiring thorough analysis to understand underlying issues. The use of tools like Shewhart control charts can help distinguish between normal fluctuations and actual problems. Ultimately, metrics should guide improvement efforts, recognizing the subjectivity of quality and the importance of Total Quality Management (TQM) to enhance both product and process quality.

Defect management is a critical component in software development, focusing on identifying, documenting, and resolving issues within software applications to ensure they meet quality standards. In complex software environments, defects can arise from coding errors, incorrect logic, or unforeseen interactions, manifesting as functionality issues, security vulnerabilities, or performance degradation. Effective defect management enhances software quality, reduces risks, and enables continuous improvement by allowing teams to address root causes and prevent future occurrences. The process involves defect prevention, detection, categorization, resolution, and verification, supported by defect metrics such as defect density, detection percentage, and removal efficiency, which help assess the effectiveness of these efforts. However, these metrics should not become targets themselves, as this can lead to unintended consequences like underreporting defects or overlooking non-defect issues. Instead, they should serve as tools for analyzing and improving development and quality assurance processes. By leveraging automation tools and fostering a culture of continuous improvement, organizations can streamline defect management, enhance software reliability, and promote innovation, ultimately safeguarding user satisfaction and organizational reputation.