I’ll be speaking on the TMF testmanagement summit in Londen. Below the summary of my presentation:
Lately there is a lot of discussion about how test will be organised in the near future. Some state that the test phase will cease to exist. This session discusses that statement. Testing will be required throughout the development lifecycle. It is expected that test activities will shift from an independent phase near the end to the life cycle, towards various activities throughout the lifecycle. These activities include reviews as well as end-to-end testing and even testing in production. In order to decide whether a separate test phase has value, we need to regard two components. Testing has a technical and an intelligence component. The first has it focus on making the software work. The second component has its focus on governance and on providing information. We do not testing because we can, but we organize test activities because they matter. Each activity aims in not only finding bugs, but also in providing trust in an early stage of the development process. Is a lot of testing to be done by non-testers? e.g. The BA review of requirements, testing by developers in their SCRUM sprint. Plus, James Whittaker states that users will be involved in testing more and more. Is the testers role more of a coaching or controlling role? But this does not suit all situations. Lets consider where an old-school testing-phase might be the best solution. So we end up having more options, tools and measures to choose from. To do so, we require vision and understanding of the goals and the test profession.
More info: http://uktmf.com/