justDeployIt

4y

A customer asks for a change request or a bug fix and it results in creating a ticket for that.
It's the process and how it works in most places but after you finish with the task and fix the same customer who provided you with the requirements will request that you share the steps on how to test the fix or the feature.
I'm not speaking about the data preparation or required configuration. I mean a step-by-step instruction on how the tester/QA will test it.
It's driving me mad!! So a way to counterplay this stupid requests, I provide the happy path and what to expect. And in case, they stumbled on a bug later in production, I can easily say "It was approved by your testing team and that's a new requirement ;)"

rant

requirements

quality

testing

Ranter

Comments

4

Fast-Nop

39106

4y

That's stupid because testers should be able to derive tests from the requirements. If the dev who coded it provides the tests, he will make the same mistakes in test case design as already in the software design.
1

justDeployIt

423

4y

@Fast-Nop that's exactly what made me angry about those requests.
I shared those aspects with my manager but he said that's what the customer wants.

And that's why I'm mentioning now that any issue is a change request as a way to push them to do their job.

Related Rants

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service