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

Simplify testing with different object store using macros #278

Open
skejserjensen opened this issue Jan 29, 2025 · 0 comments
Open

Simplify testing with different object store using macros #278

skejserjensen opened this issue Jan 29, 2025 · 0 comments

Comments

@skejserjensen
Copy link
Contributor

Currently, all tests that use ObjectStore use LocalFileSystem as it is always available. However, the tests should also be executed on the other types of ObjectStore to ensure they all work as expected by passing the tests. This could be implemented as a function that accepts an ObjectStore and performs the actual tests and which is then called by test functions that each create a different type of ObjectStore. However, this would require a significant amount of boilerplate code for each test and a new test function must added to all of the tests that use an ObjectStore every time support for a new type of ObjectStore is added. Inspired by #[tokio::test], a Procedural Macro should be created to automatically generate a test for each type of ObjectStore, e.g., using an Attribute Macro. An open question is if the macro should check if the object stores are available when compiling so the tests can still be run on platforms without all of the object stores available.

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

1 participant