Issue 22263: Add a resource for CLI tests (original) (raw)

Issue22263

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/66459

classification

Title: Add a resource for CLI tests
Type: enhancement Stage:
Components: Tests Versions: Python 3.4, Python 3.5, Python 2.7

process

Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: ezio.melotti, michael.foord, pitrou, serhiy.storchaka, zach.ware
Priority: normal Keywords:

Created on 2014-08-24 06:47 by serhiy.storchaka, last changed 2022-04-11 14:58 by admin.

Messages (3)
msg225796 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2014-08-24 06:47
Some modules have command-line interface (not always documented and tested). Their tests run a lot of subprocesses and requires long time, often longer than other tests of corresponding module. However command-line interface itself is much less important than Python interface. In the face of addition of more CLI tests it would be good to introduce new resource ("commandline" or "cli") which will control the run of such tests.
msg225896 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2014-08-25 20:38
Or you could use the existing "cpu" resource.
msg225908 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2014-08-26 06:31
Looks reasonable. On other hand, there is the "subprocess" resource which currently is not used in any test.
History
Date User Action Args
2022-04-11 14:58:07 admin set github: 66459
2014-08-26 06:31:09 serhiy.storchaka set messages: +
2014-08-25 20:38:27 pitrou set messages: +
2014-08-24 06:47:43 serhiy.storchaka create