Rules to Better Testing

• Do you understand why testing is important?
• Do you understand what "testing" really means?
• Do you know that “complete testing” is impossible?
• Do you understand why testing cannot be completely automated?
• Do you recognize the importance of critical distance?
• Do you take a risk-based approach to test planning?
• Do you know the whole Scrum team is responsible for quality?
• Do you know when you've done "enough" testing?
• Do you know what “exploratory testing” is?
• Do you understand the dangers of tolerating automated test failures?
• Do you know the different types of testing?
• Do you mix user research methods to capture the full picture?
• Do you test high-risk features with real users before launch?
• Do you treat your automated test code as a first-class citizen?
• Do you remember to use automated UI testing sparingly?
• Do you know whether a test is a good candidate for automation?
• Do you understand the "testing pyramid" models?
• Do you regularly review your automated tests?
• Do you know how to manage and report on exploratory testing?
• Do you know how to decide what to test?
• Do you understand how you know when you’ve found a problem?
• Do you use port forwarding to test local builds?
• Do you use the EF Core In-Memory provider to simplify your tests?
• Do you use Ephemeral environments for clean and isolated testing?
• Do you handle Multi-OS dev teams in source control?
• Do you know which environments you need to provision when starting a new project?
• Do you use Logging Fakes?
• Do you canary deploy your new features using a spreadsheet?