Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Implement 404 testing strategy #245

Closed
techtonik opened this issue Jun 10, 2015 · 3 comments
Closed

Implement 404 testing strategy #245

techtonik opened this issue Jun 10, 2015 · 3 comments

Comments

@techtonik
Copy link
Contributor

How do we do 404 testing? It looks like we don't have automation to back this up and run at least monthly.

(if we do have this strategy, this should be put into some entrypoint Maintenance Quests document)

@techtonik
Copy link
Contributor Author

Features creeping:

  • stats on redirects from old moved pages (needed for fixing old links on the internets and to estimate if the redirect endpoint should be preserved)

@chadwhitacre
Copy link
Contributor

We check for 404s in TestPages.browse, but I don't believe we do any external link checking.

@chadwhitacre
Copy link
Contributor

You want 404 checking on Inside Gratipay, right?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants