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

Move all tests over to use Metadata instead of SingleTableMetadata and MultiTableMetadata #2151

Open
lajohn4747 opened this issue Jul 26, 2024 · 0 comments · May be fixed by #2186
Open

Move all tests over to use Metadata instead of SingleTableMetadata and MultiTableMetadata #2151

lajohn4747 opened this issue Jul 26, 2024 · 0 comments · May be fixed by #2186
Assignees
Labels
feature request Request for a new feature
Milestone

Comments

@lajohn4747
Copy link
Contributor

Problem Description

Move all tests over to use Metadata instead of SingleTableMetadata and MultiTableMetadata. When we introduce Metadata we should make sure all tests get switched over except for compatibility tests. Metadata should have been introduced while tests covered the legacy metadata class, but once they are confirmed to work we should move over all tests (besides compatibility tests) to use Metadata instead of doubling our test suite and slowing down our testing automation jobs.

Expected behavior

Once Metadata has been merged, move over existing tests to use Metadata instead of SingleTableMetadata and MultiTableMetadata

@lajohn4747 lajohn4747 added feature request Request for a new feature new Automatic label applied to new issues labels Jul 26, 2024
@npatki npatki removed the new Automatic label applied to new issues label Jul 29, 2024
@amontanez24 amontanez24 linked a pull request Aug 27, 2024 that will close this issue
@amontanez24 amontanez24 added this to the 1.17.0 milestone Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants