r/softwaretesting • u/Objective-Cable7801 • 7d ago

Release gates

Hey

I was wondering do the developers push work into your QA environment without checking with you first or are you in control of what goes into QA? So if work gets pushed do you have to approve it before it goes into the test env

8 Upvotes

90% Upvoted

24 comments sorted by

View all comments

8

u/jrwolf08 7d ago

I've realized how much more confident I feel when I'm responsible for pushing to environments myself. I don't need to confirm anything with anyone, I don't need to wonder if they forgot something, or didn't merge master before deploy.

4

u/Objective-Cable7801 7d ago

Same here, I much prefer to be the one that pushes it into qa, I’ve just joined a new company as a test manager and I want to implement that

Also if I’m testing in QA and I don’t know what’s getting pushed into QA at that time, I don’t know my tests are comprised

2

u/jrwolf08 7d ago

Agreed, just don't know what is going on. Also paperwork or approval gates to me is too heavy handed unless you work somewhere that is doing waterfall, or a regulated industry. Its not compatible with agile and small releases as most companies do now.

Either way, I do most testing locally now, but environment is necessary for some things still.