Confirmed users, Bureaucrats and Sysops emeriti
1,531
edits
CodeCoverage/Firefly: Difference between revisions
→What
ChrisHofmann (talk | contribs) (→What) |
ChrisHofmann (talk | contribs) (→What) |
||
| Line 40: | Line 40: | ||
This section describes the work flow for recording information about those priorities and decisions; and then process for starting, tracking, and completing work to build test cases and get them into automated test suites. | This section describes the work flow for recording information about those priorities and decisions; and then process for starting, tracking, and completing work to build test cases and get them into automated test suites. | ||
== What == | == What: Code Coverage Reports and Tools == | ||
Code coverage runs happen on the weekends when extra build cycles area available. Shorter cycles are eventually planned if they prove useful. | Code coverage runs happen on the weekends when extra build cycles area available. Shorter cycles are eventually planned if they prove useful. | ||
The output of those runs are published at: | |||
... | |||
You can also instrument and run code coverage tools on your own builds. Here is how to do that.... | You can also instrument and run code coverage tools on your own builds. Here is how to do that.... | ||