I see your point, i"ll make some test cases to check the effects. 

Viele Grüße
Alexei Vinogradov 
--
Sent from mobile phone

> Am 06.04.2014 um 15:15 schrieb Andrei Rusu <notifications@github.com>:
> 
> In lib/selenium/assertions/attributeNotEquals.js:
> 
> > + */
> > +
> > +var util = require('util');
> > +exports.assertion = function(selector, attribute, expected, msg) {
> > +
> > +  var MSG_ELEMENT_NOT_FOUND = 'Testing if element <%s> has attribute: %s !="%s". ' +
> > +    'Element could not be located.';
> > +
> > +  this.message = msg || util.format('Testing if element <%s> has no attribute: %s = "%s".', selector, attribute, expected);
> > +
> > +  this.expected = function() {
> > +    return 'not ' + expected;
> > +  };
> > +
> > +  this.pass = function(value) {
> > +    return value != expected;
> I am aware of that. However 0 == '' (0 equals an empty string), for instance, and not enforcing strict comparison might produce undesired effects. I am not in favour of the non strict comparison and all the other assertions use the strict operator.
> 
> —
> Reply to this email directly or view it on GitHub.