"Exploratory testing is a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the value of her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive ...
After a feature is delivered, we have recently started to perform exploratory testing on the feature before we execute manual functional tests. We find 95% of the defects during exploratory testing so ...
I wonder if anyone have experience of a tool for session-based testing? Nowadays we use SharePoint lists where we can write down our session plus other relevant info about the session (requirement, ...
While doing exploratory testing it would be nice to be able to record the screen (in a non-intrusive way), so if a defect is found the steps to reproduce it can be easily reviewed. Are there any good ...
I'm testing a system that involves XMLs from a JMS queue getting inserted into a database using a JMS trigger (webmethods). Firstly, I turn off the JMS trigger to let messages accumulate on the ...
I'm interested in hearing suggestions for ways of recording exploratory test session notes. We currently use a mixture of Session Tester and a wiki for recording test notes. I like many things about ...
There appear to be very few tools out there specifically aimed at managing charters for exploratory testing sessions. If you're using SBTM or TBTM, how do you manage your charters? Some of the ...
Session-based exploratory testing depends on creating good test charters at the right level of detail to guide the tester, without directing them. You need to make the goal of the session clear, ...
The concept of the Testing Playbook has been recently added to the list of possible tools in your Context-Driven toolset. The Playbook has been described as being similar to the list of plays that a ...
As I understand it, this sentence means that automated tests don't find new bugs in existing code (though they might catch a new bug in new code that breaks old code). Is this correct? Or is this ...