Should you have one unit test or many?

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.