Please enable JavaScript.
Coggle requires JavaScript to display documents.
Performing a test session (How to convert notes into a report (Changes to…
Performing a test session
What to think about before a session
What do you need so that you won't get stuck during the session?
Kit: phones, SIMs, correct software on test rigs, groups set up
Sanity check of mainline function
Required knowledge
Understanding of part of function (e.g. network intelligence)
Location of MOPs, software images etc.
Oracles: How will you tell whether behaviour is 'right'?
What is the goal of the session?
Session charter (states the mission)
Session plan (gives more details, including expected length, required setup and test suggestions)
Pre-session brief
Key risks you want to explore
What to track during a session
Info for bug raising
Store off diags if needed
Enough details about scenario to repro, or to raise an issue if not reproducible
Timestamps
Info for report writing
Changes in focus (to explain reasons in report)
Thoughts that need future investigation
Blocking issues
Areas where automation would help?
Feelings while testing
Differences from planned testing
Make sure you're familiar with report fields before starting session (can see fields by pressing Edit on a test session in JIRA, and switching to the Test Report tab)
Random observations and questions
Some practical suggestions:
Autohotkey shortcut to create a timestamp
Something to indicate potential bug (e.g. !!!,
@@,
BUG1)
Something to indicate switch in focus (could just be line breaks)
Notes are primarily for tester's use - other people should only need to read session charter/plan, report and list of bugs.
Time: If expected time runs out, decide whether to stop or continue.
How to convert notes into a report
'Status' = judgement from tester
What is the quality of the function/product/solution?
Why do you think that?
What should we do about it?
'How'
BRIEF explanation of how the testing was done and what was covered.
'Value'
To what extent was testing worth doing?
How valuable is the information we found from the testing?
What have we learnt?
Not just the things that were relevant to the recent session, also stuff that could be useful for other sessions or more generally.
Changes to make
Any new areas of risk?
Does overall strategy still make sense?
Is overall plan still viable?
Obstacles
Anything that could be improved by automation?
Bugs found
Just a list. Ideally everything is raised or otherwise resolved before the debrief.
Aim to spend <30 mins writing up report
Write report ASAP after the session, so it's still fresh in your mind
Debriefer will ask 'Why?' a lot in the debrief. See if you can anticipate some of the places they'll ask it and answer in the report.