A change which rolls 'assertPropertyNotExist()' into 'assertNotProperty()' was just checked into Mozmill 1.4.2. testPrivateBrowsing/testDisabledElements.js was the only test that used this function. To fix: s/assertPropertyNotExist/assertNotProperty/ Note that the old function wasn't removed for 1.4.2, so tests that use it will still work, but will see a deprecation warning in the logs.

Aaron, could you update the test accordingly?

s/assertPropertyNotExist/assertNotProperty/

Comment on attachment 462378 [details] [diff] [review] Patch v1 - assertNotProperty Remind me to check this in once Mozmill 1.4.2 has been released.

As per the discussion in our weekly meeting this should be changed to either assertNotDOMProperty or assertNotJSProperty instead.

Aaron, can you please do that change and also create a new bug for moving all of our assertJS function calls which check attributes on nodes to assertNotJSProperty/assertJSProperty? Thanks.

s/assertNotProperty/assertNotDOMProperty I've never seen this function before so I'm assuming it's the same parameters and usage.

(In reply to comment #5) > Aaron, can you please do that change and also create a new bug for moving all > of our assertJS function calls which check attributes on nodes to > assertNotJSProperty/assertJSProperty? Thanks. Can you please explain what assertNotJSProperty is, and an example of where you are looking to use it.

Comment on attachment 463336 [details] [diff] [review] Patch - assertNotDOMProperty >- controller.assertPropertyNotExist(importHTML, "disabled"); >+ controller.assertNotDOMProperty(importHTML, "disabled"); assertProperty has been replaced by assertJSProperty which directly checks for the property of the given JS object. AssertDOMProperty will check the DOM attribute instead. That said the above code should use assertNotJSProperty.

Hopefully I got this right. Apologize, was confused with the name changes and adjusting to the different names, it wasn't clear at first.

Fixed by bug 584575.

Move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.