Go through the unit tests and make sure they all test something. Scale the really complex ones down.

cmu-phil / tetrad

Repository for the Tetrad Project, www.phil.cmu.edu/tetrad.

GNU General Public License v2.0

408 stars 111 forks source link

Go through the unit tests and make sure they all test something. Scale the really complex ones down. #57

Closed jdramsey closed 8 years ago

jdramsey commented 9 years ago

Kong went through these and found cases where exceptions were being thrown; these have been fixed. I went through the ones in tetrad-lib and found the most egregious time-wasters and scaled these down. Still though the tests do not run quickly. Also, still need to go through and make sure stuff gets tested instead of just printed where possible.

jdramsey commented 8 years ago

Did quite a bit of this, good enough for now. Most of the unit tests test something or other. None of them produce errors. I think we will just have to be more vigilant going forward.