Each of these reporting methods have a companion method that sets the value. So basically we are setting the value and verifying that the contents of the return element are what we just set. Some of the methods have dates, server info that we have to wildcard, but 2 of these 3 methods don't. The 3rd method is a "getAll" type method, so it's going to contain the responses of all 34 reporting methods and I'll just have to deal with that when I come to it.
The event handler has worked fine for all the other methods we've tried and we already have testcases and assertions built, so I don't want to change anything with those testcase assertions.
We changed tools part way through the project as the other one was inadequate (internal tool they tried to make work for verifying web services) so there was no time to plan for this, we've just had to deal with it as it comes. I have been trying at the same time to make it so anyone, no matter the technical background is, can take this project and run with it relatively quickly. Of course we would buy more licenses if that occurs...
For 2 of the 3 methods we could probably just do an xpath assertion or a simple contains would work as well, but we'd still need to ignore these methods in the event handler. We could also just turn off the event handler, but in order to run through all the suites at the same time it would be better if we could turn it off in the event handler.
Thanks,
Mary
