Forum Discussion
milano
14 years agoOccasional Contributor
Hi,
I've got some more insights and now I would really like if someone from support could take a look at this. I'm beginning to understand how this works and why there is a problem:
A) It seems that any response test step (waiting for a request and returning a response) is available and visible as soon as there are no other not-executed test steps involving the same service before it. Meaning:
1. Step 1, Mock Service 1, Operation 1,
2. Step 2, 3, .... n : Any number of steps involving services other than MS1
n+1. Step n+1: Mock Service 1, Operation 2 (or Op1 or any Op) (response step)
As soon as Step 1 has completed, Step n+1 is visible and accessible even while not activated. That is, at any moment before the activation of Step n+1, if called, it will execute and respond properly. Note that if MS1,Op2 is called before or during Step 1, the Step n+1 will not react in any way.
B) When the Step n+1 is activated, the existing request received just a bit ago is cleared, and the step is reset and readied for execution. Then it executes as if nothing happened, and waits for invocation of MS1, Op2. However, in my case, the invocation never comes as it has been already done before the step activation.
So, it seems to me that:
1. The test step should not be responsive until it is activated.
or
2. If there is some reason for it to be responsive before activation, it shouldn't clean and ignore the already received message.
Any comments are very appreciated.
Milan
I've got some more insights and now I would really like if someone from support could take a look at this. I'm beginning to understand how this works and why there is a problem:
A) It seems that any response test step (waiting for a request and returning a response) is available and visible as soon as there are no other not-executed test steps involving the same service before it. Meaning:
1. Step 1, Mock Service 1, Operation 1,
2. Step 2, 3, .... n : Any number of steps involving services other than MS1
n+1. Step n+1: Mock Service 1, Operation 2 (or Op1 or any Op) (response step)
As soon as Step 1 has completed, Step n+1 is visible and accessible even while not activated. That is, at any moment before the activation of Step n+1, if called, it will execute and respond properly. Note that if MS1,Op2 is called before or during Step 1, the Step n+1 will not react in any way.
B) When the Step n+1 is activated, the existing request received just a bit ago is cleared, and the step is reset and readied for execution. Then it executes as if nothing happened, and waits for invocation of MS1, Op2. However, in my case, the invocation never comes as it has been already done before the step activation.
So, it seems to me that:
1. The test step should not be responsive until it is activated.
or
2. If there is some reason for it to be responsive before activation, it shouldn't clean and ignore the already received message.
Any comments are very appreciated.
Milan
Related Content
- 2 years agoKimdongart1
- 2 years agorkadali
Recent Discussions
- 4 days agoemoya