I’ve got about 100 unit tests and with a coverage of %20, which I’m trying to increase the coverage and also this is a project in development so keep adding new tests.
Currently running my tests after every build is not feasible they takes about 2 moments.
Test Includes:
- File read from the test folders (data-driven style to simulate some HTTP stuff)
- Doing actual HTTP requests to a local web-server (this is a huge pain to mock, so I won’t)
- Not all of them unit-tests but there are also quite complicated Multithreaded classes which need to be tested and I do test the overall behaviour of the test. Which can be considered as Functional Testing but need to be run every time as well.
Most of the functionality requires reading HTTP, doing TCP etc. I can’t change them because that’s the whole idea of project if I change these tests it will be pointless to test stuff.
Also I don’t think I have the fastest tools to run unit tests. My current setup uses VS TS with Gallio and nUnit as framework. I think VS TS + Gallio is a bit slower than others as well.
What would you recommend me to fix this problem? I want to run unit-tests after every little bit changes btu currently this problem is interrupting my flow.
Further Clarification Edit:
Code is highly coupled! Unfortunately and changing is like a huge refatoring process. And there is a chicken egg syndrome in it where I need unit tests to refactor such a big code but I can’t have more unit tests if I don’t refactor it 🙂
Highly coupled code doesn’t allow me to split tests into smaller chunks. Also I don’t test private stuff, it’s personal choice, which allow me to develop so much faster and still gain a large amount of benefit.
And I can confirm that all unit tests (with proper isolation) quite fast actually, and I don’t have a performance problem with them.
Further Clarification:
Code is highly coupled! Unfortunately and changing is like a huge refatoring process. And there is a chicken egg syndrome in it where I need unit tests to refactor such a big code but I can’t have more unit tests if I don’t refactor it 🙂
Highly coupled code doesn’t allow me to split tests into smaller chunks. Also I don’t test private stuff, it’s personal choice, which allow me to develop so much faster and still gain a large amount of benefit.
And I can confirm that all unit tests (with proper isolation) quite fast actually, and I don’t have a performance problem with them.
These don’t sound like unit tests to me, but more like functional tests. That’s fine, automating functional testing is good, but it’s pretty common for functional tests to be slow. They’re testing the whole system (or large pieces of it).
Unit tests tend to be fast because they’re testing one thing in isolation from everything else. If you can’t test things in isolation from everything else, you should consider that a warning sign that you code is too tightly coupled.
Can you tell which tests you have which are unit tests (testing 1 thing only) vs. functional tests (testing 2 or more things at the same time)? Which ones are fast and which ones are slow?