-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Integration test suite and components testing #312
Comments
Hello @savitharaghunathan @aufi and @djzager I'm Mohd Aquib and I'm really excited about participating in the LFX mentorship program from June to August. I've been learning and working with Go for some time now and also have Basic software development skills (eg: CLI, GIT, etc) and would love to contribute to this project. Can you please suggest some resources and IRC channels that I can refer to? Your help would be greatly appreciated. |
@savitharaghunathan @aufi @djzager I am Amit Kumar, and I am currently volunteering for the Cluster API v1.5 release team. I have also contributed as the release lead shadow for CAPI v1.4 release team in the past. Moreover, I was a GSoC 2022 student for AOSSIE. I am writing to express my interest in applying for the upcoming LFX mentorship program. I have reviewed the proposal idea and would like to apply for it. However, I would appreciate it if you could inform me of any prerequisites for the proposal. I want to complete all the prerequisites before the mentoring session starts. Thank you for your time and consideration. I look forward to hearing from you. Best regards, |
@savitharaghunathan I'm concerned that having this issue in the hub will invite application level (integration) tests being contributed here. If the intent is to invite contributions to the API tests, then please clarify in the description. |
@jortel Thank you for bringing it up. |
The issue description says about the open testing work following:
That looks pretty open at this moment to me, if we really don't want have the issue in the Hub repo, operator or community repos might be suitable too for an "umrella" issue that might link issues from other repos with more specific tests parts. On integration tests, the right repo is TBD #310. We have a playground with go-based tests which is https://github.com/konveyor/go-konveyor-tests that is expected to focus on integration/application level tests, but its future is up for discussion with Dylan and others. |
Closed in favor of konveyor/operator#220 |
This issue has been moved. Please refer - konveyor/operator#220
The text was updated successfully, but these errors were encountered: