Replies: 3 comments
-
There are 2 different provisiongs for TEST and PROD:
The e2e-tests are currently associated with the test provisioning. This is why an error occurs when setting the Environment to PROD (#151). For me, it makes no sense to make all tests standalone because we need pre-set data in the UI. |
Beta Was this translation helpful? Give feedback.
-
Why we need pre-set data? The e2e-tests could generate this data and ensure the data is there before running each test. |
Beta Was this translation helpful? Give feedback.
-
That is an option, but one disadvantage is the speed, the e2e-tests will need more time if it has to create the data itself. |
Beta Was this translation helpful? Give feedback.
-
Currently the e2e tests are tightly coupled with provisioned data and some values (e.g. root-secret) are hardcoded. The e2e-tests should be running without any provisioning and should be "rerun"- able.
Tasks todo:
Beta Was this translation helpful? Give feedback.
All reactions