7 System Testing

8/13/2019 7 System Testing

http://slidepdf.com/reader/full/7-system-testing 1/3

Chapter 7 System Testing

SYSTEM TESTING

Software Testing is a critical element of software quality assurance and represents

the ultimate review of specialization, design and coding. The objective of the system

testing is to ensure that all the individual programs are woring and the programs lintogether to meet the requirements specified and to ensure that the computer system and

the associated clerical and other procedures wor together.

Testing is vital to the success of the system. System testing mars a logical

assumption that all the parts of the system are correct! the goal will be successfully

achieved. Special test data is input for processing and the results are e"amined to locate

une"pected results.

Testing Objective

Testing is the process of e"ecuting a program with the intent of finding an error

# good test case is one of that has a higher probability of finding a yet

undiscovered error

# successful test is one that uncovers a yet undiscovered error

System testing is the stage of implementation, which is aimed at ensuring that thesystem wors accurately and efficiently before live operation commences. Testing is a

vital to success of the system. System testing maes a logical assumption that if all parts

of the system are correct, the goal will be successfully achieved.

#$T% &'(#(C'() **




7.1 Unit Testing:

$nit testing is conducted to verify the functional performance of each modular

component of the software. $nit testing focuses on the smallest unit of the software

design +i.e., the module. The white-bo" testing techniques were heavily employed forunit testing.

't tests all of the methods involved in this system and checs the output of each

event

'n this system every module has been separately tested

7.2 Integration Testing:

'n integration testing the individual tested units are grouped as one and the

interface between them is tested. 'ntegration testing identifies the problems that occur

when the individual units are combined.

There are mainly three approaches to do integration testing.

Top-o!n "pproac#

Top down approach tests the integration from top to bottom, it follows thearchitectural structure.

$otto%-&p "pproac#

'n bottom up approach testing taes place from the bottom of the control flow, the

higher level components are substituted with drivers.

$ig bang "pproac#

'n big bang approach most or all of the developed modules are coupled together to

form a complete system and then used for integration testing.

7.' (a)iation Testing

#$T% &'(#(C'() *




This process evaluating #uto &inancing products of a development phase to

determine whether the &inance project meet the specified requirements for that phase.

The %bjective of the validation testing is to ensure that the product is being built

according to the requirements and design specifications. 'n other words, to ensure that

wor products meet their specified requirements.

7.* (eri+ication Testing

The process of evaluating #uto &inancing during or at the end of the development

process to determine whether it satisfies specified requirements. To ensure that #uto

&inancing actually meets the user/s needs, and that the specifications were correct in the

first place. 'n other words, to demonstrate that the product fulfils its intended use when

placed in its intended environment.

7., Test ases

This project includes the following test cases0

Comparison of different data type

'ncorrect logical operator or precedence

1"pectation of equality

'ncorrect comparison of variables

'mproper or non-e"istent loop termination

&ailure to e"it

'mproper modification

#$T% &'(#(C'() *7

7 System Testing

Documents

Transcript of 7 System Testing