The purpose of this issue is to open a discussion around e2e testing.
Currently, the charts use inline text to generate Kubernetes manifest for testing. This does not lend well for using formatters and linters while creating and maintaining the tests. Instead, we should move to static files. These can be in the following structure:
-- tests
---- external-scaler-azure-cosmos-db
------ example.yaml
---- http-add-on
------ example.yaml
---- keda
------ example.yaml
Later, we can use these static files along with a framework like Chainsaw .
The ultimate goal is to use a framework. However, we should move there incrementally so that code can be properly and easily reviewed.
If we decide to move forward with this approach, I am willing to drive this initiative.
cc @JorTurFer
The purpose of this issue is to open a discussion around e2e testing.
Currently, the charts use inline text to generate Kubernetes manifest for testing. This does not lend well for using formatters and linters while creating and maintaining the tests. Instead, we should move to static files. These can be in the following structure:
Later, we can use these static files along with a framework like Chainsaw .
The ultimate goal is to use a framework. However, we should move there incrementally so that code can be properly and easily reviewed.
If we decide to move forward with this approach, I am willing to drive this initiative.
cc @JorTurFer