,
14 tweets,
5 min read
Read on Twitter
The Observatron v0.9 now allows you to add simple text commentary as you test using a keyboard shortcut, this is logged as a json file with an optional screenshot e.g. "! menu should not look like that" would save it as a 'bug' note github.com/eviltester/obs… #SoftwareTesting
It isn't as pretty and doesn't produce reports like this extension from @morvader chrome.google.com/webstore/detai… #ExploratoryTesting
And isn't as pretty as Rapid Reporter testing.gershon.info/reporter/ #NoteTaking
It isn't even as fully featured a logging tool as this little #ExploratoryTesting tool I wrote in 2012 github.com/eviltester/exp…
It is designed to augment and support my existing note taking approach. I like tools that augment my process and work together. So I use multiple proxies to observe, interrogate and manipulate HTTP traffic.
I use FreePlane for mind mapping, because I can write Groovy Scripts that allow me to output the information in different ways. Here's an extract to markdown script that I use regularly when creating conference slides and other written material github.com/eviltester/mm-…
I write most of my logs as text in markdown format so I can use multiple tools for reporting in different ways, and it is easy to parse for custom tools I write.
I often write scripts to augment my existing tools, or extract information from them, or combine information from multiple tools together. Rather than look for a new tool. Often these are tactical, and just for my use.
I sometimes wonder what other tools I don't know about, but I don't maintain a tool list any more. I tend to use a combination of tools, and only look for tools when I have a gap in my modelling, observation, interrogation or manipulation abilities.
It was only as I was writing this extension that I stumbled across @bugreplay which is a commercial cloud tool that captures similar information as the extension I've written bugreplay.com
I built this extension because I realised I had a gap in my observation and interrogation abilities... and because I wanted to learn more JavaScript, and experiment with extensions.
Do experiment with multiple note taking approaches and tools to find a way that works for you, based around the process and the software that you test. Caution: spend more time using the tools, than augmenting and looking for new tools. (I've fallen into that trap too often)
Actually I wrote it around 2004,2005,2006 but only released it to github in 2012
And I only found it because it was mentioned in the testersio.slack.com channels #synchronicity
