An outstanding issue on my project is that we don’t have the facility for our tester to test our WCF services without using our ASP.net front-end. The issue here is that we can (and do) put some code in our front-end that will mask or hide some parts of the services that we should be testing (our services should be accessible from any client). So what do we do? we could create a seperate basic client for each service, but this can take a lot of time and require a lot of work as the service evolves, it also faces the risk that we’ll mask and hide issues again. There are automated tools to generate a form to query the service but a lot of these don’t seem compatible with wshttp bindings; this would lead us to add another binding and endpoint just for testing the service (this might be what we have to do).
The latest information on the horizon is Visual Studio 2008 (orcas) apparently includes a WCF test client. Currently I haven’t used VS2008 so have no knowledge about this tool and can’t seem to find anything useful on the ol’ interweb. Anyone know anything about this tool?