Opened 5 years ago

Last modified 4 years ago

#3594 new enhancement

implement tests that load example configs

Reported by: tomek Owned by:
Priority: very low Milestone: Outstanding Tasks
Component: tests Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Kea installs several examples (doc/examples/*) as well as the default config file (src/bin/keactrl/*.conf). We found out that sometimes the examples get out of sync.

We need a test that will load every example and check that at least the configuration phase is completed. This should be a generic test, so adding new examples should be as easy as adding new config files (or perhaps extending a list of configs in a text file somewhere).

See #3535, #3538 for related config issues. Also see
https://lists.isc.org/pipermail/kea-dev/2014-September/000088.html for user feedback about config example.

Subtickets

Change History (7)

comment:1 Changed 5 years ago by stephen

  • Milestone changed from Kea-proposed to Kea0.9.2

comment:2 Changed 5 years ago by hschempf

  • Priority changed from medium to very low

comment:3 Changed 4 years ago by tomek

  • Milestone changed from Kea0.9.2 to Kea0.9.2-final

comment:4 Changed 4 years ago by fdupont

BTW I strongly suggest that all configs which are in the user guide as examples are tested too (i.e., we should get a strong guarantee there is nothing in the documentation which raises for instance a parsing error, or with other words to cut & paste the documentation examples is safe).

comment:5 Changed 4 years ago by marcin

  • Milestone changed from Kea0.9.2 to Kea1.1

Not accepting in 1.0 as per 1.0 tickets scrub on 07/31/2015.

comment:6 Changed 4 years ago by tomek

  • Milestone changed from Kea1.1 to DHCP Outstanding Tasks

comment:7 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.