https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231555

Kubilay Kocak <ko...@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |feature

--- Comment #3 from Kubilay Kocak <ko...@freebsd.org> ---
I'd like to see something like this leverage/extend the test framework bits if
necessary to achieve what we want, to make it usable for cases other than just
pytest (nosetests, unittest, whatever). python.mk could then setup/wrap python
specific test scenarios, using generic TEST_* (TEST_COMMAND/TEST_CMD_ARGS, etc)
variables wherever possible.

I see most of the value created in leveraging/extending the test framework,
than is obtained from removing the need for TEST_DEPENDS and not needing to
specify a test target.

Test invocations are *notoriously* non-standard in the Python world (granted,
python -m pytest 'is' a common one), with various permutations of a
env/commands/args combination necessary to get it just right.

Further, its very commonly the case that pytest along is not a
standalone/sufficient dependency by itself, and having them split implicitly in
the framework and explicitly in the port is not particularly desirable.

This idea has been an open task [1] for the Python team for a while, looking
for at least a *minimally* considered/designed schema to support a plurality of
test execution needs, rather than just added on an adhoc basic, and hopefully
one that could be leveraged to the benefit of other softwares/language stacks
in the ports tree.

Perhaps a good place to start would be to take stock of the existing test
methods for existing python ports and see what scheme we can come up with to
support the 'major classes' of test execution methods.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"

Reply via email to