| | 1 | == What is Coverity? == |
| | 2 | "Coverity Prevent is a static code analysis tool for C, C++, C# and Java source code. It is a commercial product which originated as the Stanford Checker, which used abstract interpretation to identify defects in source code." [http://en.wikipedia.org/wiki/Coverity Wikipedia] |
| | 3 | |
| | 4 | == Coverity and Open Source == |
| | 5 | [http://scan.coverity.com/ The Coverity Scan Initiative] |
| | 6 | |
| | 7 | [http://scan.coverity.com/developers-faq.html Dev FAQ] |
| | 8 | |
| | 9 | Haiku is currently a [http://scan.coverity.com/rung1.html Rung 1 project]. |
| | 10 | |
| | 11 | == Workflow == |
| | 12 | * Prerequisites |
| | 13 | 1. Commit rights to Haiku's source repository |
| | 14 | 2. You have been given a Coverity account by a Haiku admin. |
| | 15 | |
| | 16 | * Log on to Coverity's website. (See account info you were given.) |
| | 17 | * Look up a Haiku defect |
| | 18 | * Asses and assign the defect. (To yourself, most likely.) |
| | 19 | * Commit fixes to defects assigned to you. |
| | 20 | Mention the CID number in the commit message. ("Bug so and so. CID XXXX.") |
| | 21 | * Mark the defect as resolved. |
| | 22 | Mentioning the commit revision number. ("fixed in rXXXXX") |
| | 23 | |
| | 24 | == History == |
| | 25 | ||Date ||Fixed||Verified||Uninspected||Lines of Code||Defects / KLOC|| |
| | 26 | ||2011-02-22||1320 ||0 ||1320 ||2,665,930 ||0.400 || |
| | 27 | ||(later) || || || || || || |
| | 28 | |
