Last week, I followed the training ‘Professionnal Scrum Developper’ with Richard Hundhausen. He showed a feature of Visual Studio.Net that I had never use: The test impact analysis tool. In a nutshell, this is a tool that analyses your last code changes, and will detect which unit tests has to be rerun to ensure you did not break anything important. Sounds promising. But wait… how does it work internally? I guess it detects...