Feeds:
Posts
Comments

Posts Tagged ‘integration test’


So, I was tasked with testing a WCF service that publishes an interface for our customers to insert stuff into our database. The WCF service is an integrator and the functions allow customers to add their data in a controlled way without having to go through our main application. It’s quite useful as they can basically add data from any source they like and it is then correctly inserted and can be viewed in the main application.

We just had a new release and we changed how time is stored in the database. We went from local time to UTC. This is quite a major change but the users shouldn’t need to be aware of it. I made the changes to this WCF service and then it was supposed to be tested. That testing was never done and I got tasked with doing it, ASAP, it should be finished yesterday, get to work!

Anyway, started fiddling with nUnit to do integration testing.
Wrote a test, compile fine and went on to run the test in nUnit when I’m greeted by the following message:

(TestFixtureSetUp): SetUp : System.InvalidOperationException : Could not find default endpoint element that references contract 'NIS.TicketIntegrationServiceSoap' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.

After looking through app.config and it’s various locations I get the tip from a colleague to try associating dlls to nUnit and double click on it. Voila! Worked perfectly.

My friend told me that this has to do with working directory for nUnit. It seems this issue has been around for quite a while and is not yet resolved.

Read Full Post »