AgileTD 2015 - Highlights

Summary of talks attended by me or Maura Licheri during Agile Testing Days in Potsdam 2015 - for sharing with other test colleagues

Transcript

1. Agile Testing Days 2015 (just the good bits)
2. Day 1: Keynote “When music speaks”
3. Day 1: Experimenting with exploratory testing Story of twice going to a ‘test script’ style company and proving that exploratory testing was a valid alternative. Have to find “Minimable Acceptable Bureaucracy” within each company @maaretp
4. Day 1: Automation in Testing @friendlytester Don’t just use automation for regression checks. * automate getting test data created and to the correct page in a flow on several browsers before starting testing * automatically collect testing artifacts together after session - logs, screenshots and Evernotes * logs make beeping noise when an error is thrown * test data creation, api with easy frontend for POs, could also work via slack
5. Day 1: Workshop - Change Dojo learn by experience: chair guiding Exercises: guide does not speak, guided is accompanied with hands guide only speaks out instructions, guided must follow guide accompanies with hands and gives status update guides ask guided how they want to be guided
6. Day 2: If I can do it, so can you - Dr Sue Black Catching up with university around her 30’s Successful campaign to save the site of Betchley Park, in UK - Enigma during WWII. She spoke about: • Confidence and how to enjoy networking • Determination • Innovation and transformation • Education and technology • Opportunity and social inclusion
7. Day 2: Human refactoring experiment - B. Beecham for teams and individuals: what do you bring to the search? relevant to us: What does a tester bring to the team? Typically: - love of exploration - passion to collaborate - desire of making things better - design safe-to-fail experiment - passion for monitoring and checking
8. Day 2: Note taking using mind maps Mind maps are an efficient way to visualize, memorize and to communicate information example with XMind: Exploratory test reporting creative note taking stimulates creative thinking
9. Day 3: Don’t refactor, rebuild, kinda - by W.Lagerweij Strangler pattern: Make something new that obsoletes a small percentage of something old, and put them live together. You do some more work in the same style, and go live again (rinse, repeat). From an old technology solution to new one
10. Day 3: Improve collaboration -
11. Day 3: Improve collaboration
12. Day 3: Improve collaboration • Know yourself and your team mates • value individuals over processes and tools • avoid labels and being judgmental • build respect and trust: safe environment: be aware that individuals fear more blame and criticism, than failure • One Size does not fit all
13. Day 3: Test your cognitive biases - O. Juncu Knowledge bias Confirmation bias Familiarity bias Status Quo Bias https://en.wikipedia.org/wiki/Monty_Hall_problem
14. BUT: Talking about biases: learn by patterns our brain learns by patterns: Making Badass Developers - Kathy Sierra (Serious Pony) keynote https://www.youtube.com/watch?v=FKTxC9pl-WM
15. Lean Coffee “How do you get team to test earlier” Ask devs to “Show Me” Refuse to be their quality safety net “How do you get distributes test team to stay a team” Call it a test community lightning talks - 7 minutes each sharing something new/interesting “How do you sleep at night”