Ajinkya SEN

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 9

•Introduction

Black box testing is a testing technique in which the


internal workings of the software are not known to the
tester. The tester only focuses on the input and output of
the software.
Black box testing is a powerful testing technique
because it exercises a system end-to-end. Just like
end-users “don’t care” how a system is coded or
architected, and expect to receive an appropriate
response to their requests, a tester can simulate
user activity and see if the system delivers on its
promises. Along the way, a black box test
evaluates all relevant subsystems, including UI/UX,
web server or application server, database,
dependencies, and integrated systems.

An example of a security technology that performs


black box testing is Dynamic Application Security
Testing (DAST), which tests products in staging or
production and provides feedback on compliance
and security issues.
•Diagram Of Black Box
•Black Box Testing Techniques

Equivalence Partitioning

Testers can divide possible inputs into groups or “partitions”, and test only
one example input from each group. For example, if a system requires a
user’s birth date and provides the same response for all users under the age
of 18, and a different response for users over 18, it is sufficient for testers to
check one birth date in the “under 18” group and one date in the “over 18”
group.

Boundary Value Analysis

Testers can identify that a system has a special response around a specific
boundary value. For example, a specific field may accept only values
between 0 and 99. Testers can focus on the boundary values (-1, 0, 99 and
100), to see if the system is accepting and rejecting inputs correctly.

Decision Table Testing

Many systems provide outputs based on a set of conditions. Testers can then
identify “rules” which are a combination of conditions, identify the outcome
of each rule, and design a test case for each rule
•Types Of Black Box Testing

Black box testing can be applied to three main types of tests: functional,
non-functional, and regression testing.

Functional Testing

Black box testing can test specific functions or features of the software under
test. For example, checking that it is possible to log in using correct user
credentials, and not possible to log in using wrong credentials.

Functional testing can focus on the most critical aspects of the software
(smoke testing/sanity testing), on integration between key components
(integration testing), or on the system as a whole (system testing).

Non-Functional Testing

Black box testing can check additional aspects of the software, beyond
features and functionality. A non-functional test does not check “if” the
software can perform a specific action but “how” it performs that action.

Black box tests can uncover if software is:

 Usable and easy to understand for its users


 Performant under expected or peak loads
 Compatible with relevant devices, screen sizes, browsers or operating
systems
 Exposed to security vulnerabilities or common security threats

Regression Testing

Black box testing can be used to check if a new version of the


software exhibits a regression, or degradation in capabilities, from
one version to the next. Regression testing can be applied to
functional aspects of the software (for example, a specific feature no
longer works as expected in the new version), or non-functional
aspects (for example, an operation that performed well is very slow
in the new version)
•Advantages of Black Box Testing

 The tester does not need to have more functional knowledge or


programming skills to implement the Black Box Testing.

 It is efficient for implementing the tests in the larger system.

 Tests are executed from the user’s or client’s point of view.

 Test cases are easily reproducible.

 It is used to find the ambiguity and contradictions in the functional


specifications.

•Disadvantages of Black Box Testing

 There is a possibility of repeating the same tests while implementing the


testing process.

 Without clear functional specifications, test cases are difficult to


implement.

 It is difficult to execute the test cases because of complex inputs at


different stages of testing.

 Sometimes, the reason for the test failure cannot be detected.

 Some programs in the application are not tested.

 It does not reveal the errors in the control structure.

 Working with a large sample space of inputs can be exhaustive and


consumes a lot of time.
•Tools Used for Black Box Testing:

1. Appium

2. Selenium

3. Microsoft Coded UI

4. Applitools

5. HP QTP.

•What can be identified by Black Box Testing

1. Discovers missing functions, incorrect function & interface errors

2. Discover the errors faced in accessing the database

3. Discovers the errors that occur while initiating & terminating any
functions.

4. Discovers the errors in performance or behaviour of software.

•Features of black box testing

1. Independent testing: Black box testing is performed by testers who


are not involved in the development of the application, which helps to
ensure that testing is unbiased and impartial.

2. Testing from a user’s perspective: Black box testing is conducted


from the perspective of an end user, which helps to ensure that the
application meets user requirements and is easy to use.

3. No knowledge of internal code: Testers performing black box


testing do not have access to the application’s internal code, which
allows them to focus on testing the application’s external behaviour
and functionality.

4. Requirements-based testing: Black box testing is typically based on


the application’s requirements, which helps to ensure that the
application meets the required specifications.
5. Different testing techniques: Black box testing can be performed
using various testing techniques, such as functional testing, usability
testing, acceptance testing, and regression testing.

6. Easy to automate: Black box testing is easy to automate using


various automation tools, which helps to reduce the overall testing
time and effort.

7. Scalability: Black box testing can be scaled up or down depending


on the size and complexity of the application being tested.

8. Limited knowledge of application: Testers performing black box


testing have limited knowledge of the application being tested, which
helps to ensure that testing is more representative of how the end
users will interact with the application.
•Conclusion:
In conclusion, Black Box Testing is a vital method in software quality assurance,
focusing on evaluating software functionality from an end-user’s perspective. Its
ability to assess whether software meets specified requirements and performs as
expected in real-world scenarios makes it a cornerstone of software testing.
While it offers advantages like accessibility to non-developers and early testing
opportunities, it also comes with limitations such as limited code visibility and
potential time consumption in manual testing. The integration of automation tools
like Testsigma can further enhance the efficiency and effectiveness of Black Box
Testing, ensuring the delivery of robust and user-friendly software products.
•Reference :

•https://www.javatpoint.com/black-box-testing
•https://www.geeksforgeeks.org/software-engineering-black-box-
testing/amp/
•https://chat.openai.com/
•https://gemini.google.com/

You might also like