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
cats-tests remains unpublished and undocumented (#152). This is a stumbling block for new contributors and for people like @djspiewak and myself who find ourselves writing add-on libraries for cats and are unable to write tests in a style consistent with the tests in cats.
cats-tests has never been published according to Git blame, even in the cats artifact, contrary to statements in #1184.
we need to consolidate all the packaging related issues. I think @BennyHill summarize the situation (questions to answer) pretty well in this comment
I totally agree that we need better documentation on how to write law tests in cats style. However, as I found out in mainecoon, you probably don't need the majority of the test utils in cats.tests. I just needed to copy one class declaration from cats.tests to be able to write tests consistent to cats, examples. The majority of the test machinery is in the discipline package in the laws module. I kind of feel that the discipline is good enough as a test-kits for cats.
P.S. alleycats also has tests consistent to cats, it just needed to copy this file out.
Activity
kailuowang commentedon May 10, 2017
My 2 cents:
cats.tests. I just needed to copy one class declaration fromcats.teststo be able to write tests consistent to cats, examples. The majority of the test machinery is in thedisciplinepackage in thelawsmodule. I kind of feel that thedisciplineis good enough as atest-kitsfor cats.P.S. alleycats also has tests consistent to cats, it just needed to copy this file out.
ceedubs commentedon Sep 21, 2017
@kailuowang was this resolved by #1758?
kailuowang commentedon Sep 21, 2017
yes, closing.