QUnit now have the "same" assertion that makes compare, compare2, isSet and isObject...and in my opinion equals too, deprecated.
The problem with all those deprecated assertion its that it doesn't deal well with unexpected input. You can discuss about same and the function behind (equiv) on http://philrathe.com/articles/equiv that site --Philippe Klaus Hartl-4 wrote: > > > All, > > I was wondering if it makes sense to extend QUnits equals method so > that it returns true if I compare two objects (or arrays)? > > Background: I'm currently writing unit test for tabs, precisely I'm > testing the default values where there are two options that have an > empty object respectively array as default value. > > I could also roll my own equality check or think about using other > values as default values. > > Any suggestions? > > > --Klaus > > > > -- View this message in context: http://www.nabble.com/Extending-QUnit%27s-equals%28%29-to-check-equality-of-objects--tp19775985s27240p20281860.html Sent from the jQuery Dev List mailing list archive at Nabble.com. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
