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

Add test suite for Fission development workflow to e2e tests #242

Open
5 of 20 tasks
erwinvaneyk opened this issue Feb 5, 2019 · 0 comments
Open
5 of 20 tasks

Add test suite for Fission development workflow to e2e tests #242

erwinvaneyk opened this issue Feb 5, 2019 · 0 comments

Comments

@erwinvaneyk
Copy link
Member

Expanding upon #239: the current e2e test suite only uses the minimal functions to deploy and execute Fission functions; many features are not explicitly covered by the tests

To ensure that we do not break the dev workflow (either due to changes in Fission or Workflows) we need to at least cover the following:

  • fission function update:
  • fission function delete (though not explicitly tested)
  • fission function create is not tested for all parameters:
    • configmap
    • secret
    • entrypoint
    • buildcmd
  • fission function logs
  • fission function test (not explicitly tested)
    • all methods
    • body (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
    • headers (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
    • body (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
    • query (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
  • fission function get
  • fission spec apply
  • fission spec destroy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant