views:

20

answers:

1

I'm working on a variation of this stack overflow answer that provides reliable cleanup of tests. How do you write unit tests for NUnit addins?

Examining how NUnit self tests, I have determined:

  • You can write tests, that pass, that verify correct behavior of NUnit for failing tests.
  • You write unit tests against test fixtures in a separate assembly (otherwise the fixtures under test will execute with your unit tests)
  • Use NUnit.TestUtilities.TestBuilder to create fixtures and call TestSuite.Run method.

What I don't see are any tests of the add-in process. I've got errors occurring sometime between install and execution. How would I unit test implementations the following?

  • IAddin.Install
  • ITestDecorator.Decorate
A: 

Sometimes, the easiest thing to do is run integration tests. It been a while since I played with the NUnit add-in API, so I can't really say regarding any existing unit tests for the extensibility mechanism. If you have looked through NUnit source code and haven't found any, then I guess that is not something that was tested or even written using TDD.

Like I said, sometimes it's easier to just run integration tests. Have your addon, for example, print something to the output stream, and have your test verify that the exact message was written. This way you could test that both the installation and initialization of your plugin succeeded.

Hope that helps...

hmemcpy
I have integration tests (that fail) and determined that unit tests would more effectively isolate the problem.
Precipitous