Nope. A “change request” is exactly what is says – it’s a (polite) request to have something changed.
- It’s actually a somewhat older term for what has become “Bug Reporting” – In the past and, currently, it was/is assumed that, anything that was produced by schooled craft people was either perfect or, acceptable –
It wasn’t implemented with a failure but, it should be changed to make it better …
There is a mindset that says – “We’re using the most up-to-date methods and tools – therefore, what we’re producing is perfect – failure free … ”
If you attempt to tell such a development team that, their code has bugs in it, they’ll usually be very upset, their combined egos are damaged and, they tend to ignore the report detailing the bug in their perfect, bug-free code.
How to work around this delicate issue?
- Submit a Change Request, politely requesting a change to the implementation which was presumed to be perfect …
BTW, as a software tester, I was submitting on average about 5 Bug Reports per day, based on the results of the Test Cases being executed – the managers of the software development teams were more than a little bit piqued because, each Bug Report referenced a specific (contractual) product requirement and, it described the product’s behaviour which wasn’t matching a specific requirement.
- When you’re testing against more than 2 000 contractual requirements, this is a fairly normal bug reporting rate …