@the_qa_guy @alex_schl @lisihocke I have tried a lot of combos and emphasis over the years. At some point I was writing about those in my blog, but recently I have not been up to anything special - just a standard user for all things #EnsembleProgramming and #EnsembleTesting.

A common confusion with #EnsembleTesting is with the patterns of speaking. While the ensemble yields control to navigator unless they have an idea of better, driver reviews and adapts instructions, and asks for clarifications.

The social software testing stuff - #PairTesting and #EnsembleTesting taking me to #TestingTours has been transformational practice. It gave me what the core leaders pretended they had inherently - other people's experiences and perspectives. Having collected ideas from thousands of people on how to look at an application or a piece of code has improved me more than any reading or course ever. Yet it feels like hardest thing for people to get to.

Half-day tutorial on social software testing approaches with #PairTesting and #EnsembleTesting at #EurostarConf done. Materials at https://speakerdeck.com/maaretp/eurostar-tutorial-social-software-testing-approaches

#EnsembleProgramming or #EnsembleTesting on #python #playwright with @ez and @alex_schl is always the highlight of the day. We have so much fun with naming things and playing with language.

Adventures in #Playwright with @alex_schl and @ez part N: deleting a line from a table to learn deletion isn't implemented with the test target.

We have almost too much fun with this stuff. But only almost. #EnsembleTesting FTW.

One of my favorite examples of early #EnsembleTesting 2015. 201 people working together to test a system that has 201 points of control, end result of finding problems a year of delay in acceptance and installation of the system. One designated navigator leading efforts, and all hands on controls. A lot of times it is better to have one pair of hands and group off keyboard raising the quality of end result. Learning or contributing.