You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussion with @travs:
In some cases, we have a single test that verifies an entire class of behavior. For example, in the evidence quality tests that we just added, we verify wholesale that every fact has a doi or url. This means that in the event that there is a failure, the user will have to interactively determine where exactly the failure is- the test won't reveal that information.
We should review all of the tests at some point and make sure they are appropriately granular for the sake of making debugging easier. One way to do this would be to use generating tests:
Discussion with @travs:
In some cases, we have a single test that verifies an entire class of behavior. For example, in the evidence quality tests that we just added, we verify wholesale that every fact has a doi or url. This means that in the event that there is a failure, the user will have to interactively determine where exactly the failure is- the test won't reveal that information.
We should review all of the tests at some point and make sure they are appropriately granular for the sake of making debugging easier. One way to do this would be to use generating tests:
http://nose.readthedocs.org/en/latest/writing_tests.html#test-generators
The text was updated successfully, but these errors were encountered: