How can I provide feedback to my team about the changes included in the assembly and their impact on risk?

Question

Is that what you already do, or do you know a good tool?

PURPOSE: The help group understands how recent source changes affect risk, so they know where to focus testing efforts. Provide data over time and send it back to the planning and defining phases of the dev loop area.

PLAN: Combine the svn data with clover complexity data in a report showing the effect of the change on the complexity or risk of the change (# lines x complexity = risk?). This is not ideal, but it can help teams better understand the changes.

Has anyone tried this? If so, what tools did you use and how did you provide this game to the team?

Answer 1

My experience is that tests and risks are identified when new features are introduced or when defects are fixed. All this was done "manually" in all my works.

Your interesting idea is basically a type of CI server plug-in / component for focusing testing based on statistics of previous defects and analyzing the complexity of modified files.

You will obviously need a code / file map to check for cases, and if you had the opposite (failed test cases and files that were changed to fix), you would have some kind of automatic way to generate some information.

, "" "". .. "" , , - ... "" - , .