fission-workflows icon indicating copy to clipboard operation
fission-workflows copied to clipboard

Add test suite for Fission development workflow to e2e tests

Open erwinvaneyk opened this issue 6 years ago • 0 comments

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:
    • [ ] src/deploy/code (#241)
    • [ ] entrypoint
    • [ ] buildcmd
  • [x] 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
    • [x] body (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
    • [x] headers (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
    • [x] body (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
    • [x] query (fission/fission-workflows/test/e2e/tests/test_fission_python.sh)
  • [ ] fission function get
  • [ ] fission spec apply
  • [ ] fission spec destroy

erwinvaneyk avatar Feb 05 '19 14:02 erwinvaneyk