this might help: http://plone.org/products/getpaid/documentation/how-to/how-do-i-run-tests-for-getpaid/
Lucie -- six feet up, inc. | "Nowhere to go but open source" Direct Line +1 (317) 861-5948 x605 http://www.sixfeetup.com | Zope/Plone Custom Development + Hosting On Wed, Aug 12, 2009 at 1:50 PM, Brandon Craig Rhodes<[email protected]> wrote: > > I am going to help with some work on GetPaid, and wanted to start by > running its tests. I cannot find anything about running tests here: > > http://code.google.com/p/getpaid/wiki/DevGettingStarted > > So I played around a bit with the "getpaid.buildout" and discovered > that: > > $ bin/instance test getpaid.core > > indeed runs a smattering of tests (23 was the count) and succeeds. But > running the more conventional command: > > $ bin/test > > results in all sorts of problems with simplejson lacking 'test_suite' > objects in its modules, and with a problem import when trying to run > "getpaid.core.tests.test_order": > > from Products.validation import validation > ImportError: No module named validation > > My question is: how can I run the tests of all of the various > "getpaid.*" pieces, all at once, using "getpaid.buildout"? I want to > see that the tests succeed; I want to then go read the tests, since > tests tend to be pretty up-to-date documentation on how something works; > and I want to measure the code-coverage achieved by the current suite. > > Thanks for any pointers! > > -- > Brandon Craig Rhodes [email protected] http://rhodesmill.org/brandon > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~---
