You're at odds with developers on test coverage. How do you ensure quality without compromising progress?

To assure quality while continuing progress despite test coverage differences with developers, prioritise key tests: Focus on the most important tests that protect key functionality. Negotiate scope. Agree on a fair scope of test coverage that addresses critical quality issues without overburdening the development schedule. Implement incremental testing. Use phased testing to gradually check quality. Communicate and cooperate. Foster open communication to ensure that testing goals are aligned and issues are addressed properly. Regularly evaluate and adjust: Continuously review and change the testing strategy to meet project requirements.

As a Designer and Dev, I can attest that effective dialogue is the backbone of successful collaboration. By being on the same page and working in tandem, we can unlock the full potential of test coverage and achieve our goals with clarity and precision. The dialogue process should be seamless, iterative, and empowering – not overwhelming or restrictive – allowing us to collectively push boundaries and deliver exceptional outcomes.

To ensure quality without compromising progress when at odds with developers on test coverage, follow these steps. First, initiate an open discussion with developers to understand their concerns and perspectives. Present data and evidence to support the importance of adequate test coverage. Collaboratively define key areas for testing that balance thoroughness and efficiency. Implement a risk-based testing approach to prioritize high-impact areas. Use automation to streamline repetitive tests and save time. Establish clear communication channels and regular check-ins to monitor progress. Document agreements and continuously review and adjust the strategy as needed. This collaborative and data-driven approach helps maintain quality.

Everyone who makes stuff (or provides services) is responsible for the quality of their output. Reputation is best understood as the total sum of quality outputs that your company achieves. Manager, developer, tester .. leader.. there are no exceptions. Workplaces that are led with a shared ownership of the "quality first" mindset, are more successful and happier places to work in. Work together; and achieve success by sharing the QA mindset. By taking quality seriously and building quality in to everything you do, you will be happier and probably richer too.

Exercise caution with metrics—they are often misunderstood and misused. Context is everything. When collecting data, understand the purpose and limitations of the summaries and the impressions they convey. It's beneficial to gather data that is useful to you, but it's even better if your peers in development, QA leadership, management, and others can also clearly understand what your reports are indicating—and what they are not. One effective metric to track is the time it takes from reporting a new defect to deploying the fix, after investigation, development, and testing. Over time, this metric reveals the true agility of your team.

"Test first" applies to everyone involved in deciding what needs to be made and then making it ready for the customer. The test first approach to delivering quality products, works on multiple levels. Finding out what is required of everyone is actually a sort of test. Understanding this, avoids problems, and builds confidence throughout the project. It provides clarity and good examples to work on. Participate as early as you can in discussion about what will be built or changed. Share your understanding via good examples. Keep it incremental. Write tests at the top level first (Test the overall .. "Who", What" & "When" not the "How" or "With what"), then trust the developers to apply their own judgment at the dev level (unit testing).

Automation in Agile project QA offers numerous benefits, enhancing efficiency, accuracy, and speed. Automated testing reduces the time needed for repetitive test cases, allowing QA teams to focus on complex testing activities, leading to fast-feedback cycles, saving time. Automation ensures consistency and reliability, reducing human error and maintaining integrity throughout development. It supports continuous integration and delivery (CI/CD), enabling seamless code integration and prompt defect identification. Automation improves test coverage, handling scenarios impractical for manual testing, and frees up human resources for exploratory and performance testing. This results in higher-quality software and better resource optimisation.

Taking a risk based approach to test coverage uses precious time wisely. Such an approach not only protects customers from potential defects but also mitigates the risk of reputational damage to the company. By strategically prioritising testing, you can maintain high-quality standards while avoiding unnecessary delays in the development process. This targeted method of risk-based testing is instrumental in balancing the need for comprehensive quality assurance with the practicalities of efficient progress.

To ensure quality without compromising progress, prioritize testing critical areas, automate where possible, and use risk-based testing. Foster collaboration with developers, focusing on incremental improvements and integrating testing early in the development process. Use metrics as a guide, not a strict goal.