Closed kloczek closed 2 years ago
Tomasz Kłoczko wrote at 2021-9-22 14:45 -0700:
I'm trying to package your module as an rpm package. So I'm using the typical build, install and test cycle used on building packages from non-root account.
- "setup.py build"
- "setup.py install --root </install/prefix>"
- "pytest with PYTHONPATH pointing to sitearch and sitelib inside </install/prefix>
When will you learn that most zopefoundation
packages
have been designed for zope.testrunner
(not pytest
) as test runner?
Usually, the tests are activated via tox
, hiding test runner
details and testing various test variants (e.g. with
different Python versions).
It is unlikely that someone will take the effort to
support more than a single test runner
even if you report serveral pytest
failures every day.
When will you learn that most
zopefoundation
packages have been designed forzope.testrunner
(notpytest
) as test runner?
Issue is that this is no longer true. At the moment MAJORYTY of all zope modules is possible to test using pytest and only few of them reports only minor issues.
Tomasz Kłoczko wrote at 2021-9-22 16:46 -0700:
When will you learn that most
zopefoundation
packages have been designed forzope.testrunner
(notpytest
) as test runner?Issue is that this is no longer true. At the moment MAJORYTY of all zope modules is possible to test using pytest and only few of them reports only minor issues.
I wrote "most ... have been DESIGNED FOR ...".
This does not exclude that pytext
may work BY ACCIDENT.
A few packages have tests designed for pytest
.
Thus, start tests via tox
; the tox
configuration handles
details regarding the test runner.
It also installs required test dependencies.
What I did:
I'm trying to package your module as an rpm package. So I'm using the typical build, install and test cycle used on building packages from non-root account.
Looks like pytest is failing in few units:
What I expect to happen:
pytest should finish without errors and fails.
What version of Python and Zope/Addons I am using:
Python 3.8.12