William Hart
William Hart
I think this would be very helpful so we understand the categories of tests that aren't being executed. I suspect that this will require a nose plugin.
We need an option to ignore tests in a specific sub-package. Perhaps '-i'.
Currently, the differences reported do not ignore the smart logic that PyUtilib supports. The output needs to be adapted to only show real differences.
The subprocess.run command either does not return the appropriate value or it does not generate output. This branch is focused on resolving this discrepancy.
I needed for my app more robust support for *.ini files parsing. (especially UTF8 encoding in ini files) I was not sure how to create a new config parser plugin...
PyUtilib has a prolific habit of running, "from pyutilib.X import *" within the module **init**.py. While this is "convenient" for many users, I think it needs to either be removed...
This should be a feature supported by the testing infrastructure in pyutilib.th NOTE: it's not entirely clear how this data should be reported.
pyutilib.testdriver should produce JUnit XML output that includes the & blocks to report the test output and error for all tests. NB: Those blocks should be included for ALL tests:...
pyutilib.testdriver should support options for redirecting test output and error to alternative locations. Currently, the test output is logged to a file and then deleted(?). The driver should support options...
The pyutilib.testdriver should allow specifying multiple sets of options for a solver. It would then run a "full-factorial" suite of tests. For example: ``` testsuites: solvers: solver_a: np: - 1...