Thank you for raising the tickets, which I forgot to do yesterday . I intend to get more feedback with more testing, when I can get both the time and the energy, so basically when my condition permits me.
How I currently work is I’ll write test notes like stuttered prose, stating what my current aims are, or briefly saying what my next experiment might be, and my thoughts on the validity of that, or further testing or risks or whatever. As I’m going I’ll put anything I want tagged on a new line, and press Ctrl+[a number] which represents a tag. I then go back afterwards and decide how to resolve everything.
I use tags for bugs, issues, important thoughts (includes test ideas) and questions. Bugs are problems with the software (“user input form is missing”), Issues are problems with the project (“I need access to the database that I don’t have”, “this needs automation hooks in it for me to test it better”, “this will take a long time we haven’t budgeted for”), thoughts/test ideas are usually risks or what I call risk-adjacent concepts that have to be resolved down, questions are stuff I need answers to that I usually need another person or other resource to answer. They can overlap, but I find that bugs are the most unique because that’s me saying “probably have to report this”. It doesn’t matter too much because I’ll go back and check them all at the end, and maybe already have answered my own question or found an observation to be invalid.
In the spirit of trying to be helpful, here’s some of my recon notes I did for the software, in OneNote, so you can see some examples. If you don’t want this out there let me know and I’ll remove it.
- The exclamation mark is a thought about future testing. It tells me that there’s a whole area to test, but I’m asking myself if it’s a plugin (not “our” code, someone else tested it already so is lower risk, may be hard to fix if broken), or if you wrote it (higher test priority, fixable).
- The checkbox I usually use for bugs, now, so that I remember to tick the box when I’ve investigated and raised/not raised the bug. Here I’ve noticed something about the usability of the UI, but I haven’t investigated it, tried workarounds, different settings, see if it’s tied to Windows, etc, so the box is unchecked.
- I use screenshots to help, in line with my notes, so that I can make reference to them. Here I’m describing the button panel, and I can use these as subheadings for immediate further testing.
- My question here is an expression of surprise, to remind me that I wasn’t expecting the behaviour, but also to find out how it’s supposed to work. I would have to go to the documents later and look it up, and find out if I’m just wrong about my assumption - the assumption is a useful discovery, even if I was wrong to assume it. It could have gone under important thoughts, or even bugs, but I find that careful categorisation of notes adds very little and acts as a distraction.
That’s essentially how I use notes and tags. Short paragraphs, and new things on their own line with a tag. When I’m doing this I go to a new line, type it out, use a keyboard shortcut for the tag, go to a new line, and that’s it; so my preference with the software would be the same thing in a different order - keyboard shortcut for, say, “bug” (problem with software), then write it out, then submit with a keystroke or shortcut, and move seemlessly on with my notes.
So that’s my flow. I want everything with absolute minimum of friction because as I write notes I’m also evaluating and problem-solving, and expounding ideas, especially in recon sessions where I’m super defocused and concentrated more on observing than detailed experiments. I use tags because I want to make sure I action something: bug investigation, inventing new charters, updating a risk catalogue, asking a question, informing someone of a problem, solving a project issue, think about the causes of bad emotional reactions, follow up on confusion with more research and testing, whatever. The notes are what I thought and did, the tags say “do something about this, sooner or later”.
Hopefully that’s of some help!