product owner, manager • A huge fan of working in agile teams • A whirlwind and a geek ▪ About my work: • Software development company in Germany called BREDEX • 120 people, 15 of whom are my testers ☺ − The rest are developers, architects, consultants, UX, ... • Focus on quality during development • Strong preference for agility @alex_schl
the testers! Then I only have to pay for all- rounders… Ah, so you do the whole quality! Awesome. Kthxbye Er, so what does the tester actually do? I don’t wanna be a tester!! Testing is below my pay grade… Not. Gonna. Happen. Never. Gonna. Work @alex_schl
• And you wanna get rid of the specialists?! ▪ Testers are stakeholder and team glue ▪ Role goes beyond doing ▪ Just because testing is the activity name doesn’t mean it’s all testers do ▪ Focus: there can only be one ▪ Passion! @alex_schl
(still) not saying that developers should do all the testing ▪ But their perspective and skills can help the whole team ▪ And let’s remember that testing more and more often is A Good Thing™ ▪ Testing is natural. Everyone can do it and everyone can improve at it @alex_schl
important things I don’t know how or what to test Testing isn’t my job / role • Exploratory Testing is a rather natural process • Cheat sheet • Practice makes perfect! • Mob testing • Testopsies • Yes it is. It is part of the development process #sorryNotSorry • Testers support with charters, coaching, expertise • Only DONE is DONE • We all have blind spots • Developers may find things a tester won’t • Avoid testing your own things • Discuss possible risks for use as charters @alex_schl
action? Can that friendly developer come and give us a group code review? I’ve started being able to look at code from a different perspective I want to learn more Java! I’m interested in pairing with testers… for other tasks too Java for tests is different than for code… We should think about other tests too… @alex_schl How are you writing UI tests?
that programming ability is binary ▪ We also need to get over the idea that it’s the most important ability or factor • Even if it’s the easiest to see… ▪ Also.... Maybe?! @alex_schl
Knife“ agile team member™ ▪ Diversity is important ▪ No silos does not mean everyone is the same ▪ Blur lines without merging roles (focus & specialization are important) ▪ Encourage equality in importance of roles ▪ We don’t expect the same from BA’s, UX, … @alex_schl
engineering) - Encourage open communication - Speak about conflicts @alex_schl Activities (things to do): - Futurespective: perfect enabled team for whole team quality - Expectation and role mapping - Skill matrix - Sit next to a developer Practices (things to observe): - No “to test” lane - WIP limit - Mobbing and pairing as routine - Testers as consultants and coaches - Reviews between multiple roles - Pairing on automation and code - We > I Things to ask: - “What are you doing?” - “What can we get done today?” - “What are we going to test where?” - “Can you help me?” Antipatterns: - Only the tester does hands on testing - “To test” still kind of exists - Anyone with a silo - A type of test belongs to one role alone Learning: - Teach everyone some testing and some coding - Bring in an external expert
▪ Chameleons not chimeras! • (Also not panic penguins) ▪ Be humble but confident; learn, teach and share ▪ Keep evolving and learning ▪ Talk to people. It’s magic [email protected] @alex_schl