Dramatically improve test coverage

Question

Dramatically improve test coverage

castle-lemongrab opened this issue 4 years ago · comments

This codebase currently has no tests. A castle with no unit tests, integration tests, or functional tests is in... unacceptable condition. Split the main client out into separate files, pick a testing framework, and at least get some basic unit tests added, with coverage metrics (N.B. should probably just use nyc and istanbul here).

Castle Lemongrab · Answer 1 · Tue Jun 30 2020 09:09:21 GMT+0800 (China Standard Time)

Note that Parler's API may change substantially in the near-term, so I'm marking this low priority. No sense in writing unit tests that'll be quickly and externally deprecated.

Castle Lemongrab · Answer 2 · Wed Jul 29 2020 10:05:39 GMT+0800 (China Standard Time)

Progress has been made on this in 0f68e58. Currently using mocha and chai. Test coverage yet to be added.

Castle Lemongrab · Answer 3 · Mon Nov 16 2020 03:38:20 GMT+0800 (China Standard Time)

Issue #36 points out the need to increase priority here. In addition to adding coverage data (probably via nyc), I'll merge in some testing support code from another project so that we can test the CLI commands directly in addition to unit testing at the class/function level.