[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Issue 232]: Incorrect RFC2119 language in CCA Test assertions
http://osoa.org/jira/browse/JAVA-232 On 3/7/2011 11:08 AM, Bryan Aupperle wrote: > Target: CAA Test-Assertions CD01-Rev1 > > Description: Use of must, may MUST, MAY and SHOULD outside of normative > statements Specifically: > Lines 39-40: The prerequisites *may* be defined in terms of one or more > other test assertions that *must* be true. > Line 41: The meat of the assertion - something that *should evaluate* to > true or false for the given target. (We missed this in the POJO > document) > Lines 42-43: Mandatory (for *MUST* requirements) or Preferred (for > *SHOULD* requirements) or Permitted (for *MAY* requirements). > Lines 44-45: Zero or more labels *that may* be attached to this test > assertion - these tags can be used to group sets of assertions. > > Also missing reference on line 23. > > Proposal: Change to: > Lines 39-40: The prerequisites *can* be defined in terms of one or more > other test assertions that *have to* be true. > Line 41: The meat of the assertion - something that *evaluates* to true > or false for the given target. (Also fix in the POJO document) > Lines 42-43: Mandatory (for *"MUST"* requirements) or Preferred (for > *"SHOULD"* requirements) or Permitted (for *"MAY"* requirements). > Lines 44-45: Zero or more labels *to be* attached to this test assertion > - these tags can be used to group sets of assertions. > > Add a [JAVACAA] to line 23 >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]