This repository has been archived by the owner on Jul 17, 2020. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 106
Writing tests #55
Labels
Comments
Anyone working on this right now?? Interested in writing test cases by myself |
Writing tests is quite a bit of work. Multiple people can do this since a lot of tests need to be written. |
@makkoli : how do we run the tests? |
All our scripts are in the package.json file. |
@makkoli what's the difference between .assert and .equal? ie.
|
@paulywill In tape, our testing suite, .assert() is an alias for .ok(), which will coerce a value to see if it's truthy, so you don't pass in a second value to compare against since it just checks if it coerces to true. The .equal() will check if the actual value returned === expected value you passed in. In this instance, the expected value data type you pass in can be a number, string, boolean, etc. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need tests to be written for server and client side.
There are example tests in
server/models/__tests__
andclient/reducers/__tests__
The text was updated successfully, but these errors were encountered: