System, method, and computer program for generating a detailed design of at least one telecommunications based integration testing project

1. A method, comprising:

analyzing, through a computer system, a scope of at least one integration testing project, the integration testing project being associated with a plurality of systems provided by different vendors, and the analyzing including converting data flows into integration chains which are each a series of interfaces by which data moves between the systems for automatic processing thereof by the systems;

tracking, through the computer system, vendor-related information associated with the at least one integration testing project, including logging the interfaces to a test management console available to the different vendors and mapping the interfaces to the integration testing project;

generating, through the computer system, an activity library associated with the at least one integration testing project, the activity library including standalone generic building blocks that describe actions which verify each of the interfaces;

determining, through the computer system, scenarios associated with the at least one integration testing project;

presenting, through the computer system, a high level design including the integration chains of the at least one integration testing project for review by at least the vendors;

generating, through the computer system, testing instructions based on the scenarios associated with the at least one integration testing project and the high level design; and

generating, through the computer system, a detailed design of the at least one integration testing project utilizing the testing instructions and the activity library by generating test cases that are linked to the interfaces.

2. The method of claim 1 , wherein analyzing the scope of the at least one integration testing project further includes removing dependencies by creative data reuse or data simulators.

3. The method of claim 2 , wherein analyzing the scope of the at least one integration testing project further includes describing all interfaces in the scope as the integration chains with minimal dependencies on each integration chain and minimal interfaces per integration chain, while still allowing a user to view data flows properly in a higher solution structure.

4. The method of claim 3 , wherein analyzing the scope of the at least one integration testing project further includes identifying the integration chains, input parameters associated with the integration chains that generate permutations, and possible validation points for each data produced in the integration chains.

5. The method of claim 1 , wherein determining the scenarios associated with the at least one integration testing project includes utilizing information associated with full coverage, risk calculation, business priority, and customization level, while filtering using a pairwise reduction approach to reach a minimal set.

6. The method of claim 5 , wherein determining the scenarios associated with the at least one integration testing project includes breaking down scenarios into multiple sub-scenarios which will allow quick identification of the scope.

7. The method of claim 1 , wherein generating the testing instructions based on the scenarios associated with the at least one integration testing project includes converting an integration chain high level description to actual testing instructions describing which activities need to be performed and at which conditions to generate a flow.

8. The method of claim 7 , wherein generating the testing instructions based on the scenarios associated with the at least one integration testing project further includes mapping the interfaces to tests.

9. The method of claim 1 , wherein linking test cases to the interfaces provides a real time view of interface delivery status.

10. A computer program product embodied on a non-transitory computer readable medium, comprising:

computer code for analyzing, through a computer system, a scope of at least one integration testing project, the integration testing project being associated with a plurality of systems provided by different vendors, and the analyzing including converting data flows into integration chains which are each a series of interfaces by which data moves between the systems for automatic processing thereof by the systems;

computer code for tracking, through the computer system, vendor-related information associated with the at least one integration testing project, including logging the interfaces to a test management console available to the different vendors and mapping the interfaces to the integration testing project;

computer code for generating, through the computer system, an activity library associated with the at least one integration testing project, the activity library including standalone generic building blocks that describe actions which verify each of the interfaces;

computer code for determining, through the computer system, scenarios associated with the at least one integration testing project;

computer code for presenting, through the computer system, a high level design including the integration chains of the at least one integration testing project for review by at least the vendors;

computer code for generating, through the computer system, testing instructions based on the scenarios associated with the at least one integration testing project and the high level design; and

computer code for generating, through the computer system, a detailed design of the at least one integration testing project utilizing the testing instructions and the activity library by generating test cases that are linked to the interfaces.

11. A computer system comprising:

a memory system; and

one or more processing cores coupled to the memory system and that are each configured to:

analyze a scope of at least one integration testing project, the integration testing project being associated with a plurality of systems provided by different vendors, and the analyzing including converting data flows into integration chains which are each a series of interfaces by which data moves between the systems for automatic processing thereof by the systems;

track vendor-related information associated with the at least one integration testing project, including logging the interfaces to a test management console available to the different vendors and mapping the interfaces to the integration testing project;

generate an activity library associated with the at least one integration testing project, the activity library including standalone generic building blocks that describe actions which verify each of the interfaces;

determine scenarios associated with the at least one integration testing project;

present a high level design including the integration chains of the at least one integration testing project for review by at least the vendors;

generate testing instructions based on the scenarios associated with the at least one integration testing project and the high level design; and

generate a detailed design of the at least one integration testing project utilizing the testing instructions and the activity library by generating test cases that are linked to the interfaces.