Refactor #4883
Encapsulate RRDtool librrd4 logic so that it's cleaner and easier to test
| Status: | Accepted | Start date: | 09/29/2010 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | testing | |||
| Target version: | 2.7.x | |||
| Affected Puppet version: | 2.6.1 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
Lots of rrd reporting is poorly tested. RRDtool is no longer maintained so ticket #4726 included support for librrd4. To do this there’s a lot of if/else statements that check which rrd library you’re using which makes it harder to write good tests. RRD logic should be wrapped in a class so that we can easily stub the methods to write better tests and make switching out rrd libraries easier in the future.
Related issues
History
Updated by James Turnbull over 1 year ago
- Target version changed from 52 to 2.7.x