hundreds-father-40408/24/2020, 2:45 AM
, tests can use Pytest style of top-level functions. The expectation would be for each test file to create a Pytest fixture that returns a
type, which wraps a SchedulerSession and exposes entry points like
. Because it’s a fixture, you define it once, and then each individual test gets a new copy of the
, which preserves the test isolation we need. If you want multiple distinct setups in your test file, you can create multiple fixtures. The test then says which fixture it wants to use.
is now changed to use Pytest style with the top-level function
has always been that way.
is the only hold out
will take as optional args the normal classmethod boilerplate we have, e.g.
Because it’s a dataclass with a constructor, we can do things like add a boolean parameter
RuleRunner(target_types=[PythonLibrary], rules=[*python_sources.rules(), foo])
, which will pre-register those to ameloriate the issue with rule registration being icky
register_util_rules: bool = True
aloof-angle-9161608/24/2020, 2:52 AM