If developers do unit testing in their development environment, before testing the original control, should the environment (including tests) be used?
Should all assemblies be publicly available?
I think sandboxing is a good idea. It saved me several times. I usually have several different virtual machines floating around that I use for development, and if I ruin this very badly, I don't have to wait until my machine is rebuilt.
, . , - , , , , , .
- , , , , . . , .
, . ( unit test).
- , , , , unit test . , , : unit test , .
;), , , . , , , , - - . , / - . , , , ..
, , . . TDD , . , , , , -, , . , . , -, .
, . . , . . ? -, . , .
What benefit do you see in this? In particular, this means that everyone receives e-mail information about each picayune test failure for each developer.
It just helps to distract everyone.
Avoid the temptation to do something just because it is possible; let your requirements lead your process. Do not create a new process just because you can.
Source: https://habr.com/ru/post/1706782/More articles:ASP.NET angle brackets with '#' or '='. Who cares? - asp.netSelect .NET Framework to use in Visual Studio - .netCertificate Authority for me / small organization - opensslHow to improve this piece of code? - recursionDoes OpenId support Ajax login? - ajaxExcel date field conversion problem - c #Differences in HTML borders in FF and IE - htmlBlackberry - testing an application on a device? - testingLinear selection in VIM - vimHow can I get notifications when a USB device is connected? - c #All Articles