Testing your Ideas

In line with Dan’s keynote on “Testing the Ideas”, this tutorial will dive deep into the theory and practice of what it means to test ideas and how to do it effectively. Participants will get the chance to discuss in detail various aspects of this topic – what it is, why it’s valuable and how to do it. And they’ll get the opportunity to get hands on practical experience through lots of different exercises and challenges.

The tutorial will be split into 4 parts:

  • A deep dive on investigative testing vs assertive testing and how it relates to Continuous Testing.
  • Testing the ideas and artefacts (before a line of code is written).
  • The output of testing the ideas – testing notes that feed better design and prevent bugs and assumptions.
  • Getting yourself into the pre-development discussions – how to communicate about testing to get into the early meeting about the ideas.

The style of tutorial is very open. There will be small group and whole group discussions, white-boarding from Dan, and lots of exercises with debrief sessions relating to the 4 parts.Participants should bring laptops, paper and a pen.

Further details or what participants should expect to obtain from the tutorial :

  1. What is testing and what we mean by continuous testing?
    By the end of this section participants will be able to:

    • Detail different perspectives of what testing is.
    • Describe what software testers do.
    • Experience and debate the difference between investigative testing and scripted testing.
    • Understand that software testing is a complex role.
  2. Testing the ideas and artefacts before writing any code
    By the end of this section participants will be able to:

    • Describe how to test ideas
    • Discuss why testing the idea of a software solution is important and the value of doing so
    • Apply techniques and heuristics to question and investigate ideas
    • Understanding of testing the ideas in an agile context in comparison with a waterfall context
  3. Testing notes – the output of our investigative testing
    By the end of this section participants will be able to:

    • Describe a number of different approaches to note-taking
    • Explain why note-taking in testing is important
    • Apply different note-taking approaches to different testing scenarios
    • Evaluate the pros and cons of note-taking approaches when testing ideas and testing products
  4. Talking about testing – getting yourself into the planning sessions
    By the end of this section, participants will be able to:

    • Describe different forms of communication and why communication is important
    • Discuss some of the challenges surrounding communication and how to overcome them
    • Influence others to be able to get involved in earlier discussions to help with testing the ideas.
    • Explain software testing more fluently to others
    • Apply techniques to help generate conversations about testing
    • Evaluate the pros and cons of different communication methods in general
Full Day Tutorial Testing