Skip to Content
avatar image
Former Member

hii gurus

Hii Gurus,

What is Unit and integration testing.

Pls explain.

thanks and regards

Montee

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • avatar image
    Former Member
    May 24, 2007 at 07:23 AM

    Hi Monti,

    Sent Mail.

    Reward Points if it helps

    Regards

    Srini

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 24, 2007 at 07:10 AM

    unit testing means va01 sales order will be tested like going to va01, doc type, sale org, dist.chal, div and enter giving sold to, and material... etc.. this is unit testing like these delivey , billing , cr.memo reqest...etc...

    integration test means those trancstion will intergrate with other modules.. people of those module involve ...STO, 3rd party, rev.a/c determination etc...

    Reward if it helps..

    ramki

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 24, 2007 at 07:11 AM

    Hi

    unit testing - you on your own test scenerios of the process flow.

    Integration testing - entire one complete cycle testing starting from the orders to till billing where all the module consultants will be involved in testing.

    i hope this will be helpful, if so give some reward points.

    Regards

    Siva

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 24, 2007 at 07:11 AM

    Hi.,

    Unit Testing

    A unit test is a procedure used to validate that a particular module of source code is working properly from each modification to the next. The procedure is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. Ideally, each test case is

    separate from the others; constructs such as mock objects can assist in separating unit tests. This type of testing is mostly done by the developers and not by end-users.

    Integration testing

    Integration testing can proceed in a number of different ways, which can be broadly characterized as top down or bottom up. In top down integration testing the high level control routines are tested first, possibly with the middle level control structures present only as stubs. Subprogram stubs were presented in Section 2 as incomplete subprograms which are only present to allow the higher level control routines to be tested. Thus a menu driven program may have the major menu options initially only present as stubs, which merely announce that they have been successfully called, in order to allow the high level menu driver to be tested.

    Top down testing can proceed in a depth-first or a breadth-first manner. For depth-first integration each module is tested in increasing detail, replacing more and more levels of detail with actual code rather than stubs. Alternatively breadth-first would proceed by refining all the modules at the same level of control

    throughout the application. In practice a combination of the two techniques would be used. At the initial stages all the modules might be only partly functional, possibly being implemented only to deal with non-erroneous data. These would be tested in breadth-first manner, but over a period of time each would be

    replaced with successive refinements which were closer to the full functionality. This allows depth-first testing of a module to be performed simultaneously with breadth-first testing of all the modules.The other major category of integration testing is bottom up integration testing where an individual module is

    tested from a test harness. Once a set of individual modules have been tested they are then combined into a collection of modules, known as builds, which are then tested by a second test harness. This process can continue until the build consists of the entire application.

    In practice a combination of top-down and bottom-up testing would be used. In a large software project being developed by a number of sub-teams, or a smaller project where different modules were being built by individuals. The sub-teams or individuals would conduct bottom-up testing of the modules which they were

    constructing before releasing them to an integration team which would assemble them together for top-down testing.

    I think this will help.

    REWARD if helpfull

    Thanks & Regards

    Narayana

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 24, 2007 at 07:11 AM

    HI Monti,

    give your mail id

    regards

    srini

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 24, 2007 at 07:14 AM

    Unit testing at a stand alone level of the function point i.e. only the given process is tested without checking the dataflow to other systems or other processes in a given IT environment.

    Integration Testing encompasses the testing of all the related functionalities of a process. All the upstream and downstream systems are tested to validate the correct functioning of the new process.

    Pls award points if this helps.

    Reg

    Sachin

    Add comment
    10|10000 characters needed characters exceeded