[DRAFT] End-to-end test service starting point #74
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR could be kept a draft, or we could decide we want to bring the code in and iterate.
Unit tests are important in many ways, but I'd trade code coverage on things that don't matter for good end-to-end tests every day of the week. Put another way: I think unit tests matter on core operations: algorithmic transforms, logic, storage operations, etc., but there are other places where an end-to-end test, demonstrating the application logic, matter more to me (personally).
My personal vision (to be discussed) is that we have a way of running end-to-end tests on a daily basis. I would like to see:
This
e2e
service may, or may not, be part of that. It provides a small service that serves static webpages. I pulled one page from NASA, and one from the FAC. Over time, we might pull more. I also excepted the domaine2e.gov
(which perhaps should change) from various rules, so that we can set up a fake domain resolution and crawl this as if it were any other site (including locally). This way, we can run the tests in the local docker stack.More thought will need to be given, however. Ideally, we would run against a
staging
deployment. This would serve for that, too, but may require more thought/development.As stated... perhaps we keep this in draft, or perhaps we pull this in to the stack and play with it further.