Here's a brief look at some of the testing types listed here
Acceptance Testing
- black-box type tests
- executed by customers / their representatives
- small set of tests generally aligned towards real-life scenarios / use-cases
- purpose primarily to verify if product meets acceptance criteria and not defect detection
- tests can verify functional / non-functional requirements
Buddy Testing
- a type of ad-hoc testing
- usually comprises two buddies working together to identify defects
- buddies with diverse backgrounds / perspectives enhance the degree of defects detected
- developer + tester is a good buddy combination
- generally performed during unit testing phase
Paired Testing
- involves pair of testers working on the same machine testing the product
- a type of ad-hoc testing
- helps in idea generation and exchange resulting in new perspectives during testing
Exploratory Testing
- a type of ad-hoc testing
- involves testing by exploring the product with set objectives and plan of action
- uses some common methods to perform exploration e.g. guessing, use case scenarios, meetings with project team, questionnaires, past release defects analysis, etc.
- can cover both functional areas as well as non-functional requirements around supported platforms and other environment variables, configuration attributes, etc.
- can also involve teams comprising members of diverse backgrounds to explore specific areas of the product
