TestChat

Write results in notebook and send email to squad with charter and results...

Any bugs or task suggestions go into JIRA for safekeeping. Straightforward

I use to do mindmaps. Colour code and a notes. But it started to get hard to manage, and preferred pen and paper as I had more freedom to doodle and record observations

colour coded spreadsheet (for now) but would like to start mindmapping

Screenshots, email, log files and face to face hands on show and tell

screenshots / licecap for gifs

I write initial notes in a notebook and then have direct conversations with my PO and developers, often with a live demo. If something I discovered needs action, it goes on a sticky on our scrum board.

what I scribbled on my notepad I summarise into Testlodge and save that in the dedicated QA place for that release/customer. Bugs are recorded in Jira.

so now I take notes and use a key to help me review them afterwards. So if a write a bug I'll draw a bug in the margin, if I have a question for someone I'll draw a ?, a flag if I need to flag something

typically record in simple text editor and share findings with the team verbally, results in interesting discussions

Mac: Images: Custom Shortcuts to save screenshots or copy selection to clipboard + preview + upload to ticket tracker.

screenshots, screen recorder, face to face chat with devs

Evernote, mind maps, process flows

Curious on answers to this so I can sell ET to work.

Bug tracking tools, now TFS

I'm quite a fan of Mindmup for mindmapping as it hooks into google drive easily.

mindmaps, relevant comments in stories, walkthrough, JIRA tickets

@nu_fenix i've kept a note of all the bugs i've found through exploratory testing as opposed to scripted. SO many more found through ET

I'm a huge fan of section based test management (SBTM). It provides some structure, so I do 2 hours sessions, meaning I don't have information overload when I share with the rest of the team http://www.satisfice...

@FriendlyTester Likewise for mind maps. I think they're good for hashing out ideas but I've always struggled to use them to capture my notes during a session. #testchat

Mindmaps to illustrate a graphical chain of thought that spans charters/sessions. Good for small focused efforts. Gets unwieldily if too big #testchat

Videos/Animations: Recordit - to create animated gifs easily http://www.recordit....

@heather_reiduff I really love the face to face communication. I feel like a lot gets lost with written recaps. The devs are usually more engaged and ask questions about how something was tested

I think as long as you have a coherent narrative in mind that's the most important aspect of conveying a testing story #testchat

@DeborahLee89 Nice to hear. Managers think ET is only for gaming industry, not finance sector.

@jasmintestscode Yes, my team is sitting all around me, so communication is simple

Attach session notes to related story/feature so whole delivery team can see

recording your screen while ET can be highly rewarding. Also the logs. So you can provide actual proof you exercised the system. Not just a tick in a box.... or pressing 'pass'

So many people mentioning MindMap. Wasnt a friend of it so far (used it for other stuff) but maybe I have to try to use it for ET!

Currently on a client site I use Google Docs. I split each time-boxed session into three sections: Planning, Setup and Exploring. I then have to link to this in the appropriate JIRA. It seems to do the job. #testchat

We use Jira (Create test session) for our test sessions/charters to track testing progress.

@jasmintestscode & they're much less likely to feel offended when a bug was found & more open to talk about potential solutions

@FriendlyTester +1 for SBTM! The structure forces me to take breaks and reset my brain between sessions and provides convenient time to review results with dev/PO

I need to write about this. I've also tried heatmaps. So model the system, and map commits to it to gauge a score. Then layer checks and ET sessions on it, to show the focus applied verse the perceived risk

@FriendlyTester I tried to use a recorder (forgot which one, the one recommended by James Bach...).. files got soooo big....

@FriendlyTester Heatmaps?

pairing with a developer :)

@nu_fenix As far as I can tell, the testing procedures at my gaming company are much better than those at Equifax, so finance should take another look :)

Mind maps has changed the game for my team, we also added cool symbols and colours to mark different things

When not on a client site I use TestBuddy (a tool I'm building with Rajit Singh). It helps testers capture and share their notes. https://testbuddy.co #testchat

@FriendlyTester nice! Would like to hear more about this

I refer you to @SimonSaysNoMore 's excellent CAST talk about how he creates, categorises and logs his testing sessions.

@ambertests Very true ;)

For sharing our findings its normally a conversation with a dev followed up with any bugs opened in jira with clear steps to reproduce.

@ButchMayhew What, does it have a specific feature for sessions?

@FriendlyTester what tool do you use for heatmaps?

@nu_fenix yes. So create a model of the system with 'sections' aka Profile, Directory, Admin etc. Then map commits to those areas to get an idea of change. More changes means more thinking or more focus. Then use same model on checks

I've also found this with videoing a whole session. I think it misses a trick of getting to the juicy bit – just a lot of not so interesting video to trawl through. Perhaps one day they'll be a tool to help with this. #testchat

For collaborative exploratory performance sessions, I share lots of images, stats, urls and views into a chat session/slack/hipchat with others

@deefex read about them lately, still very undecided about the usefulness

@FriendlyTester amazing idea! Any tips on how to map the commits?

@TestPappy Ah, but useful to who? Session logs are primarily for the tester's benefit, no?

I've also been mob testing with my devs lately - the sharing happens along with the testing!

@deefex this reminds me of @Marcel_Gehlen's incredible Pathway Exploratory Testing post. So much useful information! http://thatsthebuffe... #headexplodes #testchat

@jasmintestscode mob testing brings huge benefits

@deefex imo it’s a bit steamroller tactics to press everything into sessions for documentation and archiving

@jasmintestscode I wish I could get my devs to pair or mob - they get very bristly

@FriendlyTester @nu_fenix decide what risks are remaining, Then plan your ET sessions accordingly then add them to the map. and reduce the 'heat' So 100+ changes is red. Checks took it to orange, two ET sessions get me to green

write down everything that needs follow-up on post-its, talk to product to see if they feel like any of the findings require immediate action. the bugs are written down in Jira in either case, and put in the current sprint if they're hot

@ambertests probably too long for this but do they give reasons why they're bristly?

i think pair testing (either with other testers or devs) to show the benefit of the way we work, and how we explore. @nu_fenix this could be a good idea to sell it too

@heather_reiduff They just want to do their own work alone. Totally fine with code reviews, though

@TestPappy We need to talk about this, my grumpy brother. ;-) #testchat

@ambertests it started with me mobbing on the development with them - they saw the benefits there and (luckily) were happy to try it out for testing as well

I write notes imagining I'm taking someone through my actual process/steps/thoughts whilst exploring. Imagine saying it out loud and just type. Can always edit later before debrief/sharing #testchat

some of the most important discoveries to share are. Shit worked!!! If it works, tell people to praise the team. But also, that more sessions may be needed, I discovered we need to do more.

@simon_tomes Hadn't seen that article. Thanks for the share.

@DeborahLee89 A sub-team has tried pair, but they see it as taking twice the overall time.

@nu_fenix I want to get more doing it, and also try mobbing after reading about it.

@deefex sure, mate. You know where to find me.

@FriendlyTester I do that with devs, so they don't associate me coming to them as bad news only.

@ambertests would they try it as an experiment/one off then if they don't like it, retrospect on why. Drop it then if it's too much?

@simon_tomes Yeah, he mentions TestBuddy quite a few times, doesn't he? ;-) #testchat

@TestPappy @deefex pub?

@TestPappy Manchester, in a few week's time.

@deefex yes, sir