New answers tagged unit-tests
The concept of a unit test is that that test can run as a self contained test. It will test one behavior is true/false. Using helper files is fine as long as changes are consistent and won't affect the behavior of previously written tests. In other words, you shouldn't put anything in your helper that is unique to a single test.
I do not know of any framework/tool that supports this. Have a look at GNU global (http://savannah.gnu.org/projects/global/) - it provides a comprehensive tagging for C programs and command line tools to find references. May be you can build some shell/perl scripts around this to achieve what you want.
Google does this kind of thing. They automatically determine the dependencies in their source code and then use that information to determine what tests to run. You can read about it in How Google Tests Software. As far as I know, Google's system is proprietary. I do not know of a commercial or open-source equivalent.
You could try TestComplete - I believe we use it to test installation here. Essentially you're just testing driving another windows application: if the environment can let you check registry entries and file content then so much the better (I don't work in TC at the moment and can't recall). AutoIT could do it (I have used AutoIT a lot).
With such a large system, I'm assuming that the code is built into many different individual libraries. One way you can narrow down the list of unit tests is to identify and run only those unit tests that are found in the same library as the code change. This approach also assumes local functions aren't exported to become public outside of the module that ...
Top 50 recent answers are included