System tests for alpha

[andymeneely]

Motivation

We want to be able to have good confidence that the system is "ready" to merge into production, so this is intended to be a last-minute run through the whole site to make sure things work the way we think.

No flakey tests

We don't want to be overly flakey with our tests. The site will evolve, so we want to make these tests as future-proof as we can. That means the assertions don't need to be massive strings which will change as soon as we edit something - instead, try to aim for assertions that simulate what you would look for if you're testing this manually.

Tasks

Our routes file turned into sub-tasks. Many of these might be done already. Check them off as you complete them.

• [x] /vulnerabilities
• [x] /vulnerabilities/:id
• [x] /:id
• [x] /developers
• [x] /developers/:id
• [x] /commits
• [x] /commits/:id
• [x] /tags
• [x] /tags/:id
• [x] /articles
• [x] /articles/:id
• [x] /projects
• [x] /filepaths
• [x] /filepaths/:filepath_id
• [x] /curate
• [x] /about
• [ ] /sitemap
• [x] /version
• [x] /news
• [x] /status
• [x] /curationwizard
• [x] /api

Issue Chores

• [x] I have checked the VHP backlog for something similar: https://github.com/VulnerabilityHistoryProject/vulnerability-history/issues
• [x] I have checked if this should also be part of a Github Project: https://github.com/VulnerabilityHistoryProject/vulnerability-history/projects?type=beta
• [x] I have checked that this might need dev infrastructure or refactor labels

[PopPaolo]

The /sitemap endpoint is not active