Research and implement testing strategy
After prototype is working, a testing strategy needs to be designed. Some research needs to be done on what are the important criteria of the feature (e.g., performance, scalability, functional requirements etc.) and decide on how to test it.
This involves both research (with a deliverable) and practical implementation.
Initial ideas for the test approach:
- 10 second dance, our first app that ever needed a custom container, let's revive it and make sure it works on your new system as well. especially focus on the code changes needed for it in the repo to reflect on how we define this companion container in low code sources/configuration
- use a container from Alex that he creates as part of his AI block and self hosting a model. It's big and really an example of what'll be using a lot in the future. this might also show we need a way to use 'shared' containers. Not sure if it's always a good idea to duplicate them per app. depends on how efficient they're run on the cluster.
- create a container that's deliberately messing up. just run a while: true and see if the system rate limits the container and after continued abuse of 100% cpu, kill it and let the app owner know that the container was not behaving in an acceptible way
Edited by Ivan Koitchev