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

End to end build test #238

Open
charles-turner-1 opened this issue Oct 31, 2024 · 0 comments
Open

End to end build test #238

charles-turner-1 opened this issue Oct 31, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@charles-turner-1
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

As described in #153 & #230, I think it would be wise to add an end to end test where we

  1. Build a subset of the catalog, or an alternate test catalog.
  2. Execute some queries against this subset/test catalog.

This is mostly a belt & braces approach in response to the intake take2 upgrade. Although we have good unit test coverage (~96-97%), end to end tests give us another layer of confidence that everything is behaving as we expect.

It's going to be necessary to only build a subset or a test catalog: building the full catalog takes on the order of 1.5 hours using 48 cores on Gadi, which is prohibitively expensive.

Describe the feature you'd like

End to end tests ensuring that catalog builds produce the expected outcomes.

Describe alternatives you've considered

  • Not bothering with E2E tests
  • Full catalog build, followed by some tests against the built catalog.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant