1. Gonna miss the team’s retrospective tomorrow, which is a shame because this week seems to have flown by. I feel like I’ve been really working hard trying to understand viewtests, xpath, selenium and a little bit of RoR. I have understood and used a bit of all of the above and think it won’t be long before Ed and myself has some view tests that we can let run and see whether we have made them too brittle or too broad. It took longer because I had to wrestle with git a little, when it created a sub module in the repository for our selenium plug-in. Got fixed in the end, but that ate up pretty much a whole session.

    Darrin helped out a lot in the early sessions, by creating a method of bypassing the login in the test environment. Very handy and very necessary.

    After that I began to get to grips with concept of creating dummy data in the test so that we can test against that. Again, Darrin sorted out some examples that I learned from, so I even ended up doing my own. Which surprised and pleased me.

    I introduced Ed to the tests and he picked them up pretty quickly, so that we only have a few little things to do. One of the hardest tasks is deciding what one wants to test.

    So, from my perspective progress has been slower than I’d like. It can be aggravatig when the story cards are hanging around on the board, and our early numbers start to drop away.

    If I have a hope for next week, it’s that we are able to define more clearly the success criteria for a story, which might help in closing them. When we are pickimng up the cards to do, we don’t want to have to think too much about the scope of the card, and concentrate on the job in hand.

    And that’s all I have to say about that.

Notes