May-05-2017, 08:17 PM
That was a major SNAFU (mine). After test automation has reached a mature state, was shown to CEO, my manager reported impressive amount of time it saved and number of bugs it uncovered - I managed to break it 
.
In my defense - who would have though that a process will politely wait on stopped service, instead of dying in violent agony
? So it took me some time to get that the fault was mine 
. But I fixed it and pushed the solution to repository.
The morning starts with test failing again - my manager has not synched his commit before pushing. My reaction
I fixed the bloody thing. Another test failure. This time
product bug. Another build - another bug discovered. I say to my manager
.In my defense - who would have though that a process will politely wait on stopped service, instead of dying in violent agony
? So it took me some time to get that the fault was mine . But I fixed it and pushed the solution to repository.The morning starts with test failing again - my manager has not synched his commit before pushing. My reaction
Quote:Is it some sort of revenge? Was it worth it?
I fixed the bloody thing. Another test failure. This time
product bug. Another build - another bug discovered. I say to my manager Quote:Didn't you wish I haven't fixed my bug?
Test everything in a Python shell (iPython, Azure Notebook, etc.)
- Someone gave you an advice you liked? Test it - maybe the advice was actually bad.
- Someone gave you an advice you think is bad? Test it before arguing - maybe it was good.
- You posted a claim that something you did not test works? Be prepared to eat your hat.