Going by definitions it can be easily concluded that Exploratory and Automated Testing are two different streams of Testing, based on altogether different ideologies. But going by the vibes, I can figure out that two when done in conjunction, can bring a lot of value to the enterprises.
A few days ago QA Wizard, a business unit of Seapine Software launched Defect Scribe, a tool that helps quality assurance (QA) and software development teams improve their manual testing efficiency and create better bug reports. A subscription-based service, Defect Scribe is installed on the user’s desktop and records every user action and application screen to improve test session efficiency and create better bug reports. Available for web, Windows, or Java applications, Defect Scribe records activity during manual and exploratory testing.
What was a chit chat with Jim Holmes, Evangelist, Telerik Testing Tools ended up as an interesting conversation on few testing trends. Jim has over 25 years of experience in IT field in various capacities from PC technician, WAN manager, customer relations manager and developer to tester. He has an abysmal pool of information build up over the years, coming from his personal experiences and customer interactions, understanding their requirements, the issues they face with the automation tools and a lot more. The information collected from him is a true reflection of the current testing trends and can be of great help to the testing community.
Session-based test management (SBTM) is a technique for managing exploratory testing. SBTM helps bridle the randomness around Exploratory Testing to some extent without compromising on the essence of Exploratory Testing. SBTM overcomes the major issues involved with exploratory testing like the lack of methods that provide the visibility of the progress made with Exploratory Testing (ET) and test coverage achieved with ET.
Last Week we started the Exploratory Testing Journey on ToolsJournal, Let me take the discussion a step further by compiling the Types/Styles of Exploratory Testing for the benefit of the readers specially from the Testing Community.
Pair testing is a tool for exploratory testing in which two testers sit together to test, analyze and explore a system. It is an excellent and proven way to increase the chances of success with exploratory testing. Here at ReQtest we recently tried pair testing in one of the teams and thereafter decided to write down some of our experiences. Our team had a large test group which was constantly changing. The systems we tested were not particularly well-documented and we wanted to try new techniques to develop the work. We tried out our pair testing in two ways, planned and unplanned.
Exploratory Testing (ET) means to explore the Application under Test (AUT), learn about it, and while you are learning, design test cases and execute them to unearth the hidden software bugs. It is an informal method of black box testing. A brief knowledge of what the application does is enough to start with exploratory testing. But the key to a successful Exploratory Testing stint is the Tester and his skills of inventing test cases and finding defects. The proponents of ET consider it to be a test approach that can be applied to any test technique, at any stage in the development process.
Every tester would have at some point come across the well know debate on software test certification and its importance. I have been fortunate to attend one of the meetups organised by software testing club and meet some greats like Micheal Bolton, Rob Lambert and others. One of the topics that was discussed pretty aggressively was "Test Certification". Debate went in lines of, is Test certification required, would it help fresher's, would it help people who have been in testing for few years and so on. Made a humble attempt to highlight the discussion and some take away points that came across strongly from the community.