Geek Answers Handbook

Integration testing

I am developing on .net and using NUnit. I have tests for different classes and for each of the different modules.

Now I need to test all the modules together! modules communicate with each other through DB and Tibco infrustructure.

How can I check out this whole symphony?

PS - if in this case there is something more useful than NUnit, I am open to suggestions.

+4
source share
2 answers

If the classes called each other directly, it would be easy to write an integration test - just name the top-level class without providing any bullying. In your case, you can:

  • Build your first module
  • Make the appropriate method call that should be stored in the database
  • Create a second module
  • Make the appropriate call, which should receive the information stored in step 2
  • Etc.

I see no problem using NUnit as a runner for this test. My suggestion would be to mark the test as Explicit so that it does not run as part of a regular build or test run.

+1
source

In my opinion, you should not integrate the test.

Unit test for basic validation and acceptance for the client / product owner.

If you, however, can formulate an acceptance test in NUnit, I think. I suggest you read this . This is very opposed, but I agree.

There are tools for acceptance testing (for example: cucumber and specflow ), but they all depend on communication with the client.

-4
source

More articles:


All Articles