Start with respect and explore the value of having a good tester on your side.
Testers usually face the brunt of things if something broken makes it to production, so be weary of saying things like "it's just a simple change" or "don't worry about that test case".
It's always better to give more detail on your work than less, and to focus on the testable aspect. It is also a great idea to familiarize yourself with their test cases and to discuss them rather than lobbing work over the fence.
Start with respect and explore the value of having a good tester on your side.
Testers usually face the brunt of things if something broken makes it to production, so be weary of saying things like "it's just a simple change" or "don't worry about that test case".
It's always better to give more detail on your work than less, and to focus on the testable aspect. It is also a great idea to familiarize yourself with their test cases and to discuss them rather than lobbing work over the fence.
I like your approach, Harry! :D Thanks for contributing.