Skip to content
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

Closed
aufi opened this issue May 5, 2023 · 8 comments
Closed

Find right place for integration tests #310

aufi opened this issue May 5, 2023 · 8 comments
Assignees

Comments

@aufi
Copy link
Member

aufi commented May 5, 2023

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:

@aufi
Copy link
Member Author

aufi commented May 11, 2023

@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?

@dymurray
Copy link
Contributor

@aufi I think go-konveyor-tests seems like the most appropriate place to me. Any objections?

@djzager
Copy link
Member

djzager commented May 11, 2023

why don't they live with the component being tested?

@djzager
Copy link
Member

djzager commented May 11, 2023

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.

@aufi
Copy link
Member Author

aufi commented May 11, 2023

I'm for go-konveyor-tests repo too.

Reasons for separate repo (from my point of view)

  • it tests/will test multiple components (even analyze test works with Hub+windup addon)
  • it should be easier share the same test data for e.g. windup and lsp analyzer compatibility test
  • it should cover more application level tests that already exist in separate repos e.g. for UI or the python-api suite (bad example, but it exists)
  • and practical thing - QE should contribute to that repo, so have a separate one where they can merge tests each other without blocking/waiting for devs looks better for our future cooperation.

@djzager
Copy link
Member

djzager commented May 11, 2023

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.

@aufi
Copy link
Member Author

aufi commented May 11, 2023

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.

aufi added a commit to aufi/tackle2-hub that referenced this issue Jun 23, 2023
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 <[email protected]>
aufi added a commit that referenced this issue Jun 30, 2023
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 <[email protected]>
@aufi
Copy link
Member Author

aufi commented Jul 7, 2023

Analysis integration tests are continued in https://github.com/konveyor/go-konveyor-tests repository.

@aufi aufi closed this as completed Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants