Mailman 3 February 2010 - pytest-dev

[py-dev] py.test : setup / teardown at the directory level
by Philippe Fremy April 16, 2010

April 16, 2010

Hi, I was wondering if there is a possibility to have or emulate setup/teardown method for an entire directory of tests ? I have an expensive setup/teardown method, which I share through about 10 modules, each with about 20 tests. I would save time if I could do the setup/teardown just for that directory. cheers, Philippe

3 9

[py-dev] the seeming need of task-based build-tool properties in py.test
by Ronny Pfannschmidt Feb. 17, 2010

Feb. 17, 2010

hi, as needs like dependend tests, checking the need for test execution and the changes in distribution emerge, it seems like we are going tinto the direction of a task-based build tool where each test item is a 'task' that may depend on other tasks and has possible checked preconditions for being executed. i just wanted to throw that at the ml so people can discuss. -- Ronny

3 5

[py-dev] Testing daemonize() (of sorts)
by James Mills Feb. 15, 2010

Feb. 15, 2010

Hi Folks, Not sure how big this community here is, but at the suggestion of Ronny, here's a problem I'd like to "throw" at you: Consider the following test for my library circuits (1): http://bitbucket.org/prologic/circuits-dev/src/tip/tests/app/test_daemon.py Notice how I have to externally call "python app.py <pidfile>" in order to make the test work ? I haven't found a way to integrate the app within the test function/module at all without errors flying widely. The problem with the above method (although works and passes) is that the no coverage data is picked up by the fact that "app.py" was executed and therefore parts (or all) of the Daemon Component (2) were actually covered. Anyone have any suggestions or workarounds here ? Thanks, cheers James 1. http://code.google.com/p/circuits/ 2. http://bitbucket.org/prologic/circuits-dev/src/1e4ebb87eafc/circuits/app/__… -- -- "Problems are solved by method"

2 1

[py-dev] Acceptance testing with py.test
by Pontus Åström Feb. 15, 2010

Feb. 15, 2010

Hi, I'm considering a plugin for doing acceptance testing with py.test. The core idea is to mimic the behaviour of Concordion (http://concordion.org) with respect to visual effects and reports, but use a python engine. The python libs I am considering are py.test for running tests and genshi for xml instrumentation. Then, to get a polished plugin some code need to be written; a py.test plugin for test collection and reporting, and a utility library for easing genshi xml insturmentation. Well, the reason for this explanation is to see if anybody out there has some input regarding the idea, or maybe know of some useful libs or approaches to achieve the aim, which btw. is to obtain efficient, readable, executable acceptance tests connected to requirements. Read more about this aim on the Concordion website. Cheers, Pontus

3 4

[py-dev] RFC pytest metadata store plugin
by Ronny Pfannschmidt Feb. 15, 2010

Feb. 15, 2010

hi, i just got a basic item for a pytest caching plugin it would basically be a key-value store for test items/fspath items it should provide 2 objects as funcargs/py.test namesspace items path_meta store key-values for the current fspath item_meta store key-values for the current test item the need i have for such a feature is based in the speed issue of the codecheckers plugin, in particular pep8 is slow, and should be skipped in case of the file's mtime being less than the last run of the pep8 check and had no issues issues i havent clearly tought about yet is how to store and where to store options i currently can think of are: - xattr on the actual files/alternative streams - a sqlite db -- Ronny

3 2

[py-dev] how to use StdCapture().call propperly (i.e. not breaking py.test -s)
by Ronny Pfannschmidt Feb. 14, 2010

Feb. 14, 2010

hi, currently the codecheckers breaks py.test -s, cause the nested capture stops to work once the parent capture is gone. -- Ronny

1 0

[py-dev] pytest codecheck plugin, request for comments/review
by Ronny Pfannschmidt Feb. 13, 2010

Feb. 13, 2010

Hi, i just finished the initial version of my pytest-codecheck plugin its availiable at http://bitbucket.org/RonnyPfannschmidt/pytest-pycheckers/ currently it is not configurable, it just runs pep8 based on the moinmoin settings and pyflakes it lacks some idea of caching runs, it should auto-skip in case of codecheck-mtime > code-mtime regards Ronny

2 2

[py-dev] testrun.org, hudson, py.test
by holger krekel Feb. 12, 2010

Feb. 12, 2010

hi all, FYI i sent a mail regarding a new site http://testrun.org to the testing-in-python list, see below. Of course the contained offer applies to you here as well - may be useful for people using py.test to look into how it's configured for Hudson, a popular CI server written in Java. cheers, holger ----- Forwarded message from holger krekel <holger(a)merlinux.eu> ----- Date: Wed, 10 Feb 2010 15:02:38 +0100 From: holger krekel <holger(a)merlinux.eu> To: Testing in Python <testing-in-python(a)lists.idyll.org> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Subject: [TIP] starting testrun.org for testing in python Hi all, This year i plan to work a lot on testing and Python - and one of my plans is to build up some collective computing resources for testing. Not tied to any particular testing tool or practise but rather to Continous Integration methods. Here is the practical start of this effort:: http://testrun.org It doesn't have a fancy website such as Snakebite - in fact i really try to outcompete Titus on KISS principles here and just start operating it :) Note that I am using Hudson to get to know the current state of the art - i realize it's not a perfect fit for Python. It does have tons of plugins though and is a standard in the Java world (guess-what i actually just did some open-source strategy consulting in a Java shop and thus dived in :). We can add more jobs and views to it and if anyone here has experience and wants to help - i grant admin rights easily. Particularly since i am away after Pycon for 6 weeks. It'd also be great if some Snakebite resources or other resources could be added - just contact me or grab me at Pycon. It should not take more than 5 minutes to set a new node. Given interest i'll setup a mailing list where we discuss matters further - otherwise i presume it's ok to communicate a bit about this here. Any feedback and ideas welcome. And again, this is *not* py.test specific although i certainly want to make py.test integrate nicely. cheers, holger _______________________________________________ testing-in-python mailing list testing-in-python(a)lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python ----- End forwarded message ----- --

1 0

[py-dev] py.test 1.2.1 released
by holger krekel Feb. 8, 2010

Feb. 8, 2010

Hi all, i just released py-1.2.1 - thanks for all your feedback and suggestions here and on IRC. The announcement and changes: http://codespeak.net/py/dist/announce/release-1.2.1.html main fixes and improvements: * --funcargs [testpath] will show available builtin- and project funcargs. * display a short and concise traceback if funcarg lookup fails. * early-load "conftest.py" files in non-dot first-level sub directories. * --tb=line will print a single line for each failing test (issue67) * py.cleanup has a number of new options, cleans setup.py related files * always call python-level teardown functions even if setup failed (issue78). a detailed CHANGELOG is inlined below. cheers, holger P.S.: After Pycon US i am going to be offline until beginning april. Looking forward to it, btw! :) Changes between 1.2.1 and 1.2.0 ===================================== - refined usage and options for "py.cleanup":: py.cleanup # remove "*.pyc" and "*$py.class" (jython) files py.cleanup -e .swp -e .cache # also remove files with these extensions py.cleanup -s # remove "build" and "dist" directory next to setup.py files py.cleanup -d # also remove empty directories py.cleanup -a # synonym for "-s -d -e 'pip-log.txt'" py.cleanup -n # dry run, only show what would be removed - add a new option "py.test --funcargs" which shows available funcargs and their help strings (docstrings on their respective factory function) for a given test path - display a short and concise traceback if a funcarg lookup fails - early-load "conftest.py" files in non-dot first-level sub directories. allows to conveniently keep and access test-related options in a ``test`` subdir and still add command line options. - fix issue67: new super-short traceback-printing option: "--tb=line" will print a single line for each failing (python) test indicating its filename, lineno and the failure value - fix issue78: always call python-level teardown functions even if the according setup failed. This includes refinements for calling setup_module/class functions which will now only be called once instead of the previous behaviour where they'd be called multiple times if they raise an exception (including a Skipped exception). Any exception will be re-corded and associated with all tests in the according module/class scope. - fix issue63: assume <40 columns to be a bogus terminal width, default to 80 - fix pdb debugging to be in the correct frame on raises-related errors - update apipkg.py to fix an issue where recursive imports might unnecessarily break importing - fix plugin links

1 0

[py-dev] basic py.test tutorial - draft
by holger krekel Feb. 7, 2010

Feb. 7, 2010

Hi all, i've just completed my draft for the Pycon tutorial "rapid multi-purpose testing with py.test". see here for PDF and example directories: hg clone http://bitbucket.org/hpk42/pytest-tutorial1/ or just grab the PDF here: http://bitbucket.org/hpk42/pytest-tutorial1/raw/5a8deeba9184/pytest-basic.p… If anybody feels like walking through it and sending me feedback, that'd be much appreciated. It covers - basic usage - marking and skipping - funcargs - the "mysetup" pattern in successive examples. cheers, holger

1 0