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

Consider defining the driver workload in its own file #100

Open
p-mongo opened this issue Jan 22, 2021 · 0 comments
Open

Consider defining the driver workload in its own file #100

p-mongo opened this issue Jan 22, 2021 · 0 comments

Comments

@p-mongo
Copy link
Contributor

p-mongo commented Jan 22, 2021

@jmikola suggests defining driver workloads (which now use the unified test format, which comes with a validator) in a separate file, so that they can be easily validated:

Looking at the test files in #98, it looks like unified test format files (schemaVersion 1.0, so I assume no format changes) are nested within other files. Can this be changed to separate them out so we can actually perform schema validation on them? For example, the workload executor could point to a filename (or base name, so drivers can decide to use YAML or JSON).

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