Comsats University Islamabad

Attock Campus

Software Project Management

ASSIGNMENT#2
SUBMITTED BY:
Basla Azhar
FA18-BSE-057
SUBMITTED TO:
SIR FAHAD
Contents
Integration testing: ....................................................................................................................................... 3
Technique of integration testing: ............................................................................................................. 3
Types: ........................................................................................................................................................ 3
Black Box Testing: ......................................................................................................................................... 4
Example:.................................................................................................................................................... 4
White Box Testing: ........................................................................................................................................ 4
Example:.................................................................................................................................................... 4
Load Testing: ................................................................................................................................................. 5
For example: ............................................................................................................................................. 5
Stress Testing: ............................................................................................................................................... 5
For example: ............................................................................................................................................. 5
Alpha Testing: ............................................................................................................................................... 5
Beta Testing: ................................................................................................................................................. 5
Acceptance testing:....................................................................................................................................... 6

Page 2|6
Integration testing:
Integration testing is the second level of software testing that runs after unit testing. Test the software
modules or individual components in the test suite. The focus of the integration testing level is to detect
defects in the interaction between components or integrated modules. Unit testing uses unit tests that
are combined and tested in integration testing. This software is developed by many programmers, or is a
software module developed by many programmers. The purpose of integration testing is to test the
accuracy of the connections between all modules. After all components or modules work independently,
you need to monitor the data flow between clients. This is called integration testing.

A B C
Unit testing module module module

B
module

A C
Integration testing module module

Integration testing tests interfaces between components, interactions with different parts of a system,
such as the operating system, file system, hardware, or interfaces between systems. There may be more
than one level of integration testing and it may be carried out on test objects of varying size. For example:

 Component integration testing tests the interactions between software components and is done
after component testing;
 System integration testing tests the interactions between different systems and may be done
after system testing. In this case, the developing organization may control only one side of the
interface, so changes may be destabilizing. Business processes implemented as workflows may
involve a series of systems. Cross-platform issues may be significant.

Testing of specific non-functional characteristics (e.g. performance) may be included in integration

testing.

Technique of integration testing:

1. Black Box Testing
2. White Box Testing

Types:
1. Incremental integration testing

Page 3|6
 2. Non-incremental integration testing

Black Box Testing:

Black box testing is a testing method used to test the AUT (Application under Test) function according to
the specification/SRS without knowing the technology used to implement the application under test.

In black box testing, the main test focuses on possible inputs and expected outputs. Testers need to be
able to carefully select the correct test data. Simply put, the tester can only see the behavior of the AUT.
The tester does not need to know how to perform this procedure.

Black Box
Input Output

Example:
A simple example of black-box testing is a TV (Television). As a user, we watch the TV but we don’t need
the knowledge of how the TV is built and how it works, etc.

White Box Testing:

White box testing is a testing method used to test the running part of the application under test. To run
this test, the tester/developer may need to understand the internal structure of the application and how
it behaves.

Test Case Input Test Case Output

White Box

Example:
A Car mechanic should know the internal structure of the car engine to repair it.

Successful software delivery requires white box testing and black box testing, neither of which can be
100% tested. The main responsibility of the laboratory is to determine the types and methods of testing
related to a particular application. This will detect the biggest flaws and improve the performance of your

Page 4|6
application. Testers should be able to limit the number of tests that can be run in black box or white box
testing to show that the application is working as expected.

Load Testing:
Load testing is the most important part of performance testing. It is used to test the performance of
applications whose load is lower than required. This is called a Load test. The load is the quantity. In other
words, it only focuses on the number of users. Load tests can help testers identify obstacles. You can also
determine the reason for the restriction before deploying it to a production server. This type of test can
reproduce the load of any application or program.

For example:
If we have load of 100 users using the application at a 0.5\sec of goal time. And, the desired load is 100
user. This scenario got passed because the desired load is equal to the load

Stress Testing:
A stress test is a test that checks the applicant's behavior under unnecessarily high load. This is a negative
test and should only be used when the functionality of the application is stable. If the number of users
suddenly increases before the system fails or crashes, stress testing can help testers check the capacity of
the system. It is used to calculate the durability and stability of the application.

For example:
If we have actual load of 100 users using the application at a 0.5\sec of goal time. And, the desired load is
100 user. But in some cases 500 user increase this scenario got failed because the desired load is less than
the actual load

Alpha Testing:
Alpha testing is one of the commonly used software testing techniques in software development. It is
used to identify all software problems and errors before release. Black box and white box technologies
are used for alpha testing. Testing is carried out in a laboratory environment or in a software company,
and developers will be aware of software problems. Alpha testing is not open to the market or the public.
Alpha testing is a very important step after software development, because we cannot guarantee that the
software will run correctly, that the software will be error-free, and that the software will accept input
and provide expected output. Alpha testing can also eliminate software errors.

Beta Testing:
Beta testing is the second stage of software testing. The software is tested on site. After the software is
developed, software users will be able to use the software and easily perform important software tasks
without errors or malfunctions. Users comment on important software used for beta testing. After alpha
testing the software, you need to run a beta test of the software. In Beta testing, users ensure that the
software is fully functional, will not crash, and that the software is of high quality and can compete with
competitors.

Page 5|6
Acceptance testing:
Acceptance testing is a formal test based on user requirements and functional processing. Determine
whether the software meets your specific needs and requirements. This is done as a form of black box
testing, which includes the number of users required to accept the test system. This is the fourth and final
level of software testing.

User acceptance testing (UAT) is a test that is completed before the user accepts the final product. UAT
usually runs real-time scenarios for customers (domain experts) to complete based on satisfaction and
check whether they are working properly in the relevant business scenarios.

In this regard, we will only focus on the functions and scenarios that you use most often, mainly business
user scenarios, or daily end users or user scenarios. However, even if the software passes the three levels
of testing (unit testing, integration testing, and system testing), in actual scenarios, end users may report
some small errors when using the system.

Page 6|6