Solved: Scenario Testing vs. Integration Testing

Former Member · ‎10-24-2007

Hi,

I am really confused with all the Testing lingo. There are so many different types of testing. They all sound like one another. Can somebody please clarify for me the difference btwn scenario testing and integration testing. A definition of each with a brief explanation would be nice.

Thanks

Message was edited by:

Alvaro Tejada Galindo

Former Member · ‎10-24-2007

Hi Ali,

Testing is actually the process of exercising or evaluating a system or a system component by manual or automated means to verify that it satisfies specified requirements. It is the process of executing a program with the intent of locating errors.

There are certain levels of testing as below:

1) Unit Testing or Component Testing or White Box Testing or Scenario Testing

2) Integration Testing or Interface Testing

3) System Testing

So, Scenario or Unit testing is taken care by the developer by executing the particular piece. Example is Developer wrote one program to display the list of vendors details. So, the developer tests whether the program is displaying the data correctly and in the correct format meeting the requirements.

Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. A component, in this sense, refers to an integrated aggregate of more than one unit. In a realistic scenario, many units are combined into components, which are in turn aggregated into even larger parts of the program. The idea is to test combinations of pieces and eventually expand the process to test your modules with those of other groups. Eventually all the modules making up a process are tested together.

Integration testing (sometimes called Integration and Testing, abbreviated I&T) is the phase of software testing in which individual software modules are combined and tested together as a group.The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design items.

Example: A third party system sends vendor data file into our unix box. Our application program read the file and uploads the data and posts to different tables there by creating some document numbers.

Hope this helps.

Thanks,

Srinivasa

Message was edited by:

Alvaro Tejada Galindo

ferry_lianto · ‎10-24-2007

Hi,

Scenario/Unit testing should be taken care of by the developer at the developer side by executing the test scripts which are provided by functional peoples to trace the errors like if its not meeting the reqs or any bugs is there.

Integration testing is being done by functional peoples after deliverables by the developer to test whether its working up to the point and after integrating this module with any other module, what are the erros generating.

Regards,

Ferry Lianto

Former Member · ‎10-24-2007

Hi Ali,

Testing is actually the process of exercising or evaluating a system or a system component by manual or automated means to verify that it satisfies specified requirements. It is the process of executing a program with the intent of locating errors.

There are certain levels of testing as below:

1) Unit Testing or Component Testing or White Box Testing or Scenario Testing

2) Integration Testing or Interface Testing

3) System Testing

So, Scenario or Unit testing is taken care by the developer by executing the particular piece. Example is Developer wrote one program to display the list of vendors details. So, the developer tests whether the program is displaying the data correctly and in the correct format meeting the requirements.

Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. A component, in this sense, refers to an integrated aggregate of more than one unit. In a realistic scenario, many units are combined into components, which are in turn aggregated into even larger parts of the program. The idea is to test combinations of pieces and eventually expand the process to test your modules with those of other groups. Eventually all the modules making up a process are tested together.

Integration testing (sometimes called Integration and Testing, abbreviated I&T) is the phase of software testing in which individual software modules are combined and tested together as a group.The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design items.

Example: A third party system sends vendor data file into our unix box. Our application program read the file and uploads the data and posts to different tables there by creating some document numbers.

Hope this helps.

Thanks,

Srinivasa

Message was edited by:

Alvaro Tejada Galindo