http://permalink.gmane.org/gmane.comp.python.testing.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.python.testing.general/5513 <pre>Thanks for mentioning those two. On a brief read the differences seem to be: - Cram runs test scripts located in separate files, and can patch them with the differences, which would make it great for testing documentation examples, and maybe a bit harder if you want to run some Python setup or mocking code around the code under test. - ScriptTest returns the output etc from the command for the test to examine, whereas shelliketests and cram automatically diff it against expected output. On 18 June 2013 00:36, Chris Wesseling &lt;Chris.Wesseling&lt; at &gt;cwi.nl&gt; wrote: </pre> Martin Pool 2013-06-17T21:58:00 http://permalink.gmane.org/gmane.comp.python.testing.general/5512 <pre> I've been using Ian Bicking's ScriptTest library for that. And this weekend I learned that it's what the pip project is using too. It's on pypi. </pre> Chris Wesseling 2013-06-17T14:36:30 http://permalink.gmane.org/gmane.comp.python.testing.general/5511 <pre> On similar topic, the Mercurial sell-like tests tools have been extracted as "cram" https://bitheap.org/cram/ I never tested the bzr one so I have no idea how they compare to each other. </pre> Pierre-Yves David 2013-06-17T09:12:58 http://permalink.gmane.org/gmane.comp.python.testing.general/5510 <pre>I have just extracted the 'shell-like tests' library from bzr's test library. example: def test_echo(self): run_script(self, """ $ echo hello world hello world """) This library makes it easy to write integration tests for programs with a command-line interface: you just give the command and the expected output. The command can be run as an in-process Python call, to let you precisely control its environment through mocks etc. This style also makes it pretty easy for new contributors to add tests. https://github.com/sourcefrog/shellliketests </pre> Martin Pool 2013-06-16T20:34:42 http://permalink.gmane.org/gmane.comp.python.testing.general/5509 <pre> I've done that and it definitely changes the behavior, but not in a helpful way. Mostly the ResourceWarnings go away, but every once in a while (e.g. maybe every 5th run of the test suite) one will crop up, always in the tearDown of a different test. It's crazy! :) -Barry _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> Barry Warsaw 2013-06-14T19:47:30 http://permalink.gmane.org/gmane.comp.python.testing.general/5508 <pre> Sprinkling gc.collect() in all the suspicious tearDown() methods might trigger these warnings sooner, and attribute them to the right test. Running the tests in isolation might help too (I once had a monstrous one-liner that piped zope.testrunner's bin/test --list-tests to a while loop that ran each test in its own process via bin/test -t ^$test\$). Marius Gedminas </pre> Marius Gedminas 2013-06-14T18:00:55 http://permalink.gmane.org/gmane.comp.python.testing.general/5507 <pre>I'm wondering if anybody has some advice for tracking down ResourceWarnings in a test suite of some code written for Python 3.3. I've got a few of these cropping up which are probably related to ssl sockets that aren't getting closed properly, but it's been difficult for me to track them down by code inspection alone. Even when I instrument my tox.ini file to run the tests with -Werror::ResourceWarning, I don't get much more output than this: test_load_index_with_device_keyring (resolver.tests.test_index.TestDownloadIndex) ... Exception ResourceWarning: ResourceWarning('unclosed &lt;ssl.SSLSocket object, fd=5, family=2, type=1, proto=6&gt;',) in &lt;ssl.SSLSocket object, fd=5, family=2, type=1, proto=6&gt; ignored I suspect that the warning isn't directly tied to this test though because it can occur in different places. It's probably due to something run by my ThreadPoolExecutor and could be caused by a mock. Just wondering if anybody has some general recommendations for getting better error reporting out of Pyth</pre> Barry Warsaw 2013-06-13T19:25:49 http://permalink.gmane.org/gmane.comp.python.testing.general/5506 <pre>I figured it out in the end. Basically the module I wanted to patch had the same name of a package that was imported in __init__.py. This made the name clash and mock was getting confused of coursre, 2013/6/12 andrea crotti &lt;andrea.crotti.0&lt; at &gt;gmail.com&gt; _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> andrea crotti 2013-06-13T08:48:23 http://permalink.gmane.org/gmane.comp.python.testing.general/5505 <pre>I'm having a strange issue with Mock (version 1.0.1) that I've never noticed before So I have a patch in this form: &lt; at &gt;patch('app.notifications.create_notification') def test_challenge_ended_going_in_review(self, fake_create): but I get an error from that same test complaining about: AttributeError: &lt;module 'app.handlers.notifications' from '/home/andrea/wazoku/wazoku/wazoku-api/api/app/handlers/notifications/__init__.pyc'&gt; does not have the attribute 'create_notification' but I can't figure how and why it adds the "handlers" in between.. app/notifications.py is a perfectly normal module, what could be messing up things? Thanks _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> andrea crotti 2013-06-12T11:03:08 http://permalink.gmane.org/gmane.comp.python.testing.general/5504 <pre> Hmm, well, I dug into this and killed with a big hammer. So, starting here: MiniMe:~ chris$ sudo -u jenkins -i MiniMe:~ jenkins$ cd /Users/Shared/Jenkins/Home/workspace/xlrd/0e321e7b MiniMe:0e321e7b jenkins$ /Users/Shared/Jenkins/Home/shiningpanda/jobs/7dd0339e/tools/bin/python -c "import tox; tox.cmdline();" -c tox.ini GLOB sdist-make: /Users/Shared/Jenkins/Home/workspace/xlrd/0e321e7b/setup.py ERROR: invocation failed, logfile: /Users/Shared/Jenkins/Home/workspace/xlrd/0e321e7b/.tox/log/tox-0.log ERROR: actionid=tox msg=packaging cmdargs=['/Users/Shared/Jenkins/Home/shiningpanda/jobs/7dd0339e/tools/bin/python', local('/Users/Shared/Jenkins/Home/workspace/xlrd/0e321e7b/setup.py'), 'sdist', '--formats=zip', '--dist-dir', local('/Users/Shared/Jenkins/Home/workspace/xlrd/0e321e7b/.tox/dist')] env=None running sdist running check error: .tox/python/lib/python2.7/_abcoll.pyc: No such file or directory ERROR: FAIL could not package project Okay, well, at least I could reproduce. Breaking this down to </pre> Chris Withers 2013-06-10T15:45:05 http://permalink.gmane.org/gmane.comp.python.testing.general/5502 <pre> I presume the latest since I think the ShiningPanda plugin upgrades everything when it starts. Of course, Olivier can point out if I'm wrong :-) Chris </pre> Chris Withers 2013-06-09T21:46:44 http://permalink.gmane.org/gmane.comp.python.testing.general/5501 <pre>Another thing which I don't have quite clear yet. Can I use the LiveServerTestCase class in django 1.5 with the selenium saucelabs/whatever library? Or if I stick with the Django way of doing things I can't use these methods? 2013/6/7 andrea crotti &lt;andrea.crotti.0&lt; at &gt;gmail.com&gt; _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> andrea crotti 2013-06-07T15:16:35 http://permalink.gmane.org/gmane.comp.python.testing.general/5500 <pre>Thanks! So I think the main requirement would be to be able to write tests in a way that they run locally and on the Saucelab grid without touching them. Maybe that's possible already with the saucelab library not sure, but if this library solves it than I'll definitively have a look thanks a lot. 2013/6/7 Ronny Pfannschmidt &lt;ronny.pfannschmidt&lt; at &gt;gmx.de&gt; _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> andrea crotti 2013-06-07T14:43:09 http://permalink.gmane.org/gmane.comp.python.testing.general/5499 <pre>Hi Andrea, pytest-mozwebqa has support for saucelabs. Im currently refactoring it for usage with fixtures and will work on integrating with pytest-django later. </pre> Ronny Pfannschmidt 2013-06-07T13:43:27 http://permalink.gmane.org/gmane.comp.python.testing.general/5498 <pre>I'm putting together a plan for testing our django-based application. So basically we would like to use Selenium + sauce labs, but also make it easy to run tests normally, individually or not. And potentially even set up a CI machine internally that runs tests all the time (even if not for all the browsers that Saucelabs uses). I started to use Splinter now since the API is nice, but the first thing is that I'm not sure I can make it work with Saucelabs though. And frankly the various helper functions are quite simple to rewrite so maybe it's not worth.. Any suggestions on something I can look at? What do you use? Thanks _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> andrea crotti 2013-06-07T13:12:59 http://permalink.gmane.org/gmane.comp.python.testing.general/5497 <pre>I may cobble something together, this is a medium-low priority thing for a side project, so no guarantees, sorry :( Alex On Mon, Jun 3, 2013 at 6:14 PM, Ned Batchelder &lt;ned&lt; at &gt;nedbatchelder.com&gt;wrote: </pre> Alex Gaynor 2013-06-06T03:31:55 http://permalink.gmane.org/gmane.comp.python.testing.general/5496 <pre>Hi, i just release pytest-cache-1.0 to pypi which allows to re-run failures from previous test runs and provides a mechanism for other plugins to store data across test session (used e.g. by pytest-pep8). See https://pypi.python.org/pypi/pytest-cache for some docs. The main news is the "--ff" option which runs all tests but first the failures from the last run. Thanks to Jack Riches for the patch. Full Changelog below. cheers, holger 1.0 ---------------------------------------------- - merged "--ff" (failedfirst) option to run all tests but run the last-failed ones first. Thanks Jack Riches. - fix issue6 - --clearcache doesn't bail out if .cache doesn't exist, thanks longlho - fix issue4: consider setup time skip of a previous failure as no longer failing - ensure --cache output is sorted </pre> holger krekel 2013-06-04T19:29:06 http://permalink.gmane.org/gmane.comp.python.testing.general/5495 <pre>There's nothing there to do what you want, but a refactoring through a few layers in data.py would make it possible. Are you going to cobble together something yourself? --Ned. On 6/2/2013 12:04 PM, Alex Gaynor wrote: _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> Ned Batchelder 2013-06-04T01:14:02 http://permalink.gmane.org/gmane.comp.python.testing.general/5494 <pre>What I meant is that I have the contents of `pickle.load(open(".coverage"))` as an object in my program. Alex On Sun, Jun 2, 2013 at 4:55 AM, Ned Batchelder &lt;ned&lt; at &gt;nedbatchelder.com&gt;wrote: </pre> Alex Gaynor 2013-06-02T16:04:12 http://permalink.gmane.org/gmane.comp.python.testing.general/5493 <pre>Alex, you seem to be on the cutting edge of unusual uses of coverage.py! When you say you have the data in memory, what does that mean exactly? It sounds like what you need is a refactoring of coverage/data.py:CoverageData.combine_parallel_data to allow you to feed data into a combining step. --Ned. On 6/1/2013 4:16 PM, Alex Gaynor wrote: _______________________________________________ testing-in-python mailing list testing-in-python&lt; at &gt;lists.idyll.org http://lists.idyll.org/listinfo/testing-in-python </pre> Ned Batchelder 2013-06-02T11:55:53 http://permalink.gmane.org/gmane.comp.python.testing.general/5492 <pre>Before going into persisting processes and IOStrings, how about just setting up a RAM disk in user space on your target? </pre> Benjamin Scherrey 2013-06-02T11:24:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.testing.general