Pablo Garcia MunosSharpness AB, Sweden
Pablo Garcia started as a tester in 1996 for Ericsson.
After passing through roles like Test Manager, Project Manager, Program Manager he worked as Total Program Manager managing the complete the Ericsson Development in India.
Now, over 20 years later he has run over 50 assignments besides running his own test companies.
After working as a CEO for a international consultancy he has now started his 5:th company “Sharpness” with specialist in development and testing.
Pablo has spoken at national and International Conferences like NFI, Test management Forum, many SIGISTS and Star West. He has also given Testing courses since 2001 and released a book on test design.
Amongst other he has educated over 400 nurses in acceptance testing during the last 8 years.
The testers major dilemma: What test method is the best?
We are overwhelmed with test specialists and Agilists that wants to enlighten us with “The Best” test and QA methodology.
Exploratory, Context driven, ISTQB, IEEE, Structured, SAFe, Agile testing, RUP, BAM, Agile, RAD testing, mama-test or even “Cosytest” (yes those are test methods) ???????
Most of the times testers get disoriented and just do not know who to believe.
Pablo Garcia has worked with QA and Testing since 1996, he has vast experience of test fanatics from the most test religions. He has always both discussed and dug deep into the processes of the methods before having any conclusions.
Even though it might be fun to hear somebody from the context driven group with the IEEE it is mainly not constructive.
Join Pablo Garcia in his keynote where he describes all the different test methods and “test religions” and get a deeper understanding of the most common ones as well as hearing the conclusions he has made.
Michael BoltonDevelopSense, Canada
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. In 2006, he became co-author (with James Bach) of Rapid Software Testing (RST), a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Since then, he has flown over a million miles to teach RST in 35 countries on six continents.
Michael has over 30 years of experience testing, developing, managing, and writing about software. For over 20 years, he has led DevelopSense, a Toronto-based testing and development consultancy. Prior to that, he was with Quarterdeck Corporation for eight years, during which he managed the company’s flagship products and directed project and testing teams both in-house and around the world.
Demonstration, Experiment, and Testing
What's the difference between a demonstration and an experiment? Questions like that sound like philosophy, don’t they? Why should that difference matter to managers, developers, teams, and... testers? Who cares?
Alas, in software development, we often call both demonstrations and experiments by the same name: "tests". That’s a problem, because a demonstration shows only that a product can work in a specific set of conditions. Worse yet, a demonstration can even be staged to show that a product can appear to work without actually working at all. By contrast, the essence of a test is an experiment; configuring, operating, and observing a product to learn something about it and its relationship to the world around it.
In this presentation, Michael Bolton tells how scientists (and, yes, philosophers of science) came to differentiate between demonstration and experiment, and why being clear about the difference is essential to good testing. We test to learn about the product and to discover important problems about it, so that our testing clients can address those problems before it's too late.