I use "tools/do_tests.sh -fu -m release" to run the whole suite before
checkin.
When this fails, I run from within Wing in various ways so that I can
debug. Whenever Wing debugs something, it builds a command line that
looks like: "(project python path) (selected python filename)
(additional per-filename options)", and runs that in the project default
directory; you can also specify additional environment variables that
are set on a per-filename bases.
So, for my normal Chandler debugging, the Chandler.py per-filename
options are "--catch=never --nosplash --create --profileDir
c:/my/chandlerbin --logging z:/my/parceldir --webserver --stderr".
To debug the functional test suite, I add "-T" to that.
To debug individual functional tests, that "-T" is replaced by
"--chandlerTests functionalTestName".
To debug individual unit tests, I add "UNIT_TESTING=True" as an
additional per-filename environment variable, and right-click that
unit-test filename and "Debug Selected" (the command line ends up being
a CHANDLERHOME-relative path to the unit-test script).
In all these cases, the python path is (CHANDLERHOME;
CHANDLERHOME/parcels); I have CHANDLERHOME and CHANDLERBIN (which are
different!) set as environment variables, and have CHANDLERBIN on my PATH.
...Bryan
Dan Steinicke wrote:
To aid in our on going efforts to improve the functional tests I have
been ask to collect the methods people are currently using to run them.
Could everyone who runs functional tests please reply to this email
with a brief explanation of how you run the tests.
For myself I usually run from the console like this:
debug/RunChandler -ceT --catch=test
or occasionally tools/do_tests.sh -f
or from wing by setting chandler.py as the main debug file and using
the run arguments: -cT --catch=never
thanks for your help
Dan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
