Incorporate Exploratory Testing into your Test Strategy and find better bugs faster!
This two-day course is designed to give test engineers a global understanding of exploratory testing. From why we do it and its uses to how we do it and the value of measurement, Exploratory Testing will be examined and practiced to empower test engineers in using this method, finding better bugs earlier, focusing on customer satisfaction and making exploratory testing more manageable and easier to use as an necessary and important test method.
You Will Learn:
- How to test earlier and find better bugs!
- What is exploratory testing and why is there so much argument about its value?
- The psychology of good testers and cultural issues with exploratory testing
- When and how it can best be used in your test strategy
- Incorporating effective exploratory testing into your test strategy
- Management and measurement issues about exploratory testing
- Problems and misconceptions
- Further study
Part 1 Exploratory Testing: What is it?
- Why do it?
- What is it used for? Goals of exploratory testing?
- What are the common practices?
- Focus on the User
- Exploratory testing in agile development
Part 2 The Exploratory Testing Approach
- Project politics and “ad hoc” testing
- Testing psychology for exploratory testing
- Team culture and exploratory testing
- Risks of exploratory testing
- Problems and misconceptions
Part 3 How to do Exploratory Testing
- Black box, white box and gray box testing
- Discussion and exercises on varieties of exploratory testing including:
- User Scenario Testing
- How to Break Software (by James Whittaker)
- Error guessing
- Heuristics test oracles
- Focus on test data
- Common types of issues found in exploratory testing
Part 4 Management and measurement issues about exploratory testing
- Planning and communicating on exploratory testing
- Tips for managing and measuring exploratory testing
- Communicating coverage in exploratory testing
- When is testing done?
- Fostering a management and development team culture to support exploratory testing
A few months ago, Dr. Rebecca Fiedler and I published BBST—Test Design. This third course completes the Black Box Software Testing (BBST) set. The other two courses are BB ST Foundations and BBST Bug Advocacy. This article offers some information about the series, the design of the series (and the underlying instructional theory) and why you might be ...
Exploring key competences that endow a good games tester In this article, I will explore what I feel are the most important skills and attributes of a good game tester, and what type of mindset is needed for games testing. I believe a good game tester should have. This is based on my experience and ...
LogiGear Magazine – February 2011 – The Exploratory Testing Issue
Most software engineers intuitively perform BVA to some degree. By applying these guidelines, boundary testing will be more complete, thereby having a higher likelihood for error detection. Software is tested from two different perspectives: 1. Internal program logic is exercised using “white box” test case design techniques. 2. Software requirements are exercised using “black box” test case ...
A test plan should always include exploratory tests as part of the approach. Without them, the number of defects that find their way into production will always be higher. Exploratory testing is a key testing technique that is often left out of formal test plan phases such as system testing, system integration, and regression. Instead, ...
Lab team brainstorming session Whether you work in engineering/product, operations, or even marketing, keeping your team trained and engaged with their work is a challenge that is universal for all managers. This is hard enough when your team is in-house, but what are you to do, when you have multiple teams to manage across different ...
According to Associate Press (February 9, 2010, Yuri Kageyama, AP Business Writer), “Toyota is recalling 437,000 Prius and other hybrid vehicles worldwide to fix brake problem.” Toyota is the world’s largest automaker with impeccable quality reputation up to now.
Gondola by TestArchitect is a low-code Test Automation solution for End-to-End Testing across Web, API, and Mobile Applications. Gondola builds upon the TestArchitect family’s already-powerful testing capabilities in many ways, including faster mobile and web testing as well as heightened support for mobile application testing. LogiGear Product Manager Thuc Nguyen delves into why LogiGear created ...
LogiGear Magazine September 2012 – Integrated Test Platforms
If you want to enjoy your job and not worry about lack of resources, or have old, outdated strategies, with failing or meaningless test automation – get help! We all know about globalization. Markets are global, products are global, mobile is global and software development is a global. As a result, the workforce is ...