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
Related Rants
Cont. https://devrant.com/rants/12659551/... .
Imagine receiving three basically the exact same reports instead of just one.
When releasing games on consoles, there are some rules for basic quality the games have to meet that depend on the platform.
Some of those rules align across all platforms, but are written down as different test scenarios.
Let's say, the game mustn't crash && tests are listed as:
- Company A: Test 0.
- Company B: Test 1.
- Company C: Test 2.
If a crash affects all platforms, the _logical_ thing to do would be to write just one report, mention all affected platforms && also list all requirements that are failed due to this.
Leadership: 'No, we need to create separate reports for each affected platform.'
Result: Only one report gets actual attention, while all the others are left forgotten, living as zombies.
...sometimes I wonder whether such people are paid per report, given their approach.
/* For some context: I am dealing w/ a multiplatform project built using one of the more popular engines, making vast majority of issues present regardless of the platform. Creating separate reports makes absolutely no sense.
They changed their mind solely after this being brought up by the developers, though. */
rant
testers
bad leadership
qa
test monkeys
retards