/
Should you have one unit test or many?
Should you have one unit test or many?
- Eliot Muir
Owned by Eliot Muir
At the start of a project one can boot-strap with one. But it does lead to the problem that developers can unwittingly put in too many dependencies. i.e. violate separation of concerns.
It can be challenging with platforms like windows which are slow to spawn processes to have many independent test programs to run.
, multiple selections available,
Related content
Avoid having too many dependencies
Avoid having too many dependencies
Read with this
Run unit tests without dependencies
Run unit tests without dependencies
More like this
How do it now without a mature library system
How do it now without a mature library system
Read with this
Unit test with race conditions are a problem
Unit test with race conditions are a problem
More like this
Automated build concepts
Automated build concepts
Read with this
Unit tests which take too long to run hurt the effectiveness of your system
Unit tests which take too long to run hurt the effectiveness of your system
More like this