Lecture 6 - Classifying the Most Common Types of Testing -> Quick Intro -> By Knowledge Of The Internals Of The Software -> By The Object Of Testing -> By Time Of Test Execution -> By Positivism Of Test Scenarios -> By Degree Of Isolation Of Tested Components -> By Degree Of Automation -> By Preparedness -> Lecture Recap– Formal/documented testing
– Ad hoc testing
Formal/documented testing is a planned activity that requires the usage of test documentation – e.g., test cases.
Ad hoc testing is done without any preparation. Ad hoc testing relies on knowledge of the software and/or common sense and/or intuition. Doing ad hoc testing, the tester just follows his heart trying to find bugs.
Ad hoc testing is usually used:
– As a smoke test
– As a measure for extra peace of mind on top of formal/documented testing
– As exploratory testing when a new tester comes to a company where code is being written and should be tested ASAP
– When everybody in the company does testing before some big release
– In other cases where there are no test cases
Ad hoc testing often produces amazing results. Sometimes you just test software without any plan and come up with unusual scenarios that help catch nasty bugs. Next ->
Lecture 6 - Classifying the Most Common Types of Testing -> Quick Intro -> By Knowledge Of The Internals Of The Software -> By The Object Of Testing -> By Time Of Test Execution -> By Positivism Of Test Scenarios -> By Degree Of Isolation Of Tested Components -> By Degree Of Automation -> By Preparedness -> Lecture Recap
