I write my own in OneNote. I have a template I’ve written that lets me indicate what kind of exploring I’m doing (recon/survey, general exploration, deep coverage, bug fix verification), the start date and time, a description (the charter/mission), any linked information (the case details in our case tracking software, tools I used, model artifacts I employed, the name of a screen recording video file, whatever I think will be useful because it’s unusual or unique to this session). Then I have a notes section that includes my freeform test notes and two areas for bugs and issues in case I don’t want to raise them straight away - so that I don’t forget to. Then a section for environmental information such as the version number, database file, particular screens/windows I was testing. Then the end date/time, a completion checklist, and a space to write the name of the person that debriefed the session (if any).
These are stored as pages in a OneNote section, the completed ones going into a “Complete” subgroup so I know which ones are left to do. I export them as PDFs and attach them to the case. I have one section for sessions and one for threads, and yet another for project-related information. These live in a section group named after that particular project.
I only write these if I think the value of writing stuff down outweighs the cost. If I want to do more freeform, less formalised work (heavily defocused stuff, time-based stuff that doesn’t lend itself to note taking) then I’ll add a screen recording and write little.
OneNote has a great screen clipper and it’s great for pasting screenshots and creating tables and pasting excel areas and whatnot. I use the tag shortcuts for “To Do” to create a list of tasks to keep me on-point for the charter (keeps my test framing in check), and I have custom ones for “important information”, “question I don’t have the answer to yet” and “I think I found a bug”.
If I ever have written test cases they’ll be in these notes or in an excel file attached to them.