-
Notifications
You must be signed in to change notification settings - Fork 46
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
Restart #68
base: master
Are you sure you want to change the base?
Restart #68
Conversation
It may take a while for me to merge this in. I need to make sure Luke is On Wed, Nov 6, 2013 at 5:45 PM, Mimmo Cosenza notifications@git.luolix.topwrote:
|
Sure, no problem. Just a suggestion. By introducing the edge cases, you are really thinking about the domain and the co-domain of a function (we love functional programming). I strongly suggest to take a look at the edge cases. At the moment I implemented the expected result of each tested function to be the one implemented in domina, but there are cases in which (like we discovered in enfocus) IMHO that results are wrong and we should fix the code consequently. The implemented edge cases (at the moment only for few functions) are in the following:
Cheers |
On Nov 7, 2013, at 1:45 AM, Creighton Kirkendall notifications@github.com wrote:
|
hi,
here is a pull request which started porting domina test on clojurescript.test as we did in enfocus.
At the moment I did not add the piggieback and the ring/compojure stuff, because I'll add autin later (it's much easier to setup).
I did not touch the original code (aside from a very little minutiae), but I think we should think better about the expected result from the edge case. I set the edge tests in such a way that all of them pass against the current code, but there few place where my personal opinion is that we should fix the code. But is something we can do later, when we would have ported all the old tests.
LMK what you think about it. At the moment we can stay with the 1.0.3-SNAPSHOT, because the codebase is not changed.
To test the pull request:
lein compile, test
All the 28 test/138 assertion passed with any optimisation level, but the none (which I do not specify as a test-command).
To run a single test-command (e.g. whitespace)
lein cljsbuild test whitespace
that's all
HIH