Add pytest unit tests to `data_builder` about police-brutality HOT 6 CLOSED

@ShaynaCummings this looks good to me. If you're available for more test ideas, here are some that would rely on running process_md_texts:

• No empty links fields.
• No empty state fields.
• No empty name fields.
• More than 200 records found.

That branch looks ready for a PR...

from police-brutality.

This sounds like a great idea - tagging @samgoldman and @ubershmekel for input.

from police-brutality.

Super! This is the kind of thing I was thinking:
master...ShaynaCummings:add-tests

from police-brutality.

I've only contributed a small amount to the script, but I always think testing is a great idea. Let me know if you want me to do anything.

from police-brutality.

@ubershmekel still working on a few more of these cases, but I was wondering if there are future plans for handling invalid or non-parsable entries beyond writing to stdout? I put some specific examples as failing or unfinished tests in the draft PR if you want to take a look.

from police-brutality.

@ShaynaCummings if you prefer - you can just commit the tests and I'll hook them up to the github action, or you can cover that in your PR as well.

https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions

To test the action, fork the repo, author your new test action, make a PR to your fork, and check if the tests pass or don't based on what's in the PR. The PR should show a nice big red X or green circle I think if everything got glued. There might even be a way to output exactly which tests failed on which data points.

from police-brutality.