Collaborative Exploratory and Unit Testing

Collaborative Exploratory and Unit Testing

How to harness the insights of bug discovery to protect your code.

Cross-functional teams have team members with specialized in-depth skills. Collaboration between team members has a significant impact on the team’s ability to deliver value efficiently. In this course, we teach you how to pull together the tester-facing discipline of Exploratory testing and the developer-facing discipline of Unit testing. To do this, we create insights into the product and code through exploring and leverage these insights via unit testing. This course invites testers and developers to join and learn to boost their collaboration to the higher level.

The course teaches from the premise of combining forces of machines and humans, leveraging developer and tester skill sets. Machines are particularly well suited for exploring large computational space. Machines enable us to cover variations, in cases where manually we would sample and potentially miss problems. In variations and repeating, computers will easily outperform humans. What they can’t do is have any insight or creative ideas. That’s where humans excel and testers in particular have refined the skill to creatively understand and use software to gain understanding and insight into its quality and weaknesses.

While the focus of the course is on harnessing the insights of a bug discovery to protect your code with automation, you will also shape up your basic skills on how skilled testers think while exploring to effectively find problems with the product.


Target Audience - Why join?

The course allows for a mix of managers, testers and developers to participate. We explore in pairs and implement unit tests in a mob with a style of pairing where the navigator on the keyboard gets to follow the instructions from the group (strong-style pairing). The facilitators help in getting the tasks done balancing the available skills in the group.

Why should a developer join this course?

  • Improve understanding of experimenting with the product through exploratory testing
  • Boost ability to deliver value by collaborating well with testers
  • Improve ability to turn testing observations into useful ideas for unit testing
  • Get ideas on how to use Approval
  • Tests-framework to boost your unit testing capability; from spot checking to brute checking

Why should a tester join this course?

  • Become more helpful for developers by not only communicating bugs found but also ideas from exploration that could be used to improve unit tests
  • Build understanding of the connection of insights from exploring the product, to exploring the code to creating a unit test
  • Enhance skills in testing: from test cases to exploring with understanding of what information developers would find useful
  • Extend abilities to implement relevant checks

Why should anyone join this course?

  • Improve collaboration skills in paired and grouped hands-on work
  • Build mutual understanding and respect for developer and tester skill sets
  • Learn how to foster developer-tester collaboration in teams

Content

  • Course Principles and Introduction
  • Lines (height, distance, name, testing, programming, exploratory testing, automated testing, unit testing, Android & iPhone)
  • Strong Style Pairing Exercise Phone
  • How to obverse Patterns
  • Introduction to Mobbing
  • Exploratory Testing + Retrospective:
  • Explore Space – Build Map (very little guidance)
  • Basic use case (add guide)
  • Test Specific Area (animations) + Retro
  • Report a bug + Retro
  • Unit Testing, Seams (Guided mob) + Retro
  • White board and multi-cases + Retro
  • Overall Retrospective and Closing Summary

Agile Coach: Llewellyn Falco

  • Duration: 1 working day, from 9am to 5pm
  • Certification: No
  • Price: 350€ + VAT.
    After the registration Companies will get the invoice and should make a payment on our account in Komercijalna Banka using the selling exchange rate of that bank on the invoicing date.
  • Date: TBA
  • Location: TBA

More information via email: scrum@puzzlesoftware.rs Sign Up

How it was on the previous training?