What Are Software Testing-Testing Techniques?

[chudamani swamy]

1) White Box Testing:
i) Unit testing:
ii) Integration testing:
a) Top Down Process
b) Bottom Up Process
c) Hybrid or Sandwich process

2) Black Box testing:
i) System testing
a) GUI testing
b) Functional Testing
1) Sanity testing
2) Smoke testing
3) Internalization testing
4) Usability testing
5) Retesting
6) Regression testing
7) Ad-hoc Testing
8) Accessibility testing
9) Parallel testing
c) Non-Functional
1) Compatibility testing
2) Configuration testing
3) Intersystem Testing
4) Installation testing
5) Performance testing
i) Load testing
ii) Stress testing
iii) Volume testing
iv) Soak testing
6) Security testing
ii) Acceptance testing
1) Alpha Testing (α)
2) Beta Testing (β)


Thanks&Regards
Swamy

[tester70]

Hi,

Gray box is also a type of testing.
Gray box testing is a software testing technique that uses a combination of black box testing and white box testing. Gray box testing is not black box testing, because the tester does know some of the internal workings of the software under test. In gray box testing, the tester applies a limited number of test cases to the internal workings of the software under test. In the remaining part of the gray box testing, one takes a black box approach in applying inputs to the software under test and observing the outputs.

Gray box testing is a powerful idea. The concept is simple; if one knows something about how the product works on the inside, one can test it better, even from the outside.

[jenniferloopez]

Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing.

[emmily]

Software testing can be stated as the process of validating and verifying that a software (program/application/product) meets the business and technical requirements that guided its design and development, works as expected and can be implemented with the same characteristics. Test techniques include the process of executing a program or application with the intent of finding software bugs.

Software testing methods are traditionally divided into white- and black-box testing
White Box Testing:
It’s usually called code based testing .In White box testing, when the test tester has access to the internal data structures and algorithms including the code that implement these
Types of White Box testing
API testing (application programming interface) - testing of the application using public and private APIs
Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once)
Fault injection methods - improving the coverage of a test by introducing faults to test code paths
Mutation testing methods-is a method of software testing, which involves modifying programs' source code or byte code in small ways
Static testing - generally not detailed testing, but checks mainly for the sanity of the code, algorithm, or document. It is primarily syntax checking of the code and/or manually reviewing the code or document to find errors

Black Box testing:
Black box testing is not a code based testing i.e Black box testing treats the software as a "black box"—without any knowledge of internal implementation
Black box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing.

Grey box Testing
It involves having knowledge of internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level

Testing Levels
Unit testing: These type of tests are usually written by developers as they work on code (white-box style), to ensure that the specific function is working as expected. Unit testing is also called component testing.
Integration Testing: In Software Testing individual software modules are combined and tested as a group. It occurs before System testing
System Testing :
System testing is a testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.
System Integration Testing
SIT verifies that a system is integrated to any external or third party systems defined in the system requirements
Regression testing
Regression Testing focuses on finding defects after a major code change has occurred. Regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code. Common methods of regression testing include re-running previously run tests and checking whether previously fixed faults have re-emerged
Acceptance Testing
Acceptance testing performed by the customer, often in their lab environment on their own hardware, is known as user acceptance testing (UAT). Acceptance testing may be performed as part of the hand-off process between any two phases of development
Alpha Testing
Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing
Beta Testing
Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users