Error Guessing

Question 1

Testing by intuition and experience

Answer 1

Much ad hoc testing based on intuition and guesswork
Some people have knack for finding bugs
Good test cases derived this way
Error guessed test should be documented as part of test plan

Question 2

Intro to exploratory testing

Answer 2

Documents form basis for test design (e.g. requirements specifications)are of very low quality or don’t exist
Technique may also be applicable when there is a severe time restriction
Approach based on intuition and experience of the tester
Possible elements of test object explored leading to decision on what parts to test
Execute test cases see if something unexpected occurs and run later test to pursue leads
Gradually knowledge about test object collected

Question 3

Is it credible

Answer 3

Bad reputation in some circles, sloppy, unprofessional, ineffective, unsystematic

Question 4

Exploratory testing process

Answer 4

Briefing , one page charter to identify hotspots
Get familiar with product and target hotspots
When you find a bug explore around it, look for patterns
Document test that caused failure
Log an incident
Move to next interesting area

Question 5

When to use exploratory testing

Answer 5

Normal testing suspended or you believe more focused tests in an area productive

Question 6

Continuous integration

Answer 6

Continually adding small code additions to main code branch
Regression testing to see pre existing software not affected by new code