Page 214 - DCAP302_ENTERPRISE_RESOURCE_PLANNING
P. 214

Enterprise Resource Planning




                    notes          integration testing

                                   The software component of the system is assembled into a module and tested for
                                   1.   Data integrity

                                   2.   Configuration
                                   3.   Parameters
                                   It also helps identify resource problems and ensures that the module works on the environment.
                                   Integration testing can be ‘bottom-up’ or a ‘top-down’ approach.

                                   The ‘bottom-up’ approach combines one or more modules that perform a major function of the
                                   software system into a build which can be tested or demonstrated and tests the build. In the
                                   ‘top-down’ approach the top-level control is tested first and all modules that comprise a major
                                   function are integrated so as to demonstrate an operational function. Both the approaches are
                                   used in Integration test plans.

                                   system testing

                                   Software is but one part of a system that includes hardware, network and users. The focus of System
                                   testing is on testing the complete integrated system with reference to the System Specifications.
                                   The tests address system characteristics such as performance, security and recovery.

                                   acceptance testing

                                   This is also known as validation / functional testing. Acceptance testing demonstrates that the
                                   software is operational and conforms to all functional and performance requirements documented
                                   in the Software Requirement Specifications. It verifies the operational flow and evaluates the
                                   fitness of the system on the field from the User’s perspective.
                                   Ideally the tests are executed by the users / requestors without the assistance of the developers.
                                   The testing team should approach testing from the ultimate user’s viewpoint. The successful
                                   testing of the software instills confidence in the Users.

                                   12.5.2 planning for testing

                                   The Testing process as seen earlier starts from the definition phase and is a set of activities as
                                   indicated below.

                                   1.   Preparation of the Test Plan
                                   2.   Definition of the Test Design & Criteria
                                   3.   Identification of the Test cases & data set
                                   4.   Recording the results

                                   5.   Debugging and correction
                                   6.   Definition of the next testing cycle.
                                   A test plan has to be prepared for each level of testing. The test plan defines the scope, approach,
                                   type and the Pass / Fail / suspension criteria. Various types of testing as indicated below can be
                                   planned:
                                   1.   Functional  testing  which  focuses  on  the  business  requirements,  similar  to  acceptance
                                       testing.





          208                              LoveLy professionaL university
   209   210   211   212   213   214   215   216   217   218   219