INTRODUCTION:

System testing is a type of software testing that evaluates the overall functionality and
performance of a complete and fully integrated software solution. It tests if the system meets
the specified requirements and if it is suitable for delivery to the end-users. This type of
testing is performed after the integration testing and before the acceptance testing.

SYSTEM TESTING

System Testing is a type of software testing that is performed on a complete integrated

System testing detects defects within both the integrated units and the whole system. The
result of system testing is the observed behavior of a component or a system when it is tested.
It is performed to test the system beyond the bounds mentioned in the software requirements
specification (SRS).

System Testing is basically performed by a testing team that is independent of the

System Testing is a black-box testing that focuses on the functionality of an application rather
than the inner workings of a system.

System testing, for example, might check that every kind of user input produces the intended
output across the application. System testing is the third level of testing in the software
development process. It’s typically performed before acceptance testing and after integration
testing.

SYSTEM TESTING PROCESS:

System Testing is performed in the following steps:

 Test Environment Setup: Create testing environment for the better quality testing.
 Create Test Case: Generate test case for the testing process.
 Create Test Data: Generate the data that is to be tested.
 Execute Test Case: After the generation of the test case and the test data, test cases
are executed.
 Defect Reporting: Defects in the system are detected.
 Regression Testing: It is carried out to test the side effects of the testing process.
 Log Defects: Defects are fixed in this step.
 Retest: If the test is not successful then again test is performed.

TYPES OF SYSTEM TESTING:

 Performance testing. Performance testing measures the speed, average load time,
stability, reliability and peak response times of the system under various conditions.
It’s typically coupled with stress testing and may include both hardware and software
testing tools.
 Usability testing. These are tests to evaluate if a system is easy to use and functional
for the end user. Metrics, including user error rates, task success rates, the time it
takes a user to complete a task and user satisfaction, are used during testing.
 Load testing. This is testing to determine how a system or software performs under a
real-life extreme load and test scenarios. Metrics, such as throughput, number of users
and latency, are measured through this testing.
  Regression testing. Also known as sanity testing, it ensures that all changes
introduced into an application or code during system testing, recent code changes or
updates haven’t caused any new bugs or issues. Regression testing is responsible for
the functionality of the existing features of a system or software.
 Migration testing. This is conducted to ensure smooth migration of legacy systems to
new systems without disruptions, data loss or downtimes.
 Scalability testing. This measures an application’s or system’s capability to scale up
or down when trying to meet the changing user requirements.
 Functionality testing. This is conducted to validate a system’s functionality against
its functional and business requirements.
 Recovery testing. This is a type of nonfunctional testing done to ensure that a system
is capable of recovering from certain system errors, crashes and failures.

TOOLS USED FOR SYSTEM TESTING :

 JMeter
 Gallen Framework
 Selenium

Here are a few common tools used for System Testing:

 HP Quality Center/ALM
 IBM Rational Quality Manager
 Microsoft Test Manager
 Selenium
 Appium
 LoadRunner
 JMeter
 Apache JServ

Note: The choice of tool depends on various factors like the technology used, the size of the
project, the budget, and the testing requirements.

ADVANTAGES OF SYSTEM TESTING :

o The testers do not require more knowledge of programming to carry out this testing.
o The testing environment Is similar to that of the real time production or business
environment.
o Verifies the overall functionality of the system.
 o Detects and identifies system-level problems early in the development cycle.
o Helps to validate the requirements and ensure the system meets the user needs.
o Improves system reliability and quality.
o Facilitates collaboration and communication between development and testing teams.
o Enhances the overall performance of the system.
o Increases user confidence and reduces risks.
o Facilitates early detection and resolution of bugs and defects.
o Supports the identification of system-level dependencies and inter-module
interactions.
o Improves the system’s maintainability and scalability.

DISADVANTAGES OF SYSTEM TESTING :

o This testing is time consuming process than another testing techniques since it checks
the entire product or software.
o The cost for the testing will be high since it covers the testing of entire software.
o It needs good debugging tool otherwise the hidden errors will not be found.
o Can be time-consuming and expensive.
o Requires adequate resources and infrastructure.
o Can be complex and challenging, especially for large and complex systems.
o Dependent on the quality of requirements and design documents.
o Limited visibility into the internal workings of the system.
o Can be impacted by external factors like hardware and network configurations.
o Requires proper planning, coordination, and execution.
o Can be impacted by changes made during development.
o Requires specialized skills and expertise.
o May require multiple test cycles to achieve desired results.

CONCLUSION

System testing is very important and if not done properly critical issues can be faced in the
live environment.A system as a whole has different characteristics to be verified. A simple
example would be any website. If it’s not tested as a whole then the user might find that site
to be very slow or the site might get crashed once a large number of users log in at the same
time.And these characteristics cannot be tested until the website is tested as a whole

BIBLIOGRAPHY
Black, Rex. Managing the Testing Process (2nd ed.). New Jersey: Wiley Publishing, 2002.

Kaner, Cem. Exploratory Testing. Quality Assurance Institute Worldwide Annual Software
Testing Conference: Orlando, FL. Archived from the original (PDF) on January 26, 2009.
Retrieved April 20, 2023

https://www.geeksforgeeks.org/system-testing/