Am 25.06.2013 00:29, schrieb Alessandro Molina:
Ok, finally found the reason.
While on more recent versions the output for subtests is:
tgtest00.tests.functional.test_authentication.TestAuthentication.test_forced_login
Anonymous users are forced to login ... ok
On Python2.6 the class path
On Mon, Jun 24, 2013 at 3:50 AM, Alessandro Molina
alessandro.mol...@gmail.com wrote:
On Sun, Jun 23, 2013 at 3:27 PM, Christoph Zwerschke c...@online.dewrote:
But then BaseTestQuickStart must also create and destroy a separate
virtualenv in its setUp and tearDown methods.
It seems that
Am 24.06.2013 18:18, schrieb Alessandro Molina:
I made some advancements on the testsuite and now is able to pass on
Py2.7 on travis: https://travis-ci.org/TurboGears/tg2devtools/builds/8390939
Great. I tried it under Windows and fixed a small issue. Another problem
is that some packages like
On Mon, Jun 24, 2013 at 8:01 PM, Christoph Zwerschke c...@online.de wrote:
Am 24.06.2013 18:18, schrieb Alessandro Molina:
I made some advancements on the testsuite and now is able to pass on
Py2.7 on travis: https://travis-ci.org/**TurboGears/tg2devtools/builds/**
8390939
On Mon, Jun 24, 2013 at 11:35 PM, Alessandro Molina
alessandro.mol...@gmail.com wrote:
It's now working on all systems apart py2.6, I'll setup a 2.6 environment
with pythonz/brew and I'll try to see what goes wrong.
Ok, finally found the reason.
While on more recent versions the output for
Ok,
tests are now passing on both Py2 and Py3.
I provided a travis configuration file and enabled travis, but all the
tests are failing due to missing dependencies,
it seems I was wrong on the setup.py test subprocess assumption that it
would install the subtest dependencies, we currently have
Am 23.06.2013 14:51, schrieb Alessandro Molina:
The most simple solution would be to specify all the dependencies in
tests_require of devtools, but I don't think this is the right solution,
the tests should probably install the dependencies depending on the
quickstarted app.
But then
On Sun, Jun 23, 2013 at 3:27 PM, Christoph Zwerschke c...@online.de wrote:
But then BaseTestQuickStart must also create and destroy a separate
virtualenv in its setUp and tearDown methods.
I tried to tackle the problem in
On Thu, Jun 20, 2013 at 11:29 PM, Christoph Zwerschke c...@online.dewrote:
Am 20.06.2013 00:06, schrieb Alessandro Molina:
Maybe someone more proficient in nose knows a better way to run the
tests of the generated application from inside the testsuite, right now
it loads them with nose.run
Am 21.06.2013 15:12, schrieb Alessandro Molina:
2) What to do on Py3, the current travis env for TG2.3 tests on Py26,
27, 32, 33. But some of the quickstarts don't work on Py3 due to missing
libraries (ming, sprox, tgext.admin mostly). What should we test? Should
gearbox quickstart create the
Am 20.06.2013 00:06, schrieb Alessandro Molina:
Maybe someone more proficient in nose knows a better way to run the
tests of the generated application from inside the testsuite, right now
it loads them with nose.run which makes the whole testsuite result as a
single test.
I found that
On Tue, Jun 18, 2013 at 12:18 AM, Alessandro Molina
alessandro.mol...@gmail.com wrote:
Ok, I understand that, but as it is, it's not much more than gearbox
quickstart PROJX cd PROJX; nosetests -v, I think that it might make
sense to have it around only if we modify it to actually try all the
Am 20.06.2013 00:06, schrieb Alessandro Molina:
I tried to implement a more flexible test suite for quickstart, it now
runs the quickstart with different options trying to run the test suite
for each one of them.
You beat me to it, I wanted to do in a similar way.
Maybe someone more
In devtools.test there is a test_pastetemplate which is broken in 2.3
because devtools.pastetemplate does not exist any more. Are there plans
to add tests to devtools again before 2.3 is out?
-- Christoph
--
You received this message because you are subscribed to the Google Groups
TurboGears
I never noticed tg.devtools had a testsuite, as it is does it actually make
any sense?
As It runs a subset of the tests available in the testsuite of the
generated package, can't we just run the testsuite of the generated app?
On Mon, Jun 17, 2013 at 6:32 PM, Christoph Zwerschke c...@online.de
So yea, coming back from the death here :)
That code actually does two things.
a) It automates starting a project and makes sure that is possible.
b) It then runs a generate and then runs the tests of the generated project
to make sure it's tests are properly run.
So it's a test of both the
Great to hear you again Jorge ^^
Ok, I understand that, but as it is, it's not much more than gearbox
quickstart PROJX cd PROJX; nosetests -v, I think that it might make
sense to have it around only if we modify it to actually try all the
available quickstart options to make sure that every
17 matches
Mail list logo
