Exploratory Testing Lab
Testing in your context
Exploratory testing is about making an effective use of our available resources, skills and practical knowledge and about finding as many high severity defects as possible within a certain time limit. It is based on the tester’s skills, knowledge about testing and system at hand, and known testing methods and tools.
Exploratory testing is often integrated in the test strategy together with regular manual testing. As testers, we learn about the system more and more during the project, and additional 'exploratory tests' (or heuristics) should be added continuously to our current manual test cases repository.
in this workshop, participants will go from theory into action within a few days, exercising what they have learned in class, on their own test environment and SW product.
Testers, testing team leaders and test managers, that would like to know what is Exploratory Testing, how to plan it, run it, measure it, and improve in doing it.
But not only that - later on, implementing it in their own company, using their own context.
The objectives of this workshop is to give the participants to
- Acquire knowledge on the methodology behind Exploratory Testing
- Run a coached session, implementing Exploratory Testing within your company, using YOUR context
This workshop is from the T&C series of train and coach. It involves a training course in the beginning, followed by a coaching sessions of implementing Exploratory Testing in your company.
The coaching is adjusted to company’s own context and day-to-day, Charter, ET reporting, ET Debriefing.
Participants should have basic testing knowledge about testing life cycle, testing techniques and methods, test measurements.
Note: running ET sessions (days2+3) shall be done on customer's test environment, testing your own products. Setup of a few test environments for the workshop is necessary.
Note: The current suggested format, supports a small to medium size teams. For a larger group of testers/managers, additional days might be needed.
Also, if the product and project environment are very complex, further days of introduction & planning might be required.
Mr. Alon Linetzki - is an expert test engineer, testing coach and a testing consultant with over 23 years in testing, and over 33 years in IT. During his career, Mr. Linetzki have participated and managed various types of development projects and testing projects with a large range of technologies, size and sector domain orientation from telecommunication and finance, to banking and embedded systems.
He is the author of multiple testing classes, including: Testing in an Agile Environment, ISTQB® Agile Tester, Exploratory Testing, Measurements and Metrics for Making Good Quality Decisions, Test Process Improvement Using TPI®, Risk Based Testing, Writing Good Test Requirements, and Test Automation for Decision Makers, Introduction to Test Automation, Personal Communication and presentation Skills, Root Cause analysis in Testing and Adding business value increasing ROI in testing, and more.
Mr. Linetzki is a popular speaker in international testing conferences since 1995. He is the co-founder of the Israeli Testing Certification Board (www.itcb.org.il), and the founder and chair of SIGiST Israel (www.sigist.org.il). He is leading the ISTQB® Partner Program worldwide as part of the marketing working group. He is also one of the authors of the new ISTQB® Foundation Level Agile Tester Certification, and is involved in the next level certification of ISTQB® Advanced Level – Agile Technical Tester. Mr. Linetzki is also the ISTQB® Marketing Chair (March 2016).
Day 1 - Training Day agenda
- Presenting participants and trainer
- The different testing tactics and approaches
- Basic skills of Epistemology
- Tester's skills and attitudes
- What is Exploratory Testing?
- How do testers think?
- Exploratory Testing Heuristics
- Where and when to use ET?
2. Types of Exploratory Approaches
- ET Approaches/Styles
- Touring Heuristics
- Exploratory testing obstacles
- Constantly seeking risks…
3. How to run Exploratory Testing sessions?
- How much planning is done in ET?
- Introducing the Test Session
- Exploratory testing – step by step
- Writing good Charters
- Exercise: Writing Charters
- What to do during an ET session
- Exercise: Reporting & documenting
- What to document during an ET session?
- The session report sheet
- How to debrief after an ET session?
- Measurements of an ET session
- Exercise: Debrief + retrospect
- Example Exploratory Test session - excel
4. Bug Hunt & Bug Safari
- Situations for performing a Bug Hunt / Bug Safari
- Ingredients of Bug Hunt
- Soap Opera Scenarios
- Main benefits of Bug Hunt and Bug Safari
- Main uses of Bug Hunt and Bug Safari
5. Retrospective Day 1
- Your "take-away" from this course
- Summary discussion
Day 2+3 – Coaching Exploratory Testing in context
6. Charter Planning session with test team leader/s & test manager
7. Guided Exploratory Testing Execution sessions
- 2-3 rounds of 1-2 hours (per day) - with test engineers/team leaders (usually in Pairs),
- Plan, document the session execution, opening defects, debriefing
- For each session we shall have:
- ET planning
- ET execution,
- Summary session and restrospective each day
- Discussion about ET reporting and Statistics (metrics)
8. Retrospective - workshop
Note: the syllabus outline may vary, and additions or subtractions of topics and subtopics may occur – all in favor of delivering a better course content, that is relevant, up-to-date, and adding value.