Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write smoke testing ADR #17

Open
jisantuc opened this issue Oct 3, 2019 · 0 comments
Open

Write smoke testing ADR #17

jisantuc opened this issue Oct 3, 2019 · 0 comments
Labels

Comments

@jisantuc
Copy link
Contributor

jisantuc commented Oct 3, 2019

Per the application setup ADR,

  • Continuous integration checks passing on a PR must mean that the branch is safe to deploy. This will require more care around migrations than usual and a more thorough exercise of the application in tests than we have in Raster Foundry. As long as this repository is just an API, that probably means generative testing of workflows modeled through API interaction both for correctness and performance regressions. I believe that we already have the tools and expertise on the team to do this.
  • The application should also include smoke tests. Smoke tests will be a new feature of CI for us. We should be able to rely on the small application scope to ensure that we can define a reasonable standard for "not on fire."

We have a pretty good sense of how to do the first part (scalacheck + http4s testing, woohoo). We don't have a good idea of how to do the second one. Figure out how to run smoke tests in CI, and write an ADR about it.

@jisantuc jisantuc changed the title Write testing ADR Write smoke testing ADR Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants