Geek Answers Handbook

What is better for bug tracking? Defects on KLOC?

I'm trying to create some internal metrics to demonstrate (determine?) How well TDD improves the level of defects in the code.

Is there a better way than defects / KLOC? What about the functional density of the tongue?

Any comments or suggestions would be helpful.

Thanks - Jonathan

+5
source share
6 answers

You can also consider determining the speed of detecting defects and the speed of resolving defects ... how long does it take to find errors, and once they are found, how long do they take to fix? As far as I know, TDD should improve the repair time because it makes the defects known earlier ... right?

+8

- ; , . , /kloc C /kloc C. , , .

+3

:

...

, . , , , -)

+3

- . , . :

  • ( )
  • ( , , ..).
  • ( ?)
  • 2

, , , . , , , , .

, , . .

+3

, LOC, - , , , "".

, , :

  • . , , , , .
  • . , , , -, .
  • . , , - , .

, . 20 , . , , .

. . , , , , .

You can also flag all tickets in your defect tracking system by project module (especially for large projects) so you can tell when critical modules are in a fragile state.

+1
source

Why do not you consider defects in one case? or defects for every requirement. We encountered practical problems upon arrival at KLOK.

0
source

More articles: