[wingide-users] Wing tests not running
robert at redcor.ch
Thu Aug 2 02:16:05 MDT 2012
as we all avoid spaces and non ascii characters in our files and directory names
like "der teufel das weihwasser"
this is no limit at all!
is it not?
Am 01.08.2012 21:53, schrieb Murray:
> Great, thanks
> Not sure if it's a wing issue, but it looks like that Python Path option in
> project properties doesn't support unicode directory names. (on windows 7)
> On 1 August 2012 17:58, Wing IDE Support <support at wingware.com
> <mailto:support at wingware.com>> wrote:
> On 8/1/12 11:40 AM, Murray wrote:
> My tests need to be run from the base directory else they will fail with
> ModuleImportFailure, when they can't find the module they're supposed to
> be testing.
> If this is what is happening, why isn't wing reporting that failure?
> Is there a way to prevent Wing's test runner from changing the execution
> Or should I be changing my directory structure somehow?
> The issue probably is the current directory. Wing's test runner was
> designed when the default method of running tests was to put a call to
> unittest.main() in the test file and then to run that file from the
> command line -- which would result in the directory that the file was is
> being added to python's sys.path.
> When you run tests outside of Wing, how does the directory for your
> non-test modules get added to sys.path? One possibility to work around
> Wing's test runner's current limitations is just to add that directory to
> the Python Path via the Project Properties dialog.
> Wing IDE users list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wingide-users