Degree of Exploratory Testing: Dear Master! I want to earn new belt

Cem Kaner defines exploratory testing as “a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project.”

It’s undeniable to say that exploratory testing becomes more popular and more effective in an agile world. Some organizations have established their strategy to “evolve” their testers to be more “agile” by adopting & training on exploratory testing. When conducting the training at MeU Solutions and at seminars where I am invited as a guest speaker to introduce a “new approach” called “Context-Driven Testing”, usually I am asked the question “How to become an exploratory tester?”. In fact, testing is exploring, so tester is an explorer in testing. The correct question should be “How to be a great exploratory tester?”

Continue reading

Effective Exploratory Testing (Part 2): More Effective With Pair Exploratory Testing

Pair Testing is an approach of software testing in which two persons sit together at the same time and place to carry out and design tests. Pair testing is a collaborative effort, versus a single-person effort. Usually, one person controls the mouse and keyboard to perform directly the tests, while the other person asks questions, takes notes, and brings more scenarios which support the testing better. When talking about pair testing, we usually imply that one tester and one developer to work together.

Session-based testing is a method to measure and manage & implement exploratory testing better. In session-based testing, the testing is limited in given timeboxes, typically 60’-120’ minutes long. Each test session has its specific goals and contains a specific portion of what needs to be tested. A session can be a UAT Test for a story, a screen, a bug, a business transaction, or a technology facing for a piece of feature.

Continue reading

Using One2Explore to perform an exploratory testing session for StickyNotes

With One2Explore capabilities, the exploratory testing is more effective. One2Explore helps you structure, plan, track, report and debrief the exploratory to ensure the goal covered. One2Explore is integrated with One2Test (Testing Dashboard) and JIRA to gain more efficiency. Watch this video to see how our tester performs a testing session with this tool.

Continue reading

Context-Based Management – Metrics and The Dangers

“You Cannot Measure It, You Cannot Manage It” – It’s a favorite quote of many managers. At my side, I love to measure everything in my project. But how to translate the message from the result of this measurement into quality factors totally depends on the context.

From Cambridge Dictionary: “Metrics are a set of numbers that give information about a particular process or activity”. For examples: In Operation, we use MTBF – Mean Time Between Failures to measure elapse time between failures which occurs in a system or a service. In Conventional Testing, someone use “Test Case Productivity” which gives the test case writing productivity based on which one can have a conclusive remark; “Defect Acceptance” to determine the number of valid defects that testing team has identified during execution. In Agile Testing, “Examined Coverage” is a metric used to identify how much the software explored in scope or “Effort Density” identifies how much the effort runs into the software.

Continue reading