I avoided - or that was my intention until the game started - the 50/50s but my calf and hamstring still felt the pain the next day
Totally worth it though
that's not the role of QA to be a gatekeeper, they give the CTO and President information on the bugs and testing but it's a business decision to ship or not
yes, there's a group still goes once a week on Monday and I go when I can.
There's also one on Wednesday at the main Social Security office
Totally normal people there, not being paid a dime
It's rebounding on them, support for ICE is now negative
They're going after the weak and easy targets and dont care about citizenship as Miller has set them daily targets
so, QA should be noticing that the testers are raising tickets like this and step in and give the testers some guidance on what/how they are testing
I've worked with a clients test team who were not given any training on the system so they were raising bugs like spam clicking button 100 times, quickly resizing window 30 times, pasting War and Peace.. gave them some training and direction and they started to find problems that actual users would be finding
They find all the things the devs and their automated tests missed, then they mentor the devs in how to test for these and they work out how the bug could have been found earlier. Rinse and repeat until the tester is struggling to find issues and has coached the devs out of his job
how did misunderstanding a feature and writing pages on it help, not sure I follow the logic of why this made them a good QA person? Do you mean the features were not written well and so writing code for them was going to produce errors?