Scribd
Upload
403 views

System Testing

The document discusses different types of software testing including unit testing, integration testing, functional testing, and system testing. Unit testing verifies individual code units, integration testing verifies code units work together, functional testing ensures code meets requirements, and system testing evaluates a complete integrated system.

Uploaded by

sudhakar kethana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
403 views

System Testing

The document discusses different types of software testing including unit testing, integration testing, functional testing, and system testing. Unit testing verifies individual code units, integration testing verifies code units work together, functional testing ensures code meets requirements, and system testing evaluates a complete integrated system.

Uploaded by

sudhakar kethana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

SYSTEM TESTING:

The purpose of testing is to discover errors. Testing is the


process of trying to discover every conceivable fault or weakness in a work product.
It provides a way to check the functionality of components, sub-assemblies,
assemblies and/or a finished product It is the process of exercising software with the
intent of ensuring that the Software system meets its requirements and user
expectations and does not fail in an unacceptable manner.

There are various types of test. Each test type addresses a specific testing
requirement.

TYPES OF TESTING:

Unit Testing:

Unit testing is the testing of individual hardware or software units or


groups of related units. Using white box testing techniques, testers (usually the
developers creating the code implementation) verify that the code does what it is
intended to do at a very low structural level. For example, the tester will write some
test code that will call a method with certain parameters and will ensure that the
return value of this method is as expected. Looking at the code itself, the tester
might notice that there is a branch (an if-then) and might write a second test case to
go down the path not executed by the first test case. When available, the tester will
examine the low-level design of the code; otherwise, the tester will examine the
structure of the code by looking at the code itself. Unit testing is generally done
within a class or a component.

Integration testing:

Integration test is testing in which software components, hardware


components, or both are combined and tested to evaluate the interaction between
them. Using both black and white box testing techniques, the tester (still usually the
software developer) verifies that units work together when they are integrated into a
larger code base. Just because the components work individually, that doesn’t
mean that they all work together when assembled or integrated. For example, data
might get lost across an interface, messages might not get passed properly, or
interfaces might not be implemented as specified. To plan these integration test
cases, testers look at high- and low-level design documents.

Functional testing:

Functional testing in which the high-level design and the


customer requirements specification to plan the test cases to ensure the code does
what it is intended to do. Functional testing involves ensuring that the functionality
specified in the requirement specification works. System testing involves putting the
new program in many different environments to ensure the program works in typical
customer environments with various versions and types of operating systems and/or
applications.

System testing:

System testing is testing conducted on a complete, integrated system


to evaluate the system compliance with its specified requirements. Because system
test is done with a full system implementation and environment, several classes of
testing can be done that can examine non-functional properties of the system. It is
best when function and system testing is done by an unbiased, independent
perspective (e.g. not the programmer). Stress testing conducted to evaluate a
system or component at or beyond the limits of its specification or requirement. For
example, if the team is developing software to run cash registers, a non-functional
requirement might state that the server can handle up to 30 cash registers looking up
prices simultaneously. Stress testing might occur in a room of 30 actual cash
registers running automated test transactions repeatedly for 12 hours.

You might also like