We catch your bugs!)

Нагло вырублено топором из леса слов вИкепадии:

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.^[1] Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs (errors or other defects).

Software testing can be stated as the process of validating and verifying that a software program/application/product:

1. meets the requirements that guided its design and development;
2. works as expected; and
3. can be implemented with the same characteristics.

Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development methodology adopted.

Different software development models will focus the test effort at different points in the development process. Newer development models, such as Agile, often employ test driven development and place an increased portion of the testing in the hands of the developer, before it reaches a formal team of testers. In a more traditional model, most of the test execution occurs after the requirements have been defined and the coding process has been completed.

• 1 Overview
• 2 History
• 3 Software testing topics
  • 3.1 Scope
  • 3.2 Functional vs non-functional testing
  • 3.3 Defects and failures
  • 3.4 Finding faults early
  • 3.5 Compatibility
  • 3.6 Input combinations and preconditions
  • 3.7 Static vs. dynamic testing
  • 3.8 Software verification and validation
  • 3.9 The software testing team
  • 3.10 Software quality assurance (SQA)
• 4 Testing methods
  • 4.1 The box approach
    • 4.1.1 White-box testing
    • 4.1.2 Black-box testing
    • 4.1.3 Grey-box testing
    • 4.1.4 Visual testing
• 5 Testing levels
  • 5.1 Test target
    • 5.1.1 Unit testing
    • 5.1.2 Integration testing
    • 5.1.3 System testing
    • 5.1.4 System integration testing
  • 5.2 Objectives of testing
    • 5.2.1 Regression testing
    • 5.2.2 Acceptance testing
    • 5.2.3 Alpha testing
    • 5.2.4 Beta testing
• 6 Non-functional testing
  • 6.1 Software performance testing
  • 6.2 Usability testing
  • 6.3 Security testing
  • 6.4 Internationalization and localization
  • 6.5 Destructive testing
• 7 The testing process
  • 7.1 Traditional CMMI or waterfall development model
  • 7.2 Agile or Extreme development model
  • 7.3 A sample testing cycle
• 8 Automated testing
  • 8.1 Testing tools
  • 8.2 Measurement in software testing
• 9 Testing artifacts
• 10 Certifications
• 11 Controversy
• 12 See also
• 13 References
• 14 External links