Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unit test testRefresh requires class names to be in a specific order #84

Open
backplane-import opened this issue Oct 16, 2011 · 3 comments

Comments

@backplane-import
Copy link

Imported from backplanejs Google Code issue 84.

Reporter fdintino
Date 27 Jul 2010 2:27:26 AM UTC

testRefresh was failing because the "enabled", "read-write", "optional", and "valid" class names were expected to be in a certain order, but they were not. Should instead test on whether these four class names appear, regardless of their order.


Owner set to fdintino

Priority: Medium
Type: Defect

@backplane-import
Copy link
Author

Comment by markbirbeck on 27 Jul 2010 2:34:22 AM UTC

Patch available at:

http://code.google.com/r/fdintino-backplanejs/source/detail?r=6fc885dd8a01f71db65831274e3a1a1297786ac2


Updates

Ticket status set to FixPending

@backplane-import
Copy link
Author

Comment by markbirbeck on 27 Jul 2010 2:35:05 AM UTC

Adding 'Module' and 'Component' labels.


Updates

Module: XForms
Component: Tools

@backplane-import
Copy link
Author

Comment by [email protected] on 28 Jul 2010 8:47:05 PM UTC

I didn't incorporate these fixes into 0.6.7 because testRefresh wasn't failing for me.

I can see that the fixes are ok, however I thought it best to see the failure first; how do I reproduce this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant