Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixtures give a CLI user the option of defining benchmark input parameters
as "fixtures", i.e. results of functions locate in a special named module,
enabling better customization and configuration.
Unlike pytest, we operate only on raw Python callables, and do not expose
features like scopes, fixture names, and IDs. This is because our
motivation is slightly different from that of pytest, in that we need to
track parameter values and try to keep them constant ("session-scoped")
across benchmarks, except in niche cases.
Our magic filename is
conf.py
, similarly to conftest.py for pytest.This change incurs changes in how we construct and typecheck parameters -
since we now allow heterogeneous parameters in benchmarks by virtue of
fixtures, we need to typecheck each individual parameter set. This will
be done in a followup.