Presentation given for a Ministry of Testing Meetup in Cambridge with Neil Younger and Karo Stoltzenburg. It provides basic background on note taking, an introduction to popular note taking techniques and examples on how those can help you with your testing and reporting challenges. It leads into a hands-on testing session using specific note taking approaches of your choice. The evening was wrapped up with a debrief session and discussion.
https://www.meetup.com/MinistryOfTesting/events/234875522/
2. How this started out
● Neil attended Michael Bolton’s RST course
○ … liked the information on collating and visualizing charters using SBTM
■ … and mentioned this in passing as a possibility for a STC Meetup
● … and did a tryout at DisplayLink to collate previously existing notes
○ … and kept thinking about how this could be interesting for testers
■ … and kept discussing his findings with Karo
○ … and they started to look into and compare other note taking techniques
● … and they looked into how note taking in general is of interest to testers
■ … and how it’s actually a quite useful skill, e.g. in exploratory testing
○ … and thought it might be interesting to try a few of them out in earnest
● … and found that note-taking makes a great workshop topic for testers.
3. Reporting Challenges
● What did I do yesterday? Last week? Last month?
● How did I test that story?
● Why did I choose that path?
● Why didn’t I test that?
● How did I find that bug? How do I recreate it?
● What ideas didn’t I follow?
● How did I feel about something?
How do you effectively report your work?
“Learn to tell a
compelling story
that provokes the
right questions”
Michael Bolton
6. Note taking: Why?
● Memory storage
● Support learning
● Record what you do
Source: Austin Kleon
7. Note taking: Why?
● Memory storage
● Support learning
● Record what you do
● Order your thoughts
Source: Austin Kleon
8. ● Different devices
● In real-time vs. after the fact
● Numerous techniques
● … and formats
Note taking: Characteristics
Source: Chung Ho Leung , Ben Kraal
9. Note taking: Some good practices
● Find a format or style that suits you
● … and your context
Source: Kai Schreiber
10. Note taking: Some good practices
● Find a format or style that suits you
● … and your context
● Use a consistent structure
○ For the notes themselves
○ And when organizing the notes
Source: Kai Schreiber
11. Note taking: Some good practices
● Find a format or style that suits you
● … and your context
● Use a consistent structure
○ For the notes themselves
○ And when organizing the notes
● Regularly revisit your notes
● … and your approach
Source: Kai Schreiber
13. Cornell Method
What: Classic Note Taking method, widely in use at universities
How to use: Structure your note sheet into quadrants for title, notes, review and
summary
Benefits: Minimal setup needed, widely applicable, quite flexible
Limitations: Pen & Paper focused
Use it for: meeting notes, studying, as a fallback good practice
15. Mind Map
What: Graphical way to represent ideas and concepts
How to use: Let the map show the areas you covered, the ideas you had, the
bugs you found
Benefits: Visual. Can be tool based or pen & paper / whiteboard
Limitations: Could get crowded / noisy. Some people are simply not ‘visual’
Use it for: Meetings, Talks, Idea recording, and testing logs
18. Rapid Reporter
What: Small application that records your notes in csv format
How to use: Simply enter your notes against the appropriate heading
Benefits: Electronic, standard format, flexible, runs on Windows and Mac
Limitations: Notes can not be edited. Only one line of notes shown
Use it for: Exploratory Testing, and in particular SBTM
20. Session Based Test Management
What: A more formal structure to exploratory testing
How to use: Create charters, timebox work, record, and debrief
Benefits: Notes all follow the same structure and can be parsed by tools to
produce metrics
Limitations: The original tool is quite old and not maintained, however there are
others around
Use it for: Managing lots of exploratory testing
21. Session Based Test Management (II)
CHARTER
-----------------------------------------------
To discover something new
#AREAS
OS | Win10
START
-----------------------------------------------
4/18/16 09:00am
TESTER
-----------------------------------------------
Neil Younger
TASK BREAKDOWN
-----------------------------------------------
DATA FILES
-----------------------------------------------
drformula.xls
TEST NOTES
-----------------------------------------------
Freetext field, one of the important bits.
BUGS
-----------------------------------------------
#Bug 1
A nasty thing happened
ISSUES
-----------------------------------------------
#ISSUE 1
Enter a issue, not a bug here
#ISSUE 2
A second issue
23. What: Individually developed methods or notations,things that just “work for me”
How to use: Either as an individual method, or a flavor of an existing method
Benefits: Ease of use as developed by you / for you
Limitations: Harder to generalize, others might not understand notations
Use it for: Whichever context and situation it works for you
Bespoke / Individual
Please share!
26. The overall mission
Perform a testing session / charter
Using a specific note taking approach
In order to find out whether it suits you and the situations needs
27. Charter: Feedback on the MoT website
Dear Tester!
We finally have the first version of our redesigned homepage up and running.
Could you please have a quick look and give feedback on the website. Ideally this
would include your thoughts on usability, any general comments or any specific
things which need to be addressed. Also if you come across anything that's
broken or a spelling error which needs fixing, let us know!
You can access the webpage here: http://www.ministryoftesting.com/
This is the live page, so please use carefully!
Many thanks, Your Marketing Team
28. Resources available
● Mission and Testing Task
● Laptops (Tablets, Phones)
● Note taking templates and tools
● Test Heuristics Cheat Sheet
● Test ideas
○ Personas
○ Tasks
○ Focus
● And Neil & Karo!
Source: Phil
29. Things to consider when taking notes
● Did you manage to fulfil the charter? Was it followed?
● Any bugs observed that might lead to a new future charter?
● Any issues that might require further action to be taken?
● Are your notes comprehensible?
● Will the notes answer the question ‘what happened in this test session’.
● What about your strategy? Your Oracles?
● Is your coverage clear?
● Do the results of this session suggest the need for another session?
32. Further Reading
● Alan Richardson: 10 Experiments to Improve Your Exploratory Testing Note
Taking
● Anton Angelov: Exploratory Testing Mind Maps
● Michael Bolton: Exploratory Testing Recording And Reporting (pdf)
● Whiteboard Testing: A Key For Test Session Note-taking
● Verbal to Visual The 50/50 Rule Of Visual Note-Taking
Hinweis der Redaktion
Karo:
Welcome, thanks for coming, thanks to DisplayLink, this will be note taking by Neil Younger & Karo Stoltzenburg.
Note taking: General Background
Challenges, Why, Characteristics, some good practices
Some example note taking techniques
Mind maps
Cornell method
Session Based Test Management (SBTM)
Rapid Reporter
Hands-on
Missions, testing challenge
Pick any note taking technique
Discuss and Debrief together
Neil:
l attended Michael Bolton’s RST course
I liked the information on collating and visualizing charters using SBTM
and mentioned this in passing to Karo as a possibility for a STC Meetup
and I tried it out at DisplayLink to collate previously existing notes
and we both kept thinking about how this could be interesting for testers
and I kept discussing my findings with Karo
Karo:
and we started to look into and compare other note taking techniques
and we looked into how note taking in general is of interest to testers
and how it’s actually a quite useful skill, e.g. in exploratory testing
and thought it might be interesting to try a few of them out in earnest
and found that note-taking makes a great workshop topic for testers
Neil:
Here are some typically, to me, reporting challenges that we might face in our day to day work
What did I do yesterday? Last week? Last month?
How did I test that story?
Why did I choose that path?
Why didn’t I test that?
How did I find that bug? How do I recreate it?
What ideas didn’t I follow?
How did I feel about something? - How did I feel about something. We don’t often record feelings but sometimes we get asked about them in context of some testing. For instance, ok so it passed but did it feel ‘right’ to you?
Karo:So why do people take notes?
Memory storage
capture real-time Lectures, Presentations, Meetings
Free your mind from having to recall everything
Karo
Support learning
reading articles, listening to recordings
Taking notes supports remembering and understanding information
… and even more when doing so by pen & paper (more processing necessary)
Karo:
Record what you do
While doing sthg (e.g. a testing charter), to keep track
Transparency -> as a report
Karo:
Order your thoughts
e.g. blogging
test idea generation
Karo:
There are a lot of differences when taking notes, for example:
Different devices
(pen & paper -> electronic tools)
In real-time vs. after the fact
Numerous techniques and formats
Notations, Abbreviations, symbols, shorthand
Linear (outlining, lists, tabular)
Non-Linear (clustering, concept mapping, tree structure, visualising)
… which could be standardized or individual or a mixture of both
Karo:
Some good practices:
Find a format or style that suits you
Not all formats work for everybody (pen & paper > electronic)
.. and your context
Not all format work in every context (meeting minutes > test ideas)
Consider the end purpose of the notes
Consider recipient of the notes
Is it a collaborate note taking? Google docs, Retrospective
Karo:
Use a consistent structure (for note and organization)
Check: If I re-read these in 60 days, would I understand it?
Header (Title, Date, Identifier)
Make the notes self-explanatory
Use structure / mark-up
Keep topics of notes separate
Consider conventions (e.g. for naming notes)
Karo:
Some good practices:
Revisit your notes
…. and continuously improve your note taking -> Alan Richardson: 10 Experiments
Karo:
Before we move onto some example note testing techniques,
Any Questions so far?
Karo:
What: Classic Note Taking method, widely in use at universities
How to use: Structure your note sheet into quadrants for title, notes, review and summary
Benefits: Minimal setup needed, widely applicable, quite flexible
Limitations: Pen & Paper focused
Use it for: meeting notes, studying, as a fallback good practice
Karo:
Systematic format.
note-taking column - Notes from a lecture or teaching
questions/key word/review column (on the left) - key words, relevant questions
Summary - produced after the fact, revising the notes
When reviewing the material, the student can cover the note-taking (right) column while attempting to answer the questions/keywords in the key word or cue (left) column. The student is encouraged to reflect on the material and review the notes regularly
Neil:
What: Graphical way to represent ideas and concepts
How to use: Let the map show the areas you covered, the ideas you had, the bugs you found.
Benefits: Visual. Can be tool based or pen & paper / whiteboard.
Limitations: Could get crowded / noisy. Some people are simply not ‘visual’
Use it for: Meetings, Talks, Idea recording, and testing logs.
Neil:
This is an example of using a mind map in more of a flow based way to represent your path when testing
Neil:
It doesn’t have to be electronic. Two examples of handwritten notes.
Left Example using string and notes
Right Dan Ashby: How I interview Testers. An example of a handwritten one
Neil:
What: Small application that records your notes in csv format
How to use: Simply enter your notes against the appropriate heading
Benefits: Electronic, standard format, flexible, runs on Windows and Mac.
Limitations: Notes can not be edited. Only one line of notes shown.
Use it for: Exploratory Testing, and in particular SBTM
Neil:
Reporter | Charter | Setup | Note | Test | Check | Bug | Question | Next Time
Tool is flexible and you can define your own titles (but still with default for this exercise)
Right click for context menus. Change session time etc.
Count down in blue
Can take screen shots
Can add rich text notes
Single exe and output saved to launch directory as csv
Neil:
What: A more formal structure to exploratory testing
How to use: Create charters, timebox work, record, and debrief
Benefits: Notes all follow the same structure and can be parsed by tools to produce metrics
Limitations: The original tool is quite old and not maintained, however there are others around.
Use it for: Managing lots of exploratory testing
Neil:
Original Format
Example above is missing from ‘Task Breakdown’ the following
#DURATION: (Long)
#TEST DESIGN AND EXECUTION (%)
#BUG INVESTIGATION AND REPORTING (%)
#SESSION SETUP (%)
#CHARTER VS. OPPORTUNITY (100/0)
Neil:
An example of SBTM being used in a spreadsheet
SBMT on googledoc - change to SBTM
Karo:
What: Individually developed methods or notations,things that just “work for me”
How to use: Either as an individual method, or a flavor of an existing method
Benefits: Ease of use as developed by you / for you
Limitations: Harder to generalize, others might not understand notations
Use it for: Whichever context and situation it works for you
Karo:
Some examples here, different pens, doodles, very tense notes, post-its
Karo:
Hands-On session
We explain your overall mission, give you a a concrete testing task and some resources
30 Minutes
We’ll give a warning 5 minutes before the end to wrap up
We’ll debrief and discuss after the hands-on session
Neil:
Perform a testing session / charter
Using a specific note taking approach
In order to find out whether it suits you and the situations needs
This is really about trying out different note taking techniques
Use any of the example note taking techniques presented (cornell, mind map, rapid reporter, SBTM, bespoke methods)
Find Templates for those on either pen & paper or electronic format
If you run into problems, just let us know
Karo:
So this is your testing task. Imagine you find this in your inbox
Dear Tester!We finally have the first version of our redesigned homepage up and running. Could you please have a quick look and give feedback on the website. Ideally this would include your thoughts on usability, any general comments or any specific things which need to be addressed. Also if you come across anything that's broken or a spelling error which needs fixing, let us know!
You can access the webpage here: http://www.ministryoftesting.com/
This is the live page, so please use carefully!Many thanks, Your Marketing Team
Your manager asks you to take this on for half an hour
Karo:
Mission and Testing Task
Laptops (Tablets, Phones)
Note taking templates and tools
Electronic formats (Freemind, Rapid Reporter, SBTM Template, Notepad)
Pen & Paper (Cornell template, blanks, color pens)
Test Heuristics Cheat Sheet
Some test ideas:
Different Personas (Newbie Tester, Test Manager, HR, Test Consultant, NaT (Not a Tester))
Specific Tasks (Find a local Meetup, Contact Us, Report a Bug, Learn about Test Pairing)
Particular Focus (Corporate Identity clear, Consistency, Intuitive Navigation, Usability, Responsiveness)
Neil:
Did you manage to fulfil the charter? Was it followed?
Any bugs observed that might lead to a new future charter?
Any issues that might require further action to be taken?
Are your notes comprehensible?
Will the notes answer the question ‘what happened in this test session’.
What about your strategy? Your Oracles?
Is your coverage clear?
Do the results of this session suggest the need for another session?
Show this slide during the hands-on sessions
5 minutes before end: remind to wrap up