-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unittests for 404 html page #710
Conversation
b4cb047
to
80ecc77
Compare
Codecov Report
@@ Coverage Diff @@
## master #710 +/- ##
=======================================
Coverage 57.97% 57.97%
=======================================
Files 54 54
Lines 3569 3569
Branches 2007 2007
=======================================
Hits 2069 2069
Misses 1499 1499
Partials 1 1 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is the empty line revealed by code factor to remove but else we are good.
This test was introduced with the purpose of testing the error message in the 404 page returned by /random for a non-existent book. The actual expected output currently present in this new unit-test is too much for that purpose and may become a maintenance burden if more tests of that kind are added.
The `ServerTest.RandomOnNonExistentBook` unit test was replaced with a more general one testing multiple 404 scenarios where the content of the body is checked too.
80ecc77
to
34d069e
Compare
I've made it (and rebased on master) |
Should be merged after #709
This PR is part of a larger campaign of extending the kiwix-serve test-suite, so that major changes related to kiwix/kiwix-tools#59 and #650 can be implemented in a safer environment.