Right now we can do .to.contain() to for example make sure an element has a certain class in it. I think we also need the same for the opposite to be able to make sure an element does not contain a certain class.
My suggested API for this would be .to.not.contain() falling inline with how Chai does it. I have working code for this locally but just want to verify that the API is good with other people and we don't want something like to.notContain() or something like that before I submit the pull request and merge.
@asciidisco / @rodneyrehm , what you you guys think of the API to.not.contain()?
Right now we can do
.to.contain()
to for example make sure an element has a certain class in it. I think we also need the same for the opposite to be able to make sure an element does not contain a certain class.My suggested API for this would be
.to.not.contain()
falling inline with how Chai does it. I have working code for this locally but just want to verify that the API is good with other people and we don't want something liketo.notContain()
or something like that before I submit the pull request and merge.@asciidisco / @rodneyrehm , what you you guys think of the API
to.not.contain()
?