Figure out a way to run preflight tests against a remote system. The goal of these remote preflight checks is to ensure that a remote system is performing as expected after deployment. For example, say we deploy a new release to production. How can we verify that production is acting the way it is supposed to even if the deployment "succeeded"? This is where the remote preflight tests come in. These preflight tests are limited to the hono backend only.
The preflight tests themselves will be written in 3 user stories that are linked in seperate issues (#61, #62, #63, #65). This issue blocks the completion of those issues (for now) since there is a chance the way unit tests are written will change.
A good implementation of this issue will:
[ ] Add a Github Workflow job (hono_integration) that is triggered after a deployment to a staging env succeeds, runs preflight on this remote instance
[ ] Add a Github Workflow job (deploy_production) that is triggered after a deployment to a production env succeeds, runs preflight on this remote instance
[ ] Figure out how to have jest unit tests hit a remote url / instance
[ ] Figure out how to hit remote urls from a Github Actions runner (might block outbound traffic by default)
Description
Figure out a way to run preflight tests against a remote system. The goal of these remote preflight checks is to ensure that a remote system is performing as expected after deployment. For example, say we deploy a new release to production. How can we verify that production is acting the way it is supposed to even if the deployment "succeeded"? This is where the remote preflight tests come in. These preflight tests are limited to the hono backend only.
The preflight tests themselves will be written in 3 user stories that are linked in seperate issues (#61, #62, #63, #65). This issue blocks the completion of those issues (for now) since there is a chance the way unit tests are written will change.
A good implementation of this issue will:
Acceptance Criteria