Monsterindia | Monsterindia Wiki | qualityassurancejobs.com
Suitable Quality is determined by product users, clients or customers, not by society in general. It is not related to cost and adjectives or descriptors such "High" and "Poor" are not applicable. For example, a low priced product may be viewed as having high quality because it is disposable where another may be viewed as having poor quality because it is disposable.
1 Testing methods
2 Testing levels
2.2 Objectives of testing
3 Non-functional testing
4 The testing process *Traditional CMMI or waterfall development model *Agile or Extreme development model *A sample testing cycle 5 Automated testing *Testing tools *Measurement in software testing
Black-box testing is a method of software testing that tests the functionality of an application as opposed to its internal structures or workings (see white-box testing). Specific knowledge of the application's code/internal structure and programming knowledge in general is not required. The tester is only aware of what the software is supposed to do, but not how i.e. when he enters a certain input, he gets a certain output; without being aware of how the output was produced in the first place. Test cases are built around specifications and requirements, i.e., what the application is supposed to do. It uses external descriptions of the software, including specifications, requirements, and designs to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid inputs and determines the correct output. There is no knowledge of the test object's internal structure.
This method of test can be applied to all levels of software testing: unit, integration, system and acceptance. It typically comprises most if not all testing at higher levels, but can also dominate unit testing as well.
Typical black-box test design techniques include: