We are about to start another round of validation and this validation will span for a week or so. The individual module owners have been assigned tasks in the sense that they will be responsible for all bugs in the module and also for the bugs that are not identified in their modules.
This is certainly stricter than ever before but then it is fair too as this gives a fair sense of ownership. There has been quite some discussions on how the validation needs to be done. We have decided that 3 guys will handle any single module and that will hopefully cover all the areas in those modules.
Once the validation is done for the day, the 3 will meet and share the notes on what all and how all they have tested the product. This cumulative document will form the base for the test case document for the product and will be of use in the future.
The number 3 has been arrived at based on comfort level and the team size. I feel that is proper. No point hanging someone because of too much pressure. The intent is not only to break the product but to understand the base too so that the new kids on the block can start handling more responsibilities. This makes it pertinent that they not only see but also observe.
The preparations for the validation too have been a little tough :-
- Each day there is a gruelling 3 hour class on specific modules. The classes are not just theoretical but also practical. The kids are cross-questioned as well and let me tell you it is a bit unnerving when you see the entire team watch the poor kid who is not concentrating. Surprisingly, the kids have done well and have lived upto the pressure till now.
- At the end of the day, the students are to make notes and submit it to a reviewer
- The reviewer will collate the notes and have it sent to the module owner who will edit the document as required
- This document will be the BASE reference for the validation
- The BASE document will be edited as and when a bug is found and the particular use case is added to it.
- The document will be made public so that we can have more community involvement.
You too can checkout the code in another hour or so and start testing with it. Feel free to destroy the trac ;-). There has been surprisingly less movement in the trac for quite sometime now. Have you guys given up :-)?
Post this release, I expect a performance update to happen. Well, it is still sometime away. Let us have this release out of the door first. Mind you there is no pushing this time 😉
