With the proliferation of Agile Programming and an understanding of the importance of Unit Testing, it is apparent that
Unit Tests are an important part of development.

Further, since most new "Methodologies" for programming emphasize developing the tests before developing the code, tests
are becoming a more common component within projects.

Therefore, it makes sense to me to have the IDE identify which tests a module I have just edited will fail based on the
edit I have made.

This could be accomplished using a "Test on Save" operation which limits the tests being executed to the subset of tests
which cause a module to be executed.  Both of these information nuggets are easily obtainable using current capabilities
within the IDE.

Then when a user saves, as part of the forthcoming incremental compilation (Build on Save) capability this subset of
tests can be executed and the results provided back to the user.

Additionally, if the user opts not to have the tests run in this fashion, it can easily be disabled via a configuration
option.