Opened 6 years ago

Last modified 4 years ago

#3098 new task

Ensure test names follow the same standard

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

Description

Within BIND 10, some test names are in CamelCase whereas others follow the same pattern but start with a lowercase letter (e.g. camelCase).

The BIND 10 standard should be updated to define the format of test names, and the changes applied to all BIND 10 tests.

Subtickets

Change History (6)

comment:1 Changed 6 years ago by vorner

I always thought we use CamelCase for fixtures (as they are classes) and camelCase for test names, as they are methods. But, is it really important enough to care?

comment:2 Changed 6 years ago by muks

  • Estimated Difficulty changed from 0 to 5

comment:3 Changed 6 years ago by muks

  • Milestone New Tasks deleted

comment:4 Changed 6 years ago by stephen

  • Milestone set to Common Outstanding Tasks

comment:5 Changed 4 years ago by tomek

  • Milestone changed from Common Outstanding Tasks to DHCP Outstanding Tasks

comment:6 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.