Exploratory testing

 BUG hall of Fame !!! 

Got to create my own 

Checked and explored 

TDD 

All nets have holes 

Your money is no good hear - payment flow SAAS

Go ahead and grant those privileges 

Role based - all roles and no roles 

Can edit the role they wanted - SU 

Is not done only manually - similar to telephone support system 

Only be found via exploratory - key QA attribute 

Is methodical - sessions are a day to half a day 

What is the charter to execute and observe 

What can I vary 

Mini experiments 

Observe 

Debrief - capture the lessons learned 

Charter - can come from anywhere - just before you start to Team effort 

Target 

Resources 

Information 

Using suppot 

What can I vary 

Change directly or cause to be changed 

Does not tie back to a written requirement - 

Mar rover bug

Not size of date but rather the number of files 

Tell rover to delete 

Variable are fractal ….wow, I mean WOW!

What or where is the most risk 

Play with boundaries and constraints 

Times too late or to early  

Strings tool long too short 

Experiment w/ sequence 

Any time you can say "while", you have found a state 

The real world is WAY more complicated than the real world 

While state of updating - 

Observe 

Use all your resources 

If something goes wrong how would I know 

File bugs have conversations - value in the information is taking actions on that information 

AS a pair or pare :D 

Exploring is learning 

When and who? 

Everyone and always 

This is a tester or QA mindset 

Giving us the language 

Proves that a QA's job is NEVER done 

Explore IT from pragmatic bookshelf