If the wrapper only forwards the calls to the web services with no conditional logic at all, there’s no point in creating tests against it that don’t go through the real web service. In this case you should create one test for each operation which should only test the ability to reach the web service and come back without unexpected errors. The data returned really don’t matter. This is an integration test between your wrapper and the web service.
If your wrapper includes conditional logic, then it may be a good idea to create tests that exercise all the paths. It’ll be easier to test these cases if you do not depend on the real web service.
For testing the client code (the code that calls the wrapper), you should stub the wrapper or stub the web service. This will give you the control you need to guarantee the client always receives the same output given the same input.