Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract normative assertions for testing #117

Closed
mmccool opened this issue May 17, 2018 · 2 comments
Closed

Extract normative assertions for testing #117

mmccool opened this issue May 17, 2018 · 2 comments
Labels
for next iteration Planned or postponed topics for the future

Comments

@mmccool
Copy link
Contributor

mmccool commented May 17, 2018

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.

@zolkis
Copy link
Contributor

zolkis commented Sep 24, 2018

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.

@danielpeintner danielpeintner added the for next iteration Planned or postponed topics for the future label Sep 2, 2019
@danielpeintner
Copy link
Contributor

Close in favor of #190

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for next iteration Planned or postponed topics for the future
Projects
None yet
Development

No branches or pull requests

3 participants