What are the types of Black Box Testing ?

[Vinni.TestLead]

Click Here To Register & Submit Your Resume !

Types of Black Box Testing :-
More Testing JOBS & FAQ @ http://www.TestingKen.com
Functional Testing black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)

System Testing testing is based on overall requirements specifications; covers all combined parts of a system.

Integration Testing testing combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially mainly to client/server and distributed systems.

Incremental Integration Testing continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.

End-to-end Testing similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Sanity Testing typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

Regression Testing re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.

Load Testing testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.
More Testing JOBS & FAQ @ http://www.TestingKen.com
Stress Testing term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.

Performance Testing term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.

Usability Testing testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.

Install/Uninstall Testing testing of full, partial, or upgrade install/uninstall processes

Recovery Testing testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Security Testing testing how well the system protects against unauthorized internal or external access, wilful damage, etc; may require sophisticated testing techniques.

Computability Testing testing how well software performs in a particular hardware/software/operating system/network/etc. environment

Acceptance Testing determining if software is satisfactory to a customer.

Comparison Testing comparing software weaknesses and strengths to competing products
More Testing JOBS & FAQ @ http://www.TestingKen.com
Alpha Testing testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

Beta Testing testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.

[vineethkc]

Originally Posted by Vinni.TestLead

Types of Black Box Testing :-
More Testing JOBS & FAQ @ http://www.TestingKen.com
Functional Testing black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)

System Testing testing is based on overall requirements specifications; covers all combined parts of a system.

Integration Testing testing combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially mainly to client/server and distributed systems.

Incremental Integration Testing continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.

End-to-end Testing similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Sanity Testing typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

Regression Testing re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.

Load Testing testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.
More Testing JOBS & FAQ @ http://www.TestingKen.com
Stress Testing term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.

Performance Testing term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.

Usability Testing testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.

Install/Uninstall Testing testing of full, partial, or upgrade install/uninstall processes

Recovery Testing testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Security Testing testing how well the system protects against unauthorized internal or external access, wilful damage, etc; may require sophisticated testing techniques.

Computability Testing testing how well software performs in a particular hardware/software/operating system/network/etc. environment

Acceptance Testing determining if software is satisfactory to a customer.

Comparison Testing comparing software weaknesses and strengths to competing products
More Testing JOBS & FAQ @ http://www.TestingKen.com
Alpha Testing testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

Beta Testing testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.

Good explanation...

Thanks much...

Hope it should be "Compatibility" rather than "Computability Testing"

Testing software under different hardware & software environments. Like different OS, different browsers etc...

[tossy]

Useful information for testers!!!!!!!!!1

[vilasitar]

Thank you for the post.!!

[rajeshchoudary]

http://testing4easy.blogspot.com/

[thebobblogs]

It can be grouped by testing technique. Here is the list on my hand.

- Equivalence Partitioning
- Boundary Value Analysis
- Pairwise Testing (All-pairs testing)
- Decision Table
- Error Guessing

[mfsi_dillip]

Hi ,

As far my knowledge following are the types of black-box testing.

1-Equivalent partitioning(EP)
2-Boundary value analysis(BVA)
3-State transition diagram
4-Decision table
5-Syntax testing
6-Use case diagram

Thanks,
Dillip

[monalisayankar]

The answer by dilip is right.

[srinivasanep]

Both answers are right. It depends upon the interviewer