18 - 20 May 2016 in Prague

The website of last year conference can be found on 2015.czechtest.com


Exploratory & Session Based Testing

Positive:
Exploratory testing is a very effective and efficient approach to testing software, and other systems, too. Sometimes - very rarely - it should fully replace other approaches. Always, it effectively supplements other approaches.

Negative:
To an alarming extent, the exploratory approach has become more an ideology than a test approach. This sad fact has nothing to do with the approach itself, but it is a purely social phenomenon. fanned by hype and false propaganda. This has some benefits, since it has helped to diffuse good exploratory ways, but it has serious drawbacks as well, since it may lead to worse testing by - wrongly - discarding most non-exploratory methods.

 

In my tutorial, I will concentrate on how to use the best parts of exploratory approach, but at the same time to understand its costs and limitations.

  • An experiment: let's test it!
  • The story: four testing schools, context-driven school, exploratory, rapid testing
  • The anarchistic revolution: have agile, lean, exploratory and XP anything in common?
  • Is exploratory testing really context-driven? Only to some extent
  • We all do some exploratory testing even without knowing it
  • What does exploratory really mean?
    1. Context-driven adaptation of test approach to real needs (HTSM)
    2. Using non-standard requirements sources and inspirations
    3. Creatively designing test cases while executing test cases
    4. Simultaneous learning, test execution and test design
    5. No advance test case specification
  • Isn't exploratory testing really exploratory requirements elicitation?
  • How can exploratory principles be used in non-exploratory context?
    Examples
    1. Context-driven adaptation of test approach to real needs (HTSM)
    2. Using non-standard requirements sources and inspirations
    3. Creatively designing test cases while executing test cases
    4. Simultaneous learning, test execution and test design
    5. No advance test case specification
  • Comparison between exploratory and non-exploratory: relative benefits and costs
  • Finding three right balances: how much QA, how much testing, how much exploration
  • Freestyle versus managed exploratory testing
  • SBTM: how is it done
    1. Session planning
    2. Session execution
    3. Session reporting
    4. The full picture: session of sessions
  •  

    Bogdan Bereza, Victo, Poland

    Bogdan Bereza

    Bogdan is known for his pragmatic yet creative approach to quality issues and for his ability to cross-connect between areas such as programming, design, requirements engineering, testing, and project management. Over the years, he has bridged knowledge gaps between technology and psychology, as well as between iterative (including agile) and sequential approaches. He has committed a few books, and many articles as well as conference presentations on these subjects. He is ardent supporter of IREB, co-founder and vice president of ARE. He is a grumpy and critical lover of agile and exploratory, which he teaches at Agile Academy in Sweden.