My favorites | Sign in
Google
Projects on Google Code Results 1 - 7 of 7
#summary Overview and Introduction = API Documentation = The full documentation for this project is located at http://gaetestbed.geewax.org/index.html = Introduction = Writing tests for !AppEngine applications seems more difficult to me than it should be. This project is a set of base tes...
== Welcome Python Developers! == Here you will find my presentation materials and hopefully a series of tutorials to help the agile developer get moving with python. === Topics currently documented === SQLAlchemy (in brief) [http://pythontutorials.googlecode.com/svn/presentations/AgileSA...
The main plugin generates a series of SAX-like events that can be custom formatted into an XML document. The default formatter provides a simple XML document listing each test and its status, any associated traceback information and captured output. =Installation= {{{ $ easy_install nosexml ...
nose provides an alternate test discovery and running process for unittest, one that is intended to mimic the behavior of py.test as much as is reasonably possible without resorting to too much magic. nose has recently migrated from another host; if you recently filed a ticket at [http://nose.pyt...
When nosetests runs a sequence of tests and one of the tests crashes badly, i.e. causing python to terminate, all subsequent tests are aborted. This plugin will run the tests in a master/slave model where the master starts a slave which actually runs the tests the master tells it to. If a test cr...
nosetty is a plugin for [http://somethingaboutorange.com/mrl/projects/nose/ nose], a test runner for python. It accepts various commands at the terminal, giving you some one-on-one quality time with your tracebacks. Most importantly, editing a failure point is as easy as typing a number. How abou...
This is a plugin for [http://somethingaboutorange.com/mrl/projects/nose/ nosetests], a discovery based test runner for [http://python.org/ python]. If you're hacking deep inside your codebase and you break a core component, your test suite will probably blow up a zillion times with the same error...