I led into this yesterday when I talked about simplifying the way in which we specify which user is executing the test.
When HP Service Test starts execution it picks up the protocols.config and uses it for your service call. If you have multiple services to hit in your test that are invoked by your test you can write a mapping file that maps each service to the appropriate protocols configuration file. If you are only hitting one service and that service calls other services on your behalf (an orchestration service) you only need the configuration for the service you directly consume.
Once that protocols.config is bound to the service, HP Service Test will not refresh the configuration until the iteration has complete. This is a particularly useless feature especially when you are trying to test multiple user configurations in the one project. As I outlined there are many ways to structure your service test projects and having each action be a test is an issue here. The solution is one project file per configuration. Not a pleasant experience if you have a lot of user configurations to run and lots of services.
|
Ryan Boucher is a Software Inquisitor and is passionate about it. You can find a whole raft of articles and anecdotes about software testing and other topics he gets excited about. |
| Tags |
