This is a test coverage method that was used in crytek, it is a rather clever idea
http://code.google.com/p/mcover/ I'm thinking if we embed it, and set up markers through out, we can have it save out the markers that were triggered by a user during usage then users can email in the list of saved out markers, and we can see what actual code is being used, and reduce testing efforts by the team to those areas that users are not hitting. LetterRip _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
