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
When testing modules and new features in a test cluster there can be some drawbacks in testing the functionality, this can limit testing and can take a lot more time as we need to find or create an application to fulfil our needs. Have seen this kinder problem during the testing of Keda where testing the scalers is a challenge due to not having an application to push load to for scaling
Approach
We should look to create a repository that contains test applications for our modules that can be spun up in test clusters that will give use the ability to test the features to modules when needed
A starting point would be to create an application that takes advantage of SQS which would give us the ability to test event-driven scaling within Keda
Is the plan to have one application that utilises all our modules or a set of application for each module. Could this utilise something like feature flags for each module?
Background
When testing modules and new features in a test cluster there can be some drawbacks in testing the functionality, this can limit testing and can take a lot more time as we need to find or create an application to fulfil our needs. Have seen this kinder problem during the testing of Keda where testing the scalers is a challenge due to not having an application to push load to for scaling
Approach
We should look to create a repository that contains test applications for our modules that can be spun up in test clusters that will give use the ability to test the features to modules when needed
A starting point would be to create an application that takes advantage of SQS which would give us the ability to test event-driven scaling within Keda
Definition of done
Reference
How to write good user stories
The text was updated successfully, but these errors were encountered: