Reading a little about acceptance testing, and starting to see the role that testing could play for us. Still not sure about the view testing that I’m doing. I couldn’t come up with a compelling reason why we are doing them. Hoping that it will become clear why we do them.
With regard to acceptance testing it seems that the intention is to relate the acceptance test to the story on the card. That is the mechanism that we then can verify that that story is finished , tested and accepted. I’m not sure how much our existing tests meet this requirement, and of course there is probably an element of retro fitting that should diminish as things progress.
The dilemma is how deep we go into the testing before we start to get diminishing returns. With the view tests, I am currently checking that the correct things are being rendered, that particular areas of content are existing, and that the right messages are appearing to users. The problem comes because it’s difficult (and maybe unecessary) to write tests that go into that level of detail.
