posted 27 Jun 2014, 00:32 by Neil McLaughlin
updated 24 Jul 2014, 01:33 by Royd Brayshay
David Evans: Setting a Good Example
To get the most out of Specification by Example (SBE), Behaviour Driven Development (BDD) or Acceptance Test-Driven Development (ATDD), you need much more than the right tools. You need high value specifications. How do we get the most out of our specification and test writing effort? How do we turn vague business-speak into testable scenarios? How do we express good acceptance tests that are both readable and automated? How do we distinguish between Stories, Specifications and Scenarios? These and other questions will be addressed in this talk in which we take a practical approach using real-world examples.
If you work with Cucumber, Fitnesse, SpecFlow or similar tools to support BDD and SBE, you will learn how to avoid common mistakes that teams make when writing tests. You will also learn to recognise the characteristics that take good example scenarios beyond the role of acceptance tests and into living documentation for long-term value.
Bio: David Evans is an experienced agile consultant, coach and trainer with over 25 years of IT experience. A thought-leader in the field of agile quality, he has provided training and consultancy for clients in the UK, USA, Ireland, Sweden, Germany, France, Australia, Israel, South Africa and Singapore. A regular speaker at events and conferences across Europe, David was voted Best Keynote at Agile Testing Days 2013. He has also had several papers published in international IT journals. He currently lives and works in the UK, where he is a partner along with Gojko Adzic in Neuri Consulting LLP (www.neuri.co.uk).
Gwen Diagram: Introducing Agile into an Environment where Automation doesn't exist
Regression! You must regress! This is what a waterfall tester has had hammered into them before any release. This is fine in a waterfall environment but when the releases go from 7 months to 2 weeks it's impossible to regress the entire application without automation. If automation doesn't exist how can the testers survive?
This is a talk on the importance of the tester being able to choose their own tools, knowledge sharing between developers and testers and identifying the parts of the system to automate with the help of agile.
Bio: Gwen Diagram started using a Dick Smith System 80 in Preschool, first saw the internet when she was 8 and spent a misguided youth on IRC chatrooms from the age of 10. She's worked in IT support and moved into Testing in 2011. She has a great fondness for telephones (mobile, PBX or SIP), databases, Ruby and breaking things. Working in a Waterfall environment she was dragged kicking and screaming into Agile in 2012 with no automated tests. @gwendiagram