So it's clear to everyone that exploratory testing is more than just "testing". They should be planned and, at some level, documented.
Attached is a form, if you wish, to be filled in before, during and after the tests.
Exploratory Tests Form
Date: Feature to be tested:
The scope of testing:
Examples: UI
Functionality Validation Usability Validation etc.
Time Frame (recommended: up to 2 hours):
The technique to be used (mark the relevant one/s or add new ones):
Examples:
Risk management (tests what is more risky) Use case / User stories “Drifting” vs. the spec Scenario based (Soap Opera) These are tests where one assumes that the user has everything going on. Invariance testing changes things that shouldn't affect the product and then makes sure that they indeed don't Gorilla testing is a quick attempt to determine the level of risk of a subsystem It can also be used to find major bugs early in the cycle run tests that emulate user tasks. Some testers should explicitly be given a task focus, not a feature focus. Their job is to do whatever users do in order to accomplish whatever it is that users try to accomplish. Run the tests based on the Manual of the product Bug based testing. Run tests based on bug types found in the feature/application going over the menus
Test mission:
Examples:
Does something work as requested in the requirement? How does something work under this and that conditions? Is documentation of something aligned with the actual something behavior? What is the performance of something? Does something behaves user-friendly way? Does something affected current and existing behavior of something
Running log (please fill while you go):
Testing the: Conjecture(or: what could go wrong and how to find it): Flows that I run in high level: a. b. c.... Conjecture refuted / corroborated: New conjecture etc.... I saw something strange… Bugs found in high level (will be reported later):
My impressions:
Feelings I had about the product, about specific features, flows etc. (Bad and good ). Thoughts about the testing: is the product good? Reliable? Does it serve its purpose? Will users like it?
Thoughts about the test itself: (what was good, what we can improve, what was missing). what should be tested next based on my experience.
Jun 28, 2015
Attached is a form, if you wish, to be filled in before, during and after the tests.
Exploratory Tests Form
Date: Feature to be tested:
The scope of testing:
Examples: UI
Functionality Validation Usability Validation etc.
Time Frame (recommended: up to 2 hours):
The technique to be used (mark the relevant one/s or add new ones):
Examples:
Risk management (tests what is more risky) Use case / User stories “Drifting” vs. the spec Scenario based (Soap Opera) These are tests where one assumes that the user has everything going on. Invariance testing changes things that shouldn't affect the product and then makes sure that they indeed don't Gorilla testing is a quick attempt to determine the level of risk of a subsystem It can also be used to find major bugs early in the cycle run tests that emulate user tasks. Some testers should explicitly be given a task focus, not a feature focus. Their job is to do whatever users do in order to accomplish whatever it is that users try to accomplish. Run the tests based on the Manual of the product Bug based testing. Run tests based on bug types found in the feature/application going over the menus
Test mission:
Examples:
Does something work as requested in the requirement? How does something work under this and that conditions? Is documentation of something aligned with the actual something behavior? What is the performance of something? Does something behaves user-friendly way? Does something affected current and existing behavior of something
Running log (please fill while you go):
Testing the: Conjecture(or: what could go wrong and how to find it): Flows that I run in high level: a. b. c.... Conjecture refuted / corroborated: New conjecture etc.... I saw something strange… Bugs found in high level (will be reported later):
My impressions:
Feelings I had about the product, about specific features, flows etc. (Bad and good ). Thoughts about the testing: is the product good? Reliable? Does it serve its purpose? Will users like it?
Thoughts about the test itself: (what was good, what we can improve, what was missing). what should be tested next based on my experience.
Jun 28, 2015
