[wingide-users] wing unittests und plone

Wingware Support support at wingware.com
Mon Jan 12 11:15:52 MST 2009


robert rottermann wrote:
> when this script is started with a "test" parameter, insted of starting
> zope/plone the test are run.
> so it would be nice, if the last line could be replaced with:
> exec "$WING" "$ZOPE_RUN" -C "$CONFIG_FILE" "$@"

That won't work of course.

Is the issue that you want to use these tests in the integrated Testing
tool, or do you want to debug them, or do you just want to be able to launch
from Wing?

If that latter, you should be able to do it in the OS Commands tool in
Wing IDE Pro.

If you want to debug, you may be able to do that by using 'import wingdbstub'
as described at http://wingware.com/doc/debug/debugging-externally-launched-code
or by configuring a project that mimics the environment set up by the
launcher script and set up the $ZOPE_RUN file as the main debug file.

To work with tests in the Testing tool, the only way is to find and
add the actual unit test files that the Zope/Plone script is running.
If they depend on setup and tear-down that's done by that script and
don't themselves contain code to do that before/after tests are run,
then they probably will not work in Wing's Testing tool w/o modification.

-- 

Stephan Deibel
Wingware | Python IDE
Advancing Software Development

www.wingware.com



More information about the wingide-users mailing list