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

Unify testing utilities #694

Open
sebastiantia opened this issue Feb 12, 2025 · 0 comments
Open

Unify testing utilities #694

sebastiantia opened this issue Feb 12, 2025 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@sebastiantia
Copy link
Collaborator

Please describe why this is necessary.

We have repeated definitions of testing utilities such as into_record_batch defined in both the top-level kernel and test-utils crate, along with other examples such as repeated definitions of string_array_to_engine_data that should be merged.

This duplication increases maintenance overhead and can lead to inconsistencies between test implementations.

Describe the functionality you are proposing.

  • Consolidate duplicated testing utilities into a single, well-defined location (likely test-utils).
  • Ensure that all test code references the unified utilities rather than maintaining separate versions.
  • Where applicable, refactor existing tests to use the centralized implementations to improve maintainability and readability.

Additional context

No response

@sebastiantia sebastiantia added enhancement New feature or request good first issue Good for newcomers labels Feb 12, 2025
@sebastiantia sebastiantia changed the title tests: unify testing utilities Unify testing utilities Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant