Today I attended a lunch meeting at EAST. Erik Brickarp held a presentation on Challenges in Exploratory testing. He talked about stuff he encountered through his career at Ericsson and later VeriSure. Interesting!
Some items in notes form for me to remember:
- Session Based Test Management, SBTM - "Wrinting better chartesr" by Michael Kelly, available at Youtube - need to look up!
- Estimation - who wants to know what and when (personal reminder: check out the notes from Michael Bolton on estimation in Stockholm, May 2015)
Information of interest is usually on the lines of "we're on time", "we're behind, but it is ok because of this or that" or "we're behind and it is urgent to solve our obstacles"
- Check out test framing by Michael Bolton/James Bach
- Low tech dashboard - James Bach
- SBT (metrics) Setup - Bug - Testing - the ratio/percentage of time spent on each bit. Can show that setuptime is crazily large (expensive) in relation to testing. Can show that quality has decreased (higher time spent on Bugs than 6 months ago...) ...
- SFDIPOT - google the translation S=Structure, F=Funcionality etc.
We also discussed the differences between test idea, test case and charter.
Erik has a document with loads of questions to ask when setting a stretegy, not all are relevant always, but some are relevant sometimes.
The heuristic test strategy model by MIcheal Bolton is well worth spending time on recap.
Some items in notes form for me to remember:
- Session Based Test Management, SBTM - "Wrinting better chartesr" by Michael Kelly, available at Youtube - need to look up!
- Estimation - who wants to know what and when (personal reminder: check out the notes from Michael Bolton on estimation in Stockholm, May 2015)
Information of interest is usually on the lines of "we're on time", "we're behind, but it is ok because of this or that" or "we're behind and it is urgent to solve our obstacles"
- Check out test framing by Michael Bolton/James Bach
- Low tech dashboard - James Bach
- SBT (metrics) Setup - Bug - Testing - the ratio/percentage of time spent on each bit. Can show that setuptime is crazily large (expensive) in relation to testing. Can show that quality has decreased (higher time spent on Bugs than 6 months ago...) ...
- SFDIPOT - google the translation S=Structure, F=Funcionality etc.
We also discussed the differences between test idea, test case and charter.
Erik has a document with loads of questions to ask when setting a stretegy, not all are relevant always, but some are relevant sometimes.
The heuristic test strategy model by MIcheal Bolton is well worth spending time on recap.
Inga kommentarer:
Skicka en kommentar