Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
This sucks, I’m sorry 😐. It’s good to have an alliance with your embedded tester for when everything else is going to shit— if no one is dictating to them what to test, you can send them in-place builds from your own branch and at least make sure your work is quality (assuming you’re allowed to make builds at will)
My embedded QA person is one of my favorite people, because he completely understands my frustration when bosses try to implement a foolish deployment strategy, and he’s willing to work with me directly to get shit done. He shares the same frustrations I do, but even worse because QA gets shat on so often when anything goes wrong (or right) -
@BrokeTheInteger yeah I think next time I'll ignore the advise and deploy anyway.
Fuck me I'm pissed. This sprint, my tech lead has been away and a senior dev has been covering for him. We plan a load of work and distribute stories and we churn threw it quite well. However, my senior dev says let's not deploy until all the works done. I was like, how is it going to be tested? He was like well it will be fine because it's all one test. Bs. We now have 2 days left, tester is getting stressed because they don't know what to test or what's been finished. Scrum master is asking why all of it should be tested at the same time and I'm here like this is fucking dumb. Also the tester decided to start testing with the most complex piece of work, rather than prioritising.
Starting to wonder if I'm just the outsider or whether no one understands that granularity is better.
undefined
scrum masters testers seniority agile