-
Notifications
You must be signed in to change notification settings - Fork 35
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
Find right place for integration tests #310
Comments
@dymurray @djzager The integration art of tests (with expected contribution from QE) should be moved from the Hub repo. Would you prefer something else than https://github.com/konveyor/go-konveyor-tests? |
@aufi I think go-konveyor-tests seems like the most appropriate place to me. Any objections? |
why don't they live with the component being tested? |
Looking at the comment that precipitated this issue, talking about the windup addon test not belonging in the hub. I believe the right answer is for the windup analysis integration test to live in the tackle2-addon-windup repo. |
I'm for go-konveyor-tests repo too. Reasons for separate repo (from my point of view)
|
Am I missing something? The only test I see in the integration directory is a rewrite of the e2e test from the windup repo that was written in bash, now written in go...that we want to put into a 3rd repo. |
That fits to my understanding, yes. The only existing rewritten test demonstrates that the integration works, but we're choosing a place for creating the test suite based on similar code as the existing test. |
Integration E2E tests using API are now in https://github.com/konveyor/go-konveyor-tests those are executed using global CI workflows. Related to: - konveyor#310 - konveyor#418 Signed-off-by: Marek Aufart <maufart@redhat.com>
Integration E2E tests using API are now in https://github.com/konveyor/go-konveyor-tests those are executed using global CI workflows. Related to: - #310 - #418 Signed-off-by: Marek Aufart <maufart@redhat.com>
Analysis integration tests are continued in https://github.com/konveyor/go-konveyor-tests repository. |
There is a
test/integration
directory with tests working with multiple Konveyor components using the Hub API.There might be some part of integration tests relevant for the Hub, but majority of such tests is more or less Konveyor application-level E2E testing that should likely be in a separate repository. The exact place is to be discussed&agreed.
Related resources:
The text was updated successfully, but these errors were encountered: