vitalije,
I'm running from the console by running the launchLeo script from the
command line.
I think the tests do run - when I open the unittest.leo file and do
run-all-unit-tests-locally, the window freezes - indicates something is
going on.
As you can see from my test, there are false
the results should appear in the console. Leo should be started with the
console and also you need to select @test node or some of its ancestors
before executing run-unit-tests-locally.
Try also executing tests externally.
Try assert False to make test fail and see if there is any output
Hi Vitalije,
I think I have a bigger problem - see my other message. Even when I run
Leo's own unit tests I get no "output".
On Monday, October 15, 2018 at 2:37:32 PM UTC-7, vitalije wrote:
>
> you should put:
>
>1. @others line in @test node before assertions statements
>2. put cloned
Seems I have the same problem when I load unitTest.leo. When I run tests, I
do not see their results.
On Monday, October 15, 2018 at 2:29:44 PM UTC-7, anl...@gmail.com wrote:
>
> Thanks vitalijie.
>
> I think I get the idea, but I'm still having trouble.
>
> Let's say I start with this node
you should put:
1. @others line in @test node before assertions statements
2. put cloned factorial node under the @test node
that way the definition of the factorial function will be part of the test
script that get executed by Leo's run-tests command.
Vitalije
On Monday, October 15,
Thanks vitalijie.
I think I get the idea, but I'm still having trouble.
Let's say I start with this node (hyphen denotes a node, and indented
hyphen denotes a subnode).
- factorial
This node contains my factorial definition.
Now I'll create some more nodes so that I end up with:
- factorial
Responding to Chris's comments re cPanel / LeoVue etc., just a PSA,
Docker is easier and more useful than you think ;-)
It sits less comfortably in Windows than it does in Linux, but it
gives an extremely clear cut curated environment and is really not
complicated to use if you're at all familiar
Red Hat Openshift provides a free node.js environment online but after an
hour of trying to suss out how to marry LeoVue with that I am going back to
writing.
My brain hurts.
Chris
On Monday, October 15, 2018 at 8:01:37 AM UTC-7, Chris George wrote:
>
> Success after installing more
> This has nothing to do with recent work. I am executing pytest from the
command line on Windows.
Mystery solved, and fixed at 16011ec6. The culprit was python3_test.py.
python3_test.py created the "a" and "b" files with module level code!
I found this file by brute force, deleting all
On Sunday, October 14, 2018 at 4:01:06 PM UTC-5, Edward K. Ream wrote:
>
>
> Rev ea79240bb changes leoRope.py so that it fails gracefully if rope does
>> not exist. Rev f5a3ef694 deletes the rope folder. All tests pass.
>>
>
> But somehow this breaks TravisCI.
>
The traceback from TravisCI
Success after installing more depednencies manually.
I run a small web hosting operation on the side. Now to find a way to
install this entire infrastructure on cPanel without terminal access to the
server. :-(
cPanel is still about a year away from rolling node/npm as supported
Ugh. The entire node/npm thing is a dog's breakfast. I have problems, as
usual.
Linux Mint 18 KDE
node v10.12.0
npm 6.41
Running npm run build or npm run dev gets me these errors. This was after
having to manually install a handful of dependencies that npm couldn't
satisfy.
ERROR in
On Mon, Oct 15, 2018 at 8:06 AM Edward K. Ream wrote:
> This has nothing to do with recent work. I am executing pytest from the
> command line on Windows.
>
> pyflakes (without args) or even pyflakes --setup-plan generates two empty
> text files, named "a" and "b" in the present directory.
This has nothing to do with recent work. I am executing pytest from the
command line on Windows.
pyflakes (without args) or even pyflakes --setup-plan generates two empty
text files, named "a" and "b" in the present directory. This is true even
if no fixtures are found! I have looked in
-- Forwarded message -
From: Matt Wilkie
Date: Sun, Oct 14, 2018 at 6:21 PM
Subject: warning: bug in cached @file and/or Leo Cloud plugin?
To: leo-editor
Heads up:
> I've just had this weird situation where I noticed the @file contents
were definitely NOT the most recent
15 matches
Mail list logo
