Hi pytest contributors and users!
hope your initial exploratory "2014" testing worked out ok!
Since the pre-xmas release 2.5.1 we got a few more bugs reported:
https://bitbucket.org/hpk42/pytest/issues?status=new&status=open&kind=bug
Could some of you look into some of them, possibly commenting/owning?
Relatedly, I also opened a doodle for the first 2014 bug/issue day:
http://doodle.com/uph9qa6ydqaad3ay
Please respond quickly as i'd like to announce the final date on Monday.
During that day i'd also like to discuss a roadmap for 2.6 and what
we want included there. Currently I am thinking of this:
- introduce a little warning system so we can emit them from hooks
through config.warn(...) for generic warnings and node.warn() for a
location-bound warnings. Like lint/pep8 checks warning types should
get a number W01, W02 etc. so they can be disabled selectively.
They would be reported like skips with e.g. "5 passed, 3 warnings" and you
can get details reported via "-rw". Warnings do not cause a non-zero
return code. This system should help to resolve a couple of enhancement
issues/address complaints, for example when test classes with an __init__
are skipped and someone took hours to find out why the test class is
not collected. (These day's it produces a skip 's skipped
- move traceback presentation logic from py lib to pytest and provide
better Python3 support (nested tracebacks etc.) and maybe some "shorter"
traceback options. This addresses and helps to address a number of
traceback related enhancement issues.
- (maybe) improve marker mechanism to work similarly to fixture one,
e.g. a @pytest.marker decorator marks a marker function which can process
any parameters (and bail out if parameters are bad).
- other issues selected from the issue tracker
Note sure yet but we might go for a 2.5-maintenance branch and use
"default" for 2.6 targetted development. Comments welcome.
FYI i got generous sponsored access to Rackspace hosting resources
and would appreciate some help in managing windows/linux hosts
into something we can use for pytest continous integration/development.
If anyone knows how to automate Windows or Linux setups i can give sub
accounts to play with.
Lastly if anyone is interested in doing a 2014 Summer of Code project
for pytest, let me/us know. I guess we should publish this via a re-tweeted
blog entry some time and list some potential projects.
cheers,
holger
_______________________________________________
Pytest-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pytest-dev
