Keeping Test Notes

# 

## Notes


## Potential problems


## Testing issues


## Other test ideas
  • every such Markdown document has a title that reflects what I’m focusing on during the testing session
  • I put the majority of my notes into Notes section, including start and finish time, environment setup, etc.
  • Potential problems are things that look like bugs to me when I stumble upon them. These can later become real bugs the team will solve.
  • Testing issues are things I struggle with during the testing. These are things that prevent me from performing as good a testing as possible. Testability issues can come in here.
  • Other test ideas are things I notice would deserve more testing but are out of scope for my current session. I’ll likely get to these in later sessions.
![image](picture_path)

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Design it; Code it — Ingressive FCE_ABEOKUTA Meetup 1.0

7 UX Tips for Designing Killer Landing Pages

50 Shades

UI Interactions of the week #207

Historical Viz Digest: Issue 3

Reflection Point: Icons

Designing UX for Web 3.0

6 Design Essentials for Indian Kitchens

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Pavel Saman

Pavel Saman

Tester

More from Medium

The foundations of the Agile method | Agilitest blog

Environments in Postman

Ways to Declutter Old Backlog Bugs

Why Automation Testing Is Important In Agile Development?