TESTING AND IMPLIMENTATION
Introduction:
Software testing is a critical element of software quality assurance
and represents the ultimate review of specification, design and coding.
Testing presents an interesting of a system using various test data.
Preparation of the test data plays a vital role in the system testing.
After preparation the test data, the system under study is tested those
test data. Errors were found and corrected by using the following
testing steps and corrections are recorded for future references. Thus,
series of testing is performed on the system before it is already for
implementation.
The development of software systems involves a series of production
activities where opportunities for injection of human errors are
enormous. Errors may begin to occur at the very inception of the
process where the objectives may be erroneously or imperfectly
specified as well as in later design and development stages. Because of
human in ability to perform and communicate with perfection,
software development is followed by assurance activities.
Quality assurance is the review of software products and related
documentation for completeness, correctness, reliability and
maintainability. And of course it includes assurances that the system
meets the specification and the requirements for its intended use and
performance. The various levels of quality assurance are described in
the following sub sections.
System Testing
Software testing is a critical element of software quality assurance and
represents the ultimate review of specifications, design and coding. The
testing phase involves the testing of system using various test data;
Preparation of test data plays a vital role in the system testing. After
preparation the test data, the system under study is tested.
Those test data, errors were found and corrected by following testing
steps and corrections are recorded for future references. Thus a series
testing is performed on the system before it is ready for
implementation.
The various types of testing on the system are:
Unit testing
Integrated testing
Validation testing
Output testing
User acceptance testing
Unit testing
Unit testing focuses on verification effort on the smallest unit of
software design module. Using the unit test plans. Prepared in the
design phase of the system as a guide, important control paths are
tested to uncover errors within the boundary of the modules. The
interfaces of each of the modules under consideration are also tested.
Boundary conditions were checked. All independent paths were
exercised to ensure that all statements in the module are executed at
least once and all error-handling paths were tested. Each unit was
thoroughly tested to check if it might fall in any possible situation. This
testing was carried out during the programming itself. At the end of this
testing phase, each unit was found to be working satisfactorily, as
regarded to the expected out from the module.
Integration Testing
Data can be across an interface one module can have an adverse effect
on anothers sub function, when combined may not produce the
desired major function; global data structures can present problems.
Integration testing is a symmetric technique for constructing tests to
uncover errors associated with the interface. All modules are combined
in this testing step. Then the entire program was tested as a whole.
Validation Testing
At the culmination of integration testing, software is completely
assembled as a package. Interfacing errors have been uncovered and
corrected and final series of software test-validation testing begins.
Validation testing can be defined in many ways, but a simple definition
is that validation succeeds when the software functions in manner that
is reasonably expected by the consumer. Software validation is
achieved through a series of black box tests that demonstrate
conformity with requirement. After validation test has been conducted,
one of two conditions exists.
The function or performance characteristics confirm to specification
that are accepted.
A validation from specification is uncovered and a deficiency created.
Deviation or errors discovered at this step in this project is corrected
prior to completion of the project with the help of user by negotiating
to establish a method for resolving deficiencies. Thus the proposed
system under consideration has been tested by using validation testing
and found to be working satisfactorily.
Output Testing
After performing the validation testing, the next step is output testing
of the proposed system, since a system is useful if it does not produce
the required output in the specific format required by them tests the
output generator displayed on the system under consideration. Here
the output is considered in two ways: - one is onscreen and the other is
printed format. The output format on the screen is found to be correct
as the format was designed in the system design phase according to the
user needs. As far as hardcopies are considered it goes in terms with
the user requirement. Hence output testing does not result any
correction in the system.
User Acceptance Testing
User acceptance of the system is a key factor for success of any system.
The system under consideration is tested for user acceptance by
constantly keeping in touch with prospective system and user at the
time of developing and making changes whenever required.
