Most projects probably run linting before testing.
At the moment the order of execution cannot be specified properly:
test may depend on lint
but still specific tests (e.g. test-python) do not depend on lint-python
We could use one of the following approaches for solving this:
A) add a configuration variable (RUN_LINT_BEFORE_TEST) in order to let all modules add a module-specific dependency (e.g. test-python: lint-python)
B) add a test-prepare target, which depends on the linting (and maybe other details). All module-specific tests must depend on it - or we must ensure somehow (ordered dependencies?), that the test-prepare target is fulfilled first.
Most projects probably run linting before testing.
At the moment the order of execution cannot be specified properly:
* `test` may depend on `lint`
* but still specific tests (e.g. `test-python`) do not depend on `lint-python`
We could use one of the following approaches for solving this:
* A) add a configuration variable (`RUN_LINT_BEFORE_TEST`) in order to let all modules add a module-specific dependency (e.g. `test-python: lint-python`)
* B) add a `test-prepare` target, which depends on the linting (and maybe other details). All module-specific tests must depend on it - or we must ensure somehow (ordered dependencies?), that the `test-prepare` target is fulfilled first.
Most projects probably run linting before testing.
At the moment the order of execution cannot be specified properly:
test
may depend onlint
test-python
) do not depend onlint-python
We could use one of the following approaches for solving this:
RUN_LINT_BEFORE_TEST
) in order to let all modules add a module-specific dependency (e.g.test-python: lint-python
)test-prepare
target, which depends on the linting (and maybe other details). All module-specific tests must depend on it - or we must ensure somehow (ordered dependencies?), that thetest-prepare
target is fulfilled first.The (undesired) relationship between
lint
andtest
was removed in5a39e297c7
.