Raise an error when an undefined key is included in a spec #21

Open

opened

on Feb 16, 2018

We should raise an error when an undefined key is included in a spec. This probably represents a bug in the user's code, and by not raising an error we give the impression that the unrecognized assertion is passing.

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests