Forum Discussion
BA_Service_Haus
14 years agoRegular Contributor
Hi Ole.
thanks for your reply.
For a better understanding, please let me explain our approach:
- the tester defines the request and assertion data for one service operation by using keywords.
- the kdt(keyword driven test)-Framework writes them down to a testcase within a soapUI project file
- with another keyword this soapUI testcase can be executed (this is done by calling the testrunner.bat for the prepared testcase)
- if the user wants to test another operation within the same kdt, he just repeats the same steps
You can see, we call the testrunner.bat for a single testcase which always contains just a single operation request.
Now we want enable the user to define a required mock, by using keywords.
But I don't know how to start the mock the best way.
One idea currently is to define the start and stop of the mock within the setup and tear down script (this can be done by the framework too).
But if there is an "intelligent" mock (e.g. a stateful one), than it might be necessary to run the mock from the start and not stop it until the whole kdt was finished.
If you have another (better) idea, I would be glad to hear it.
Best regards
Nico
thanks for your reply.
For a better understanding, please let me explain our approach:
- the tester defines the request and assertion data for one service operation by using keywords.
- the kdt(keyword driven test)-Framework writes them down to a testcase within a soapUI project file
- with another keyword this soapUI testcase can be executed (this is done by calling the testrunner.bat for the prepared testcase)
- if the user wants to test another operation within the same kdt, he just repeats the same steps
You can see, we call the testrunner.bat for a single testcase which always contains just a single operation request.
Now we want enable the user to define a required mock, by using keywords.
But I don't know how to start the mock the best way.
One idea currently is to define the start and stop of the mock within the setup and tear down script (this can be done by the framework too).
But if there is an "intelligent" mock (e.g. a stateful one), than it might be necessary to run the mock from the start and not stop it until the whole kdt was finished.
If you have another (better) idea, I would be glad to hear it.
Best regards
Nico