wow, ok, so here's another huge plus for TDD and BDD. it gives you the confidence to not immediately blame your own code when something goes wrong when you deploy and take part in a large SOA project. when you know that, given the right inputs, you'll produce the right results (because you built the system using TDD based on the other system's messages), you know to look to things outside your system when it's going pear shaped.
turns out, this was a human error thing that was the result of some less-than-stellar design on my part. also, the QA test plan was not using our intended behavior for the software, so... suffice it to say, there were a lot of cognitive leaps to be made to get this validated. buuuuuut... the greatest thing i got out of it was i was an effective troubleshooter because i didn't waste time (or stress) digging in my code for answers.
it turned out to be an education thing. once the dust settled, code was verified.
No comments:
Post a Comment