Integration with training and system testing in the Unit Test structure

Question

As shown in the article domain-manager , I am interested in creating a test harness for integration, which creates a server and many clients, where they all work within the same process . But as soon as I achieve this goal, I will be very tempted to perform such integration and system tests as part of a single test (NUnit test or VS Team).

What are the pros and cons of choosing to run integration or system tests as part of a unit test? Here is my own punch:

Pros

• This can reduce the time and cost of performing integration tests.
• Integration tests are performed, possibly with each assembly.

Against

• Not all integration tests will be fast. Some of them take a minute (for example, a performance-oriented integration test).

In any case, if my new integration testing code does not fit into a single testing system, where would you recommend placing it? Speak differently, what "integration tests" would you recommend?

Answer 1

, - Framework Unit Testing Framework, . , , . , ( ), , , . , , , .

CI, (, ). , , , , , , .

, , , . - . - - Category NUnit, . , , .

Answer 2

.

, . , ( , ).

NUnit - , , . , " " " ".

, ; , . , ( ), .

---

, . , - ( ). , , - , :

void TestDateToString_KnownBug_FailsOnPseudo();

, , , - - .

Answer 3

, unit test . . , , .

, "unit" - .

Pros

• - ( )
• unit test (GUI ..)
• ( , ).
• Unit test , - , . -, .

• , , , - .
• , - , , .
• Most unit test infrastructures do not provide high-level tools such as recording / reproducing test plans or user interfaces suitable for acceptance testing / business users.
• Configuring / disabling can be ugly and complicated if many processes / systems are involved in the testing process. Many unit test frameworks do not support collaborative cancellation, which will allow you to clean the house.