This session is part of Exploratory Testing Week. Go Pro or buy a ticket to unlock this session and many more
Discussions: Reporting your Exploratory Testing
About This Discussions
In this session, Suman Bala will be joined by three guests, Niranjani Manoharan, Monica Arzani & Laveena Ramchandani where they will share their different experiences on how they report their Exploratory Testing.
This is your opportunity to ask this panel of talented and experienced individuals your questions on this theme, such as:
- How do you determine missing values? What are the different ways to do that?
- How to find invalid entries?
- What kind of information are the most important when reporting exploratory testing?
- How do you adapt your reporting to different stakeholders?
- How do you get the rest of the team to report on exploratory testing?
- Can we pair explore?
What our panellists have to say about themselves:
With my increasing curiosity to learn, I wanted to use my exploratory testing skills to understand data analysis. Data analysis is defined as a process of cleaning, transforming and modelling data to discover meaningful information for business decision making. For the purpose of this study, I used the COVID-19 vaccination progress dataset.
To do data analysis, domain knowledge would be super helpful - for example, if you are not a wine connoisseur, then how would you know about the good or bad categories of wine? But in this case, I was using it as it was relevant to the pandemic situation we all are in!
While cleaning data, it is critical to know when to drop columns and rows. Determining missing values and replacing them with mean imputation is a common practice.
Exploratory testing is quite an interesting area for me. It is a type of testing where we are not confirming the happy paths but also unveiling any unknowns, risks or even assumptions. The assumptions come into our minds when we do not know 100% how a piece of functionality works, which might lead to assumptions. By assuming we have added a major risk to the product! So, by exploring the product we can confirm what the product should and should not do, which in turn helps make better team decisions or even enhance existing testing patterns and advocate for repair.
I have been in testing for 5 years and a half. I started just after graduating and system testing has been my first job. I work in a traditional industry: we make anchors, drills and tools for construction companies. Testing in my business unit is very influenced by hardware testing protocols. We believed we could model every user and system behavior, by writing tons of specifications and testing according to them. As a newbie, I trusted the system and process in place, until I started realizing that we built ourselves a golden cage ad we would just repeat and optimize over and over what was already known.
Test manager and test engineer, with a passion for learning and improving . My preferred approach is exploratory testing, where I use what I learn about the system to continuously inform the next experiments, using a variety of tools and techniques as needed. I started as an applied mathematics graduate, developing and verifying algorithms and simulations for complex mechatronics system, to become a cross functional engineer in testing, that can keep in mind the whole system, our customers and the project context, while going deep into the technology.
Test Manager - Data science & Digital @ EasyJet
I am a vibrant, motivated and committed individual. I have been in the testing industry now for over 7 years. It's been a great experience learning and sharing skills. I aim to broaden my knowledge further more. Data science is what I am currently focusing on, and it's very exciting to see all the new things one could learn out of it and merge it with testing. Definitely quite interesting!
Suman Bala is a Test Architect with a passion for improvement in quality processes and is a strong believer in Test Automation. She feels proud of how people’s perspective has changed regarding testing throughout her career. She is striving to instil the idea that quality is everyone’s responsibility as opposed to merely laying it at the feet of QA. She is a co-organiser for the Ministry of Testing Bucks meet-up. She is a mentor and coach at work and within the wider testing community. She is co-designing and delivering the “Software Testing Bootcamp” sponsored by the West Yorkshire Combined Authority.