Closed
Bug 666008
Opened 14 years ago
Closed 14 years ago
Deprecate or remove controller.assertX functions
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: harth, Assigned: harth)
References
Details
(Whiteboard: [mozmill-2.0+])
Attachments
(1 file)
From bug 650963, we should deprecate or remove all the controller.assertBlahBlahBlah() functions in favor of the assert and expect modules.
Assignee | ||
Comment 1•14 years ago
|
||
This deprecates them. The only problem with this is you don't see the warnings unless you do --console-level=DEBUG.
Assignee: nobody → fayearthur+bugs
Attachment #540859 -
Flags: review?(ctalbert)
Assignee | ||
Updated•14 years ago
|
Summary: Deprecate or remote controller.assertX functions → Deprecate or remove controller.assertX functions
Comment on attachment 540859 [details]
Deprecate controller.assertX() methods
Nit: Calling the function logDeprecated makes it sound like a general deprecation utility, so either parameterize it with a message param so that it is a generic deprecation logging utilty or call it logDeprecatedAssert so that it's clear this is a one-time use thing.
I tend to prefer the general approach where it takes the API name and the message as parameters and prints the same standardized message that you have there, just by using the passed in message and funcname parameters. Make sense?
Attachment #540859 -
Flags: review?(ctalbert) → review+
Assignee | ||
Comment 3•14 years ago
|
||
comments addressed, thanks clint, master:
https://github.com/mozautomation/mozmill/commit/0173de6c6a8198b1b3c4090bb30a18cfdc75781e
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•