30 Good Practices to improve Exploratory Testing
Use a bug tracking system
Use boundary testing of values
Consider using testing personas
Use happy, sad and optional paths
Become skilled at reading server logs
Learn about usability and accessibility
Learn to use emulators and simulators
Learn more about the customers needs
Be present in business process ...
You may find yourself tempted to write out a bunch of charters early on to show management types so that it doesn't look like you're sitting on your hands. Resist this urge if you find it upon you.
There's no real need to overcomplicate charters. If start a session and you realize the scope is overambitious, modify the scope and note down whatever new ...
I am in for this idea. This can be a part of regular testing. But whether it will have a positive impact on productivity; is largely dependent on the way you implement this idea.
Definitely, there are positive aspects of gamification which you have talked about above.
I just want to focus on implementation part of it. Because we have to take care of the ...
I think this is commonly referred to as
Persona Based Testing
This exists for both manual role-playing (as you refer to) and is also a useful tool for writing automated tests to help get the test writer in the right frame of mind. It helps to create software when, instead of saying "user updated profile", we say "Mary, a programmer aged 28, updates her ...
I like to keep things simple.
I work with a small team of testers and programmers. We like to keep things lightweight.
For managing charters and information flow, I use a spreadsheet and a whiteboard.
I categorize charters by product area. I haven't found getting more detailed than that to be useful to me (or others). I name charter files by their product ...
Personally, I really like exploratory testing based on the following three ingredients:
The amount of time a tester gets
Makes planning possible
Team decides per sprint/week/day etc.
Allows lean manual testing for others (e.g. developers or domain experts), too
Testers are extremely focused (higher chance of finding bugs)
Example: usually between ...
Yes, it would. I like teams that execute exploratory testing in pairs, I think it is easier to write charters, create mind-maps and decide on heuristics together than alone. It will keep you sharper, you will go faster in executing and analysing the results.
I would like to find answers on the following questions during an interview:
Will your team like ...
It really comes down to who is consuming the information contained in your notes and what that information will be used for. If your testing found a bug, for example, you would likely want to write up steps to reproduce, information about your environment, and other information that would help find and fix the bug. If you are reporting on what you tested to ...
Use whatever you are comfortable with. I'd suggest starting with something basic for recording notes like Notepad++. The important thing is to be able to keep detailed notes about your session, to setup a session charter, etc. Once you've got some practice with it, you can see what works and what doesn't.
I've used Rapid Reporter and Session Tester as ...
What are the general recommended strategies and techniques for Exploratory Testing?
Recommended Strategies with ET:
Use Exploratory Charters to guide your work. Even if you don't timebox your exploration, charters will give you just enough specifics to be useful.
It will take time to develop your ability to write good charters. Start with crappy ones and ...
Great idea. Some things that might help:
Instead of pair testing, just explain the basic context and let the candidate figure it out. A big advantage here is you will get a feel of:
How many questions does this person ask?
What type of questions? Relevant or not?
How independent and confident is this tester?
Quantifying the result isn't hard science, but:
1) As a free solution: You can use FFmpeg for full screen recording. For windows it requires ScreenCapturer (also free and opensource). For linux it can record the screen natively.
2) Camstudio is also a good solution. The output files may be huge, but you always can encode it with FFmpeg ...
I recently discovered PSR.exe, which is part of Windows 7 (just type in psr in the search field). It allows the user to record everything he or she does (like Snagit), but also makes it easy to add comments and to highlight certain regions of the screen. Once you finish recording, everything will be saved in a zip file as a so called ".mht" file. When you ...
Not saying that it's cheap, but, tools like OneNote tend to fill this void very well. We use a notebook for each application. For projects, we use Tabs/Sections for Modules/areas, and for operational type changes, we use a new section for each Release. Each session takes up 1 page. These get stored on either a sharepoint or in a shared folder that we all ...
IVR (Interactive Voice Response) applications allows
customers to call and navigate through various instructions
to Login, check on account, pay bills, order service, Customer call, Raise complaints etc.
IVR applications interacts with the caller to determine (via collection
of customer entered dtmf digits) who is calling and the reason
for the call.
Gather an audience from a wide background and expertise
Different people with different background offer different ways of thinking. It is surprising how a person sitting next to you offers a new way of thinking.
Brain-storming session with this gathered crowd
When people are working together, they stimulate each other into getting better ideas faster.
Exploratory testing is an experience based testing technique, so it mostly depends on whoever executes the test.
Having said that, James Bach outlines a few good points that we can potentially benefit from:
An exploratory test session often begins with a charter, which states the mission and perhaps some of the tactics to be used. From my personal ...
Should we take notes in a simple text file or should we take it in a
fancy Excel sheet?
I am used to carrying a notebook with me, It's my childhood practice. I believe as a human being I can't remember every point, I discussed with the teammates. I have all the things with me like a personal digital assistant, laptop, desktop, Personal Server,
Try Wink, it's very light because it captures a screenshot on each click or keystroke.
You can export to PDF for printing or make it a Flash video.
It works on all Windows versions, recorded projects tend to grow huge.
Recently I learned about Screenpresso
It's not as good as SnagIt but much better than Jing. In free version you can record videos only up to 20 secs. This limitation is gone in paid version.
I once tested a Windows client UI by randomly banging on the keyboard while my coworker randomly moved and clicked the mouse. I found bugs that way, and I could reproduce them, but (at least initially) I couldn't tell you the exact set of keystrokes and mouse clicks that triggered the problem. That is monkey testing.
Exploratory testing is testing ...
Black box approach in and of itself is specifically designed to come from the user perspective backwards. The difference between black box and white box testing is knowledge of the underlying code and components.
Therefore when you are prepping for black box testing you should be coming from the user perspective who utilize the application. This is any ...
"free-style testing that largely depends on the creativity of the testers and how well they know the product or feature under test."
I would switch 'creativity' (which I also see at Wikipedia) with 'experience and training'. How well they know the product is definitely helpful.
I break down exploratory testing like this:
The different paths:
Happy - ...
Rapid Testing is a strategy where you test a product quickly to meet extremely short product delivery schedules, by eliminating all unnecessary work and only testing critical areas of the product. Instead of trying to eliminate all bugs, the rapid testing ethos is to stop 'damaging defects' from being released.
Rapid Testing is therefore the terminology ...
set up regular workshops demonstrating how were some of the bugs discovered during previous exploratory testing sessions, what led to them being discovered
Yeah, definitely a good idea. I happen to have been thinking of something similar. Please read the bullet point below:
It will be especially useful to set up a workshop that teaches/demonstrates how to ...
As they say be careful what you measure - you will get it.
There are many questions in workplace forums about metrics and motivation proposals which went wrong, debating how different metrics can be misused and gamed.
You use "gamification" as having more fun with the task. "Gaming" is also used in opposite sense: using the metrics against the original ...
Sounds to me like (smart) monkey testing. Definition from the ISTQB glossary (v3.1):
Testing by means of a random selection from a large range of inputs and by randomly pushing buttons, ignorant of how the product is being used.
Quite often fuzz/monkey/random/… testing refer to the same thing, but I like this distinction:
[…] Fuzz testing is more ...
Pick some samples for training but don't add more process for all
I recommend not documenting the details of all exploratory testing sessions for future re-use because trying to script, what is essentially a voyage of exploration, is not in the nature of exploratory testing. The main exception to that is to get examples for training and education.
Do the following:
Get familiar with the application by using it.
Try to get an overview and notice the different areas / components you recognize.
Use the application from a user point of view.
A lot of questions will come up in your mind. Write them down and clarify them later with business analysts and developers.
Aks the following questions:
What type ...