You're at odds with developers over unit testing strategies. How do you find common ground?

It could be address by: - Discuss the specific benefits and limitations of each strategy. - Identify common goals and priorities - Propose trial periods for different approaches - Be flexible and open to adjustments based on feedback - Document and review results collaboratively

Open communication, empathy, and a willingness to compromise is how you should proceed. Action items: Schedule a team meeting to discuss testing strategies openly with prepared data on the benefits of unit testing, including metrics on bug reduction and long-term maintenance costs. Actively listen to the developers' concerns about time constraints and productivity. Propose a compromise: Start with unit testing critical functions and gradually increase coverage over time. Schedule a future date to evaluate its effectiveness. Offer to pair-program with resistant team members to demonstrate efficient unit testing techniques, such as leveraging generative AI Create a shared document outlining agreed-upon testing guidelines and best practices.

Brown bags, are great ways to demonstrate to showcase how one test is better than another. Be sure to not use other's code in example of falling short, though your brown bag could be inspired by a poor Pull Request, it shouldn't be obvious, perhaps prepare for it but it in put in a queue so some time has passed. However, highlighting someone's code as a great example, is a pleasant surprise in a brown bag and could inspire testers to write tests that get featured in other's brown bags in the future. What's great is if you can use your own experience and examples, demonstrating both humility and growth.

If you are working in an agile environment, and regularly have end of sprint demos, highlighting test coverage to stakeholders, when it's good (so perhaps not every sprint) is a great way to evolve into a leadership role in the future. You may find you want to be a Test Lead or want to be a Technical Program Manager and getting experience communicating metrics, and progression is way to start getting your reps in, and a way for others to notice. If perhaps quality of tests, or test coverage dips. Retrospectives maybe better place to present team slipping and your chance to volunteer to own whatever problem going forward, be it setting a threshold, or adding a test linter, or module.