Suppose I have two separate processes P1 and P2. In P1 and P2 there are several modules/components which are standalone. There is no dependency between P1 and P2. P1 and P2 are tested separately and they have their own test scenario. Now when P1 and P2 interact with each other I am planning to combine their own test scenario to one scenario. Is there any related work on this issue?
Hi Muhammad,
What you are describing is precisely the difference between unit testing and integration testing.
As you state, processes P1 and P2 must be tested individually to ensure that they are fit for use. This includes ensuring that changes made to individual components over time do not break their implementation rendering them unfit. In particular, you must ensure that individual components react properly when their preconditions are not met, and that they deliver what is expected from them, i.e., that they meet their own postconditions.
Integration testing is a step beyond because, even in the case that individual modules do provide what is expected from them in each invocation, it is not guaranteed that interaction between modules will proceed in the right sequence, or that each module will meet each other's expectations. So at this point I would advice against repeating individual, unit tests in integration testing. Rather, integration testing should precisely target behaviour that requires interaction between components, and this is explicitely orthogonal to unit testing.
To sum up: do unit-test your individual modules and target for violated preconditions and met postconditions; do integration-test your combined modules and target for results that require interaction.
Hope that helps,
Fernando
https://en.wikipedia.org/wiki/Unit_testing
https://en.wikipedia.org/wiki/Integration_testing
Adding to Fernanado's reply for detailed scenarios you need to create Test Suites and Test Plan for Individual process and also integration testing plan.
There are many tools available to I had personally worked for tool called QMetry.
http://www.qmetry.com/
Though it is paid you can ask for evaluation for few day .
Hope this helps
Probably you are trying to mix up two levels of testing i.e; unit testing and integration testing. Each of which serves a different purpose and helps us to uncover different types of bugs
You said that there is no dependency but now you are trying to combine those processes that means there must be dependency.. So from unit testing it is going to phase of integration testing. and you require different scenarios for each type of testing. In case of Unit testing it had one scenario but when you are combining then it requires a different scenario with those test paths that shows how those processes work together.
- Badges
- Science topic
- Similar topics
- Computer Science