Implement unit testing

[nicolassaw]

Problem There is no quick way to test specific pieces of the code without running the code from the beginning and creating test data (ie. HTML and json files) to work with. Unit tests would provide built-in ways to do so.

Goal Add unit testing to the code (python documentation). Ensure that your test HTML or json files are redacted and do not store real person data. Store any test files in the resources folder.

[nicolassaw]

Design unit tests for these modules:

• [ ] scraper: complete (for searching one specific cause number)
• [ ] parser: complete (for parsing one specific cause number)
• [ ] cleaner: in progress
• [ ] updater: in progress
• [ ] orchestrater: in progress

Next step ideas for unit testing:

• [ ] For tests that people run before merging new versions: Come up with test that runs based on a specific known day and judicial officer.
• [ ] For tests that run before weekly live running: Test based on the past week of live data.
• [ ] Create unit tests for cleaner that considers structure of final visualizations

[nicolassaw]

We are rethinking how we're doing unit tests and are making them more modular. This means that this is blocked by #93 in so far as each of the functions needs to be built out for each major module in order to write the unit tests for each of the functions. But not all of the modules need to be written to begin unit testing on any individually, just the one being tested.

In this pull request, the scraper has been rewritten to have modules and many of the scraper unit tests have been written, but not all of them. Those last scraper unit tests can be written.

But writing unit tests for parser, cleaner, and updater is blocked by that module being rewritten in #93.