Sep 4, 2018 · 1 min read
Hi, thanks a lot for your compliments, personally I can recommend using unit tests as long as they’re the simplest one to write and you can easily track the coverage of the repo and connect some CI to it to run all of the use cases.
The simple example of test is unit test for description extracting, which is receiving the text of the site as the input and then asserting that the outputted description is equal to the one, which is pre-defined in the test.
If assertion doesn’t fail, then the test have been passed.
Hope, I’ve managed to help you :)
