ProgrammerHumor
pleaseTestMore
Discussion
Is it?
My QA will raise issue like, when I click button, it works.
Page loaded too fast, make sure we didn’t miss something.
My QA once blocked a hotfix to master because the very old systemd version their test environment had didn’t like me updating the unit file and just masked it.
Be me.
Work on a really important bug that is very delicate as it affects the entire app.
Strongly warn the QA leads that they need to be pretty thorough when testing the app due these changes, as the bug's use case works as expected but the changes impacts other areas and is probable some stuff stops working as intended.
1+ month pass with no issues found, and changes are pushed to prod.
Within 2 days a client was complaining about an entire functionality of the app not working due the changes.
I'm chew off because my changes broke prod and need to stay after hours to rush a solution.
That’s a day before demo) tomorrow afternoon they assign to you 20 more bug tickets from backlog)))
Is this God Miracle ?
Here's my problem. They find a bug that has NOTHING to do with my code. Not even same page or api.
This is what heaven looks like.
Thats because you have 53 bugs from the last sprint to take care of.
37 old bugs reopened.