tag:blogger.com,1999:blog-8486730092200937906.post6233712283786829452..comments2023-12-11T00:30:01.572-08:00Comments on TESTER'S WORLD: Bugs per lines of codeExplorehttp://www.blogger.com/profile/05260796550075594266noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-8486730092200937906.post-25747064383641786752023-02-22T05:55:23.748-08:002023-02-22T05:55:23.748-08:00Thanks for sharing the blog. It's very helpful...Thanks for sharing the blog. It's very helpful and informative. Thank you.<br /><br /><a href="https://www.credosystemz.com/courses/azure-training/" rel="nofollow">Azure Training in Chennai </a> | <a href="https://www.credosystemz.com/courses/azure-training/" rel="nofollow">Azure Certification Training in Chennai </a> Trending Technologyhttps://www.blogger.com/profile/04546877815865778124noreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-45805364748741183832017-06-07T04:13:43.634-07:002017-06-07T04:13:43.634-07:00Excellent and very cool idea and the subject at th...Excellent and very cool idea and the subject at the top of magnificence and I am happy to this post..Interesting post! Thanks for writing it.What's wrong with this kind of post exactly? It follows your previous guideline for post length as well as clarity<br /><a href="http://www.greenstechnologys.com/java-training-course-content.html" rel="nofollow"> Java Training in Chennai</a>Karthika Shreehttps://www.blogger.com/profile/06515257484162457182noreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-26850479331218866162013-08-06T04:55:34.690-07:002013-08-06T04:55:34.690-07:00A computer bug is an error, flaw, mistake, failure...A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result. Bugs arise from mistakes and errors, made by people, in either a program’s source code or its design.<br /><a href="http://www.traklive.com/" rel="nofollow">Defect Bug Tracking</a>Anonymoushttps://www.blogger.com/profile/15473312649299752455noreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-17430762453976030932013-06-10T08:54:30.349-07:002013-06-10T08:54:30.349-07:00I, too, am looking for more depth in the analysis....I, too, am looking for more depth in the analysis. For example, the defects per lines of code tested this month, so that I can trend the number and see that quality is improving toward benchmarks at say the mid-point and at the end of each test phase. Do you have any hints on where to find such metrics for .Net development?Peter DeLormehttp://sc.edunoreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-11108959362998270762013-04-30T22:26:41.904-07:002013-04-30T22:26:41.904-07:00This is very interesting. The number of defects f...This is very interesting. The number of defects found is going to change through the stages, unit test, system integration test, acceptance test. Are there any metrics on the reduction through phases? <br />Also the number of defects is proportional to the test coverage /thoroughness. Are there any metrics on the number of tests per KLOC.<br /> I am working on the first iteration of a new product with 430KLOC and expecting a defect density of less than 1. At more than 0.5 I would be disappointed and my exit criteria is 0.01: t<br />he defects rates quoted in this article seem very high. Perhaps the severity of a defect needs taking into account: a defect that causes a crash and data loss is different to a menu entry typO.pete keyshttps://www.blogger.com/profile/13829165191650271211noreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-72972935186121290302013-04-30T22:25:41.461-07:002013-04-30T22:25:41.461-07:00This is very interesting. The number of defects f...This is very interesting. The number of defects found is going to change through the stages, unit test, system integration test, acceptance test. Are there any metrics on the reduction through phases? <br />Also the number of defects is proportional to the test coverage /thoroughness. Are there any metrics on the number of tests per KLOC.<br /> I am working on the first iteration of a new product with 430KLOC and expecting a defect density of less than 1. At more than 0.5 I would be disappointed and my exit criteria is 0.01: t<br />he defects rates quoted in this article seem very high. Perhaps the severity of a defect needs taking into account: a defect that causes a crash and data loss is different to a menu entry typO.pete keyshttps://www.blogger.com/profile/13829165191650271211noreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-36783888558351334332012-05-29T07:52:52.348-07:002012-05-29T07:52:52.348-07:00i dont have any such metrics, but when the build i...i dont have any such metrics, but when the build is stable in functionality its better to initiate for security testing in parallel to the development. That can actually save time in terms of cost rather hen waiting completely for a finished productExplorehttps://www.blogger.com/profile/05260796550075594266noreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-82796256474354169582012-01-16T13:59:39.480-08:002012-01-16T13:59:39.480-08:00In the real world of in-house testing, you need to...In the real world of in-house testing, you need to make your own expected "bugs by code line" number. Whit this you can define SLA´s for the developers or factories you use.Knachohttps://www.blogger.com/profile/10592918760830329320noreply@blogger.comtag:blogger.com,1999:blog-8486730092200937906.post-32067391982278006522011-09-23T14:35:05.760-07:002011-09-23T14:35:05.760-07:00Any chance you have also collected metrics on the ...Any chance you have also collected metrics on the Cost to achieve a specific kloc level?<br /><br />The reasons this matters is that it relates to the number of Security Defects in code and the cost to control such events.Anonymousnoreply@blogger.com