|visits||member for||2 years, 6 months|
|seen||Mar 12 '14 at 17:36|
Testing an internal shared library which is used by more than one product on different release cycles
@Sam Woods I agree. This is actually the way I am planning on doing this. It will take a little more up-front effort to truly extract this core from our current solution so that it can be on its own, but this is how we originally envisioned it, yes.
How can I run a set of tests on multiple machines concurrently using MSTest?
Does this method you describe require anything more than the agent on the machines running the tests?