-
-
Notifications
You must be signed in to change notification settings - Fork 646
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
Assertions are referred to as tests in cider-test #1627
Comments
And, of course, when running just a single test with
|
No good reason. :-) I agree with you that "assertion" would be better here. Names are always a pain. |
True that. I'll have to check if the middleware keeps track of both the number of tests and the number of assertions that were executed. |
It does. What you're calling a |
Got it. That definitely makes sense and I don't might referring those as we do internally, but in the UI we should probably follow in lein's footsteps in terms of terminology. |
Indeed. I believe boot also follows the same terminology. |
I've noticed that in our messages we never use the term
assertion
, which is what lein uses extensively. I mean tests are composed of assertions:This is one test with 5 assertions (
is
) in it. However, our message right now is:It should be
@jeffvalk Was there a particular reason you avoided the term
assertion
?The text was updated successfully, but these errors were encountered: