This adds a regression test for #61, which I (re)broke with some recent refactoring. These tests will check to make sure that the routes produce the expected page, as judged by the value of the <h1> element on each of the pages. If we update the wording, we'll have to update these tests to match.
They will run on every push to main as part of the integration tests.
While I was fixing this, the About page was failing, due to it using multiple <h1> elements (only 1 per page is allowed in HTML5). I've switched to an <h2> for the second, and reformatted the code at the same time, removing some unnecessary imports.
mekkim
commented
2 years ago
This adds a regression test for #61, which I (re)broke with some recent refactoring. These tests will check to make sure that the routes produce the expected page, as judged by the value of the
<h1>element on each of the pages. If we update the wording, we'll have to update these tests to match.They will run on every push to
mainas part of the integration tests.While I was fixing this, the About page was failing, due to it using multiple
<h1>elements (only 1 per page is allowed in HTML5). I've switched to an<h2>for the second, and reformatted the code at the same time, removing some unnecessary imports.