My explanation for building a relationship with devs was to be curious.
This fence stuff really creates a bad environment to making quality software.
The dev chucks it over and begins working on another task. QA uses the application in an environment someone else setup and configured (not always the dev) any semblance of malfunction is thrown back over, and for some reason environment problems a so prevalent the dev resents needing to debug someone else's mistakes.
I don't know how many times a dev and I would talk about testing specific cases and executing on the before they even commit the code. It is horrible for reporting to show all the bugs QA helps find, but is great for the product quality.
My explanation for building a relationship with devs was to be curious.
This fence stuff really creates a bad environment to making quality software.
The dev chucks it over and begins working on another task. QA uses the application in an environment someone else setup and configured (not always the dev) any semblance of malfunction is thrown back over, and for some reason environment problems a so prevalent the dev resents needing to debug someone else's mistakes.
I don't know how many times a dev and I would talk about testing specific cases and executing on the before they even commit the code. It is horrible for reporting to show all the bugs QA helps find, but is great for the product quality.
Making a Relationship with Your Developer
Jesse Phillips ・ Jul 2 ・ 2 min read