Hey Ronny,

On Wed, Apr 13, 2011 at 00:38 +0200, Ronny Pfannschmidt wrote:
> hi,
> 
> after some thought i would like to discuss adding a generic testdir,
> so for each test different plugins could store data/metadata
> 
> currently only the tempdir plugin creates a session dir on first use of
> the tmpdir funcarg/pytest.mktemp
> 
> i'd rather have to possibility to store for each test
>  * full test id
>  * stdout/err
>  * logfile for stdlib logging
>  * tmpdir for plugin
>  * some kind of serialized full taceback,
>    optionally with some locals/globals
>  * coverage reports
>  * profiler reports
>
> since all of those are a misfit for the tmpdir functionality,
> i'd like to propose a extension of the mechanism
> 
> the basic tmpdir would move to the "tmpdir" subdir of the testdir,
> stdout/err, log, would in turn be files in the testdir
>
> it would also be easily possible to keep those in sync with xdist+rsync
> should the need arise, just make a new testdir for the remote id, and
> sync the directory content.
> 
> further possible uses include using coverage data and test results of
> previous runs to decide what tests can likely be skipped without causing
> too much of a problem or providing relative progress information on the
> collection status (based on the number of test id's in the last run).
> 
> Please discuss additional uses and possible problems.

Currently, i'd think going for a "testdir" that easily allows to create
dirs, files, run (sub) processes and collect results is one thing.

And the other thing, collecting and accessing all kinds of historic
information from a test run does not need to be accessible via a
funcarg, does it?

IMO, a pytest-history plugin would introduce recording all this
information and adding cmdline opts for re-run/re-present info
to access it as well as an API (pytest.gethistory() or so)

best,
holger

> Regards Ronny



> _______________________________________________
> py-dev mailing list
> py-dev@codespeak.net
> http://codespeak.net/mailman/listinfo/py-dev

_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev

Reply via email to