| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files @@ Coverage Diff @@
## main #220 +/- ##
==========================================
+ Coverage 97.36% 97.44% +0.08%
==========================================
Files 20 20
Lines 947 978 +31
==========================================
+ Hits 922 953 +31
Misses 25 25
|
Sorry, something went wrong.
|
@Sparks29032 I am afraid this one has a conflict. |
Sorry, something went wrong.
Ah, probably from me fixing a typo on another PR. Should be resolved now. |
Sorry, something went wrong.
| [ | ||
| "--smear", | ||
| "100", | ||
| "--smear-pdf", |
There was a problem hiding this comment.
This code block also tests the default behavior if a user inputs both morphs. The pdf smear takes precedence.
Sorry, something went wrong.
|
I am merging this. I had one comment which is to please make all new tests as pytest tests, not unittest tests. We would gradually over time like to migrate back to pytest tests entirely, but at least, let's not make new unittest tests. |
Sorry, something went wrong.
|
Thanks for merging! I thought these tests were already migrated from unittest to Pytest in #83. These tests seem to follow the Pytest documentation. |
Sorry, something went wrong.
maybe I didn't check well enough. It looked as if it was indented and part of a class and not a standalone function. |
Sorry, something went wrong.
|
They are classes, but I thought this is supported and encouraged by https://docs.pytest.org/en/stable/getting-started.html. I think I need the python tests presentation lol. |
Sorry, something went wrong.
Ah, I see. I don't really see any benefit unless tests are sharing a bunch of code or marks, but mostly I just assumed they were unittest tests (which are typically the only tests we write in classes.....) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Closes #210.
The --smear-pdf option first converts the PDF to an RDF before applying the smear. The --smear option does not do such transformation. If both are enabled, the --smear-pdf option takes precedence.