-
Notifications
You must be signed in to change notification settings - Fork 11
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 tests #21
Comments
The unit tests are nowhere near complete so I will reopen this bug. |
nathan-osman
added a commit
that referenced
this issue
Sep 1, 2014
nathan-osman
added a commit
that referenced
this issue
Sep 1, 2014
nathan-osman
added a commit
that referenced
this issue
Sep 2, 2014
Another update (since I've been forgetting to reference this bug in commit messages): I just added tests for CMarkdown (our custom markdown extension). The following should be included in the test suite before this bug is closed:
These are the big ones that I can think of off the top of my head. I may think of others to add. |
nathan-osman
added a commit
that referenced
this issue
Feb 9, 2015
nathan-osman
added a commit
that referenced
this issue
Feb 9, 2015
nathan-osman
added a commit
that referenced
this issue
Feb 9, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ideally, we should have unit tests for as much of the code as possible to ensure new commits don't have unexpected side-effects. If set up correctly, we can use Travis CI to run the tests for pull requests.
The text was updated successfully, but these errors were encountered: