Open eric978 opened 1 year ago
Hi @strawhatrag ! That'd be great! I assigned it to you. A place to start might be to grab a sandbox (assuming you need a larger environment to run a few clusters) and get familiar with how kubeslice works. Then I think it's a matter of diving in and adding some test cases (functional, config/unconfig, etc). Happy to throw out some suggestions when you're ready. (Apologies for bad cert on the sandbox url... must've expired... we're fixing it. ;-) )
@eric978 Let me work on this now
Hi @ashutosh887. Thanks for volunteering. I think you should be set... if I can help, let me know!
I'm not clear with the objective @eric978 Can you please help
What is this test/framework for? How is it different for unit and integration tests? Any references?
Hi Bhargav. For better or worse, there is a lot of freedom here. ;-) We currently don't have an automated test framework for an open source contributor to verify their changes prior to raising a PR for their change.
One thought for how to processed would be to create a github action that runs the example demo (https://github.com/kubeslice/examples/tree/master/kind) using private contributor-built artifacts.
But there is plenty of room for other ideas too. The goal is just to give a community contributor a way (or ways) to have reasonable confidence that their change is a good one.
I'm interested in contributing to the project. Who should I reach out to for information about how to get involved?