-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Unit test suite for InlineColorEditor #2092
Comments
Comment by njx Oops, not quite ready yet...forgot to add the unit tests for the text field. |
Comment by njx OK, should be ready for review now. |
Comment by jasonsanjose Reviewing |
Comment by jasonsanjose Nicely done, especially without firing up a new window. I guess this stuff doesn't rely on ProjectManager, so that's a bonus. Initial review complete. |
Comment by njx Changes pushed. I also added JSDoc comments to all the helper functions, since some of their args were just non-obvious enough to require some explanation. |
Comment by njx Just added one last little refactoring cleanup I noticed. |
Comment by jasonsanjose Looks good. Merging. |
Issue by njx
Wednesday Nov 21, 2012 at 07:17 GMT
Originally opened as adobe/brackets#2174
@
jasonsanjoseA few of these unit tests got checked in as part of an earlier pull request (and were reviewed by Peter F), but some of those got modified in this pull anyway, so it's probably worth just reviewing everything from scratch.
Note that these are all mocked tests in one form or another--the first set use a full InlineColorEditor and a mock editor/document (so the InlineColorEditor doesn't actually live in the mock editor); the later ones just test ColorEditor by itself (not inside an InlineColorEditor).
Let me know if you think I should build some more integration-y tests as well. I think these tests give pretty good overall coverage though.
njx included the following code: https://github.com/adobe/brackets/pull/2174/commits
The text was updated successfully, but these errors were encountered: