Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Efficient and Effective Testing
Transcript of Efficient and Effective Testing
Efficient, but non-effective (semi-automated test plans) Why not effective? Because we do not test everything (whether manual or semi-automated test plan)
Because not every change is bad - but we might not know what to expect Why efficient (sometimes)? Because we check all data in all affected tables - and it's done very fast How do we get to
"Efficient AND Effective"? What have we not mentioned? GUI testing GUI testing is too cumbersome for automated testing; must be done by humans Know what we need to test
Only test it once
Have semi-automated check points for everything we test How do we find out what we need to test? Analyze all the programs (flow chart the process paths) Gap Analysis How to ensure we test all process paths, and only test them once? In a G.A., you overlay you scenarios over the flow chart thereby identifying what is covered and what is not.