On Oct 15, 6:15 pm, "Edward K. Ream" wrote:
> It has been fun tracking this down. I'll fix the documentation immediately.
Well, "immediately" now has a new meaning :-) For the last several day
I have been busy creating action items from leo-editor and email.
Still not done yet, but I just added
On Sat, Oct 15, 2011 at 5:03 PM, Edward K. Ream wrote:
> I am not sure what happens at present, and I'm not sure whether any settings
> apply to these commands.
Good news (mostly): you can set up dynamic unit tests exactly the way you want.
I was going to point you at the documentation but (ho
On Sat, Oct 15, 2011 at 3:54 PM, vitalije wrote:
> Did I cause appearing of this problem with enabling a new plug-in previously
> disabled? (I really did change @enabled plug-ins setting recently)
You might have "caused" the problem in some sense, but in a truer
sense you had nothing to do with i
Did I cause appearing of this problem with enabling a new plug-in previously
disabled? (I really did change @enabled plug-ins setting recently)
I would prefer if it would be possible to launch tests externally without
loading plug-ins.
As I see in Code-->Testing-->@file leoTest.py-->runUnitTest
On Sat, Oct 15, 2011 at 1:06 PM, vitalije wrote:
> I do test externally all the time and haven't noticed the above problem
> until recently.
The problems stem from newly enabled plugins.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To
I do test externally all the time and haven't noticed the above problem
until recently.
Anyway, thanks for the fix.
PS: I don't think that "assert True" need any gui related function as many
other tests. In fact I use a lot of tests just to execute some code without
writing script file and then
On Sat, Oct 15, 2011 at 1:22 AM, vitalije wrote:
> I have recently noticed strange behaviour of testing in Leo. Somehow tests
> run ok, but they are still reported as broken.
> Even a node with headline '@test example' and body of just one line 'assert
> True' is reported as FAILD
> Here is trace
Hello!
I have recently noticed strange behaviour of testing in Leo. Somehow tests
run ok, but they are still reported as broken.
Even a node with headline '@test example' and body of just one line 'assert
True' is reported as FAILD
Here is traceback:
File ".../leo-editor/trunk/leo/core/leoComman
