Twelve Principles of Software Testing

Software testing is based on the fundamental principle of viewing the product from the user's perspective, conducting comprehensive testing to discover defects early and as extensively as possible, and tracking and analyzing issues to propose improvements.

Testing should follow the "good enough" principle: insufficient testing cannot guarantee quality, while excessive testing leads to waste.

The article lists twelve specific testing principles:

1. User‑Centric Perspective – Testers must consider user needs, environments, and habits to design effective tests.

2. Throughout the Software Lifecycle – Testing should start early and continue throughout development to detect defects sooner and reduce costs.

3. People Are the Decisive Factor – Despite the importance of tools, human expertise in selecting tools, setting environments, and designing test cases remains crucial.

4. Quality First – Quality is the core of an organization; testers should advocate for sufficient time and resources to maintain quality.

5. Early Defect Detection – The earlier defects are found, the better; testing should be incremental and focused.

6. Close Collaboration with Stakeholders – Testing is not isolated; it requires tight cooperation with project managers, developers, and user representatives.

7. Evidence‑Based Testing – Test bases must align with test objectives, such as using detailed designs for unit tests or defined quality metrics for overall testing.

8. Continuous Planning and Adjustment – Test plans must be adaptable to changing requirements, software changes, and environment shifts.

9. Tailored Testing Methods – No single method fits all; testing approaches should be selected based on project specifics and may vary across phases.

10. Prioritized Testing – Because exhaustive testing is impossible, tests should be prioritized based on risk and importance.

11. Pay Attention to High‑Defect Areas – Code sections with many defects likely hide additional issues and require careful handling.

12. Objective Third‑Party Testing – Independent testing teams or third‑party specialists provide more objective and effective verification; even developer‑performed tests should involve peer review.

The article concludes that all twelve principles are vital and must be deeply understood and practiced for effective testing.

Additionally, the IDCF DevOps Hackathon challenge is announced: an original end‑to‑end DevOps experience combining lean startup, agile development, and DevOps pipelines. The event will take place in Shanghai on March 25‑26, 2023, giving participants 36 hours to build and launch a product from scratch. Both corporate teams and individuals can join.