You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking on e2e tests and how they are organized. Should we create more folders than scalers to split the tests by funcionality?
I said because for instance, hashicorp vault e2e test is using postgres, but the important thing of that test is not postgres scaler at all, and the same with aad-pod-identity/workload-federation, or for the HPA pause and custom names. Maybe we could split e2e test in different folders based on the thing that are testing, of course for testing Vault we need an scaler, but doesn't matter which scaler.
My proposal for the moment is having 3 folders:
Scalers: For scaler stuffs
Secret-providers: For e2e test about all the things related with secrets
Internals: For e2e test about internal mechanism, like hpa pause, hpa custom name, etc
The text was updated successfully, but these errors were encountered:
Proposal
I'm thinking on e2e tests and how they are organized. Should we create more folders than scalers to split the tests by funcionality?
I said because for instance, hashicorp vault e2e test is using postgres, but the important thing of that test is not postgres scaler at all, and the same with aad-pod-identity/workload-federation, or for the HPA pause and custom names. Maybe we could split e2e test in different folders based on the thing that are testing, of course for testing Vault we need an scaler, but doesn't matter which scaler.
My proposal for the moment is having 3 folders:
The text was updated successfully, but these errors were encountered: