0 views collected around this technical thread.
This article outlines ten essential practices for testers in agile projects, covering early requirement involvement, test strategy creation, CI/CD integration, collaboration, TDD/BDD adoption, exploratory and performance testing, regression, continuous improvement, and knowledge sharing to ensure high‑quality software delivery.
The article examines the ongoing debate about the necessity of dedicated QA roles, explains why high‑quality projects require systematic testing performed by professionals, outlines appropriate QA‑to‑development staffing ratios, discusses training and management of QA staff, and offers practical guidance for test case management and overall project quality assurance.
This article examines how viewing software development through a data‑system lens can enrich DevOps practices, discussing value streams, microservice decomposition, agile testing techniques, implementation principles, and the role of continuous delivery in reducing uncertainty and enhancing organizational effectiveness.
This article explains the origin and structure of the Agile testing quadrant, compares it with the traditional V‑model, introduces the test pyramid and its evolution into layered automation, and discusses the purposes and benefits of test automation while also noting a related training event.
The article explains the purpose of software metrics, warns against measuring individual performance and isolated indicators, and outlines key agile testing metrics such as code coverage, acceptance test pass rate, defect density per story point, and automation rate to help teams track progress toward quality goals.
The article examines how agile testing shifts quality ownership from individuals to the whole team, outlines the responsibility process model—from denial to responsibility—and proposes three keys (intention, awareness, confrontation) to cultivate a genuine sense of responsibility within development teams.
The article explains precise testing—a data‑driven approach that maps test cases to source code changes to improve test efficiency, coverage measurement, and impact analysis—while discussing its architecture, implementation methods, benefits, and the practical challenges of adopting it in agile projects.
This article argues that traditional, step‑by‑step test cases are becoming obsolete, advocating for alternative test design methods such as mind maps, matrices, user‑story acceptance criteria, and emphasizing exploratory testing, codeless automation, and knowledge‑centric approaches to improve efficiency and maintainability.
This article describes a company's practical implementation of agile testing within a DevOps transformation, detailing each sprint phase, the adoption of Cypress for automated testing, and concluding with reflections on continuous quality improvement and a recruitment invitation for experienced DevOps professionals.
This article explains agile testing as a collaborative team activity, defines its broad and narrow meanings, describes the role of agile testers, outlines ten guiding principles, presents testing strategies, the test‑automation pyramid, agile testing quadrants, and the agile testing manifesto.
This article explains the origin and structure of the Agile Testing Quadrant, compares it with the traditional V‑model, introduces Mike Cohn's Test Pyramid and its alignment with shift‑left testing, and details how layered automation expands the pyramid to include data and environment automation for higher quality and efficiency.
This article presents an Agile Testing Transformation Model that addresses the challenges faced by traditional testers in fast‑paced Agile projects by outlining cultural, organizational, process, and practice changes needed to ensure quality and speed, and provides concrete guidance, diagrams, and references for successful adoption.
This article presents a curated list of fifteen essential books for software testers, covering foundational testing concepts, agile testing principles, practical BDD approaches, and DevOps methodologies, each accompanied by concise recommendation reasons to guide both beginners and experienced professionals.
The article explains the shortcomings of traditional scripted testing in agile projects, introduces the test pyramid and exploratory testing concepts, clarifies how exploratory testing differs from random testing, and outlines practical Session‑Based Test Management techniques for effective agile quality assurance.
This article translates and summarizes the Agile Testing Manifesto, presenting its five declarations, five principles, and thirteen guidelines in both Chinese and English to provide testers with concrete guidance for applying agile practices in software testing projects.
This article provides a comprehensive Q&A covering common misconceptions, recommended books, incremental vs. iterative development, test‑to‑dev ratios, suitable projects, DevOps differences, unit‑test ownership, workload estimation, bug handling, release criteria, test‑team organization, automation practices, and essential skills for effective agile testing.
The article outlines five typical mistakes new agile testers make—waiting for the next build, not fully integrating with the team, clinging to a quality‑control mindset, relying solely on manual testing, and ignoring the big picture—and offers practical advice for each to foster effective, collaborative testing within agile development.
This article describes how a hotel testing team integrated white‑box testing—code review and static analysis—into fast‑paced agile workflows, detailing the exploration timeline, typical functional testing challenges, three concrete bug‑finding case studies, measurable quality improvements, and practical promotion guidelines.
The article argues that while automated testing saves time and ensures regression safety, manual testing remains essential for user experience, exploratory bug discovery, handling complex mobile scenarios, and adapting to agile changes, highlighting its irreplaceable creativity and analytical strengths.