The Power Hour Elizabeth mentioned Power Hour - Exploratory Testing
Questions we didn’t get to
- Do you have experience in having to keep around reports for specific releases that happen quite frequently? Any good practices for leaving results documented for posterity?
- What about reporting on trends in test execution. Any approach/tools you recommend for analytics?
- Do you have any suggestions on how to also highlight what went Well in the Test report.
- Do you find that regularly providing good test reports contributes to meaningful change in the Product Development process as a whole?
- Is there a good accessibility testing training that you would recommend?
- Have you used a testing report tool like qa touch? whay do you think about it?
- how do you deal with client reported bugs? they usually log critical bugs for minor issues. Do you add them in a separate section in your report?
- What type of graph format need to use to indicate issues ?
- What are the criteria that need to decide on test status : Pass/Fail/Conditional Go
- Should we be providing just metrics for our reports or should we look at providing information that answers key questions?
- How can exploratory testers create their portfolios?
- What do your reports look like? How do you organise within your reports?
- What tools (or strategy?) do you prefer to use for test reporting? Or if no preference, how do you decide what is the best tool/strategy to use?
- Should a Test report be pushed to the version of the code it relates (for that specific environment)?
- how long does it take you to work on each test report?