Through the evolution of the practice of QA in agile teams, a high degree of quality can now be added to product development. Not only can thorough tests be designed, written and executed within a single iteration, the use of post-mortem analysis allows for team reflection and, as a result, process improvements. So how best to perform QA in say a two week iteration? One way is as follows * The user stories are chosen and the team members select which tasks to perform from this. * Developers are given the morning to sit and work out which unit tests and low-level functional tests they will write. The QA person then meets and discusses this with the developer, finding out (at the high level) what the expected functionality is. * The QA person has the opportunity to request that the developer adds more tests to the suite, change existing ones, etc - the idea is that a QA input has been provided before the developer writes a line of code. * Agreement is made and the developer starts ...
Comments
Post a Comment