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 nose.run() did not run properly. There were several problems: argv[0] must be the command name, the egg_info must be generated first, and it had also issues with output redirection.

So I solved it differently, by running "setup.py test" for the quickstarted project in a subprocess and checking the output. This has the advantage that TG can switch to any other test runner like nose2 and nothing has to be adapted in this test.

The improved test_quickstart found a failing test with Mako on Windows due to different linefeeds that would otherwise have gone unnoticed.

We should now also add a Travis service hook for tg2devtools.

-- Christoph

--
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to turbogears-trunk+unsubscr...@googlegroups.com.
To post to this group, send email to turbogears-trunk@googlegroups.com.
Visit this group at http://groups.google.com/group/turbogears-trunk.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to