Menu
▾
▴
#242 programmatic access to summary data
If one is running *lots* of tests, it might be nice to
have an option to display the results in a different
way, like:
foo: pass
bar: fail
baz: pass
fcopy: pass
and so forth.
Maybe it would be better to give some sort of
programmatic interface to the summary information, such
as test name, result, desired result, test text, etc...
that way it would be possible to write ones own ways of
collecting the information.
Logged In: YES
user_id=240
I guess some of this is available, maybe another option to
verbose is enough to keep it from giving you more
information than just a plain 'fail'?
Logged In: YES
user_id=80530
seems like the core of a good idea.
If you can flesh it out a bit (what
interface are you looking for, etc.)
we can get a TIP going on it.
Logged In: YES
user_id=80530
Tcl Bugs 761334 and 761344
suggest other needs along these
lines. Currently summary information
about the test suite is printed by
[cleanupTests], but the data that
makes up that report is not available.
Additional interfaces to access the
internal values like $numTests(Failed)
would allow for combining results
from multiple interps (the issue in
those bug reports) and would allow
for reporting the same data in
alternate formats, as requested here.
Logged In: YES
user_id=240
Upon looking through the code, it seems as if tcltest really
was designed as an application rather than a library.
'puts', 'exit' and the like are used throughout.
Logged In: YES
user_id=240
I have an initial cut at some changes. They are pretty far
reaching, so before going any further, I would like to
submit them for people to have a look at.
Known failures:
1) One of the rename tests renames 'incr', which is used by
the new version of the test suite.
2) A few of the tests access the 'testConstraints' variable
directly.
There are probably other things, but I'd rather find out
sooner or later that some aspect of the direction I'm taking
needs reworking or abbandoning.
Logged In: YES
user_id=240
It wasn't ok with the previous upload. Let's try again and
compress it this time.
Logged In: YES
user_id=79902
I approve of a programmatic way of getting test results in
general and especially so if it works across processes
(there are a few spots in the core test suite which could
make good use of it) but I have no specific expertise to
offer on how to make it happen or whether davidw's patch is
a good one.
Logged In: YES
user_id=80530
here's an updated patch against
the current HEAD.