codethesaur.us
codethesaur.us copied to clipboard
Add/fix unit test(s) to check HTTP status codes for invalid lookups
Description
Bug #690 resulted from a invalid language_name
/ friendly_language_name
mixup that would result in 500 server errors. The unit test that seem to check for invalid language/structures didn't catch this.
This issue should add new unit test(s) or fix the existing unit test(s) to make this more robust.
Requirements
- Unit tests that check behind the scenes if invalid languages are looked up should be added/fixed
- Unit tests that check HTTP status codes (404, 500, others if needed) should be added/fixed for invalid lookups
- Probably should also add/fix unit tests for other scenarios too (other pages don't exist, malformed URLs, etc.)
Additional Notes
This need to be tested locally to ensure they work:
-
python manage.py test
should run all unit tests -
python manage.py validatelanginfofiles
should run tests on the language files -
python manage.py validatemetainfofile
should run tests on the meta info file
While they'll be run when a pull request is made, making sure they run and pass locally first will speed things up.
Hi I would love to work on this issue :)
Hey @sharktankful, I missed your comment somehow. Feel free to take it!
And let me know if you need any help.
This issue has been inactive for 345 hours (14.38 days) and will be unassigned after 63 more hours (2.63 days). If you have questions, please leave a comment, message @codethesaurus or @geekygirlsarah on Twitter, or email [email protected].If you are still working on this issue, that's fine. Please comment here to tell the bot to give you more time.
This issue has been inactive for 417 hours (17.38 days) and is past the limit of 408 hours (17.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you for your interest in contributing to this project.