Thursday, September 20, 2018

Sure, NOW they decide we need to test

So today the PM gets insistent in the daily that I need to write up a test plan for the rework of our DB population module.  It was written incorrectly by a contractor who left recently, and there seems to be lingering blamestorming on how we did not know he was not doing the right thing (hint: when you have 5 priorities and only 3 developers, you end up having to assume everyone knows enough to ask for help).

Now, I get the desire for testing, but until this very week, nothing, I mean NOTHING has had an official test plan on this faux Agile fustercluck of a project.  So why does this suddenly need a test plan?  And who is going to test it?  The DB relationship are part of the complexity of this part, and I'm the only one who has any idea of what those relationships are.

I swear, it's going to turn into me teaching someone the whole mess including how to test this, all the while being given other work, because someone else is 'doing the testing'