Making Separate Assemblies For Different Types Of Tests For The Same Component?

Posted by sooprise on Programmers See other posts from Programmers or by sooprise
Published on 2011-05-31T21:11:52Z Indexed on 2012/06/27 21:25 UTC
Read the original article Hit count: 165

Filed under:
|
|
|
|

I was told by a few members here that splitting up my unit tests into different assemblies for different components is the best way to structure unit tests. Now, I have a few questions about that idea.

  1. What are the advantages of this? Organization, and isolation of errors?
  2. Let's say I have a component named "calculator", and I create an assembly for the unit tests on "calculator". Would I create a separate assembly for the integration tests I want to run on "calculator"? Or is the definition of an integration test a test across multiple components, like "calculator" and whatever else, which would require a separate assembly to test both of them together? In that case, would I have one assembly to do all of the integration testing for every component combination?

© Programmers or respective owner

Related posts about c#

Related posts about unit-testing