Improve HTML route & template test coverage #31
No reviewers
Labels
No Label
bug
documentation
duplicate
enhancement
help wanted
invalid
maintenance
peach-lib
peach-network
peach-oled
peach-stats
peach-web
question
refactor
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: PeachCloud/peach-workspace#31
Loading…
Reference in New Issue
No description provided.
Delete Branch "route_test_coverage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
context.back
andcontext.title
for thechange_password
route and templateLooks good to me. Thanks for fixing the change password title.
The tests that test .post routes passing arguments, and .get routes which make complicated calls to retrieve data, seem more valuable to me as tests, to ensure there are no regressions. The .get tests which just confirm the page renders for a particular route seem less valuable but if its just one test per route that seems pretty manageable.
Thanks for taking a look!
Agreed that we need more test coverage for GET and POST routes. I'd like to learn how to mock the backend data to make those tests as accurate as possible.
The HTML tests are great because they test routes and template rendering in one go. This is especially helpful for templates with more complex context logic; if we mess up a variable name or some tera operation the tests will alert us. I can remember testing by clicking through the whole interface manually in the early days of peach-web 😅 That was tedious.