Missing test dependencies: hypothesis about pydoctor

[tristanlatr]

it looks like all the test dependencies are already liste in the test extras: https://github.com/twisted/pydoctor/blob/662eafaedcdfcfa0c5a83c1048c28f187fbcf4c9/setup.cfg#L64C6-L64C6

so it’s just a matter of installing the test extra and documenting this process.

[tristanlatr]

This requirement is installed through tox. I agree it should be listed in the setup.cfg under the test requirements, but for the short term: can you use tox to run tests ?

[buhtz]

can you use tox to run tests ?

Describe in the docu how and then I can.
I don't like tox and don't think this is something external contributors should be bothered with. But it is your decision as upstream maintainer. But part of your decision then should be documented.
Do not expect that contributors know what tox is or know how to use it. It would be easier for all of us if you would stick to default-vanilla Python build system. You can use tox/poetry/fancy-xyz in your CI or your not-public build machine.

And I don't trust your tox config. Even your vanilla unit tests do use the real filesystem. How does tox mess up my system then?

Your tox do not work out of the box. See #755.

[tristanlatr]

Ok lets move the test dependencies out of the tox config so tests can by simply be run with pytest.