You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For defining test cases we need to extract and name all the normative assertions.
I have automated this process but it requires following some conventions in the markup of normative assertions. I'll test the automation first in the TD spec and when it's reasonably stable can make a similar PR for the scripting API spec.
The text was updated successfully, but these errors were encountered:
I would argue that it's enough to use MAY, MUST, SHOULD, as ReSpec will handle them as normative assertions and every occurrence is as well defined as it would be by a special tag. There is no separate normative and non-normative use of MAY, MUST, SHOULD, etc. So let's keep the specs clean.
For defining test cases we need to extract and name all the normative assertions.
I have automated this process but it requires following some conventions in the markup of normative assertions. I'll test the automation first in the TD spec and when it's reasonably stable can make a similar PR for the scripting API spec.
The text was updated successfully, but these errors were encountered: