Food for thought. I haven't touched Twisted in a decade and remember the fact we're using end-to-end tests is because there was no easy way to run multiple test files without attempting to restart Twisted's reactor which cannot be restarted and so was problematic a decade ago.
Github Copilot notes:
pyproject.toml disables the 'twisted' pytest plugin via addopts (-p no:twisted), but the PR description/README state the suite uses pytest-twisted. If pytest-twisted is intended, remove this disable; if not, drop pytest-twisted from dev deps and update docs accordingly to avoid confusion.
Originally posted by @Copilot in #34 (comment)
Food for thought. I haven't touched Twisted in a decade and remember the fact we're using end-to-end tests is because there was no easy way to run multiple test files without attempting to restart Twisted's reactor which cannot be restarted and so was problematic a decade ago.
Github Copilot notes:
pyproject.toml disables the 'twisted' pytest plugin via addopts (-p no:twisted), but the PR description/README state the suite uses pytest-twisted. If pytest-twisted is intended, remove this disable; if not, drop pytest-twisted from dev deps and update docs accordingly to avoid confusion.
Originally posted by @Copilot in #34 (comment)