I looked at the tutorial on @test usage and finally realized why it wasn't working for me. In order for the @test to have the code loaded so it can test it, (when your not working on loaded, Leo code), you need to grab it from somewhere and then follow it with test. The way the tutorial handles this is to have an @file node at the top of your code, so the @test can load it via an import.
I could so the same thing but was not structuring things this way as I was just developing an at button script. Doing this would also require that I save the @file node before each run of an @test of change code. Is there a way to do something like the following for the @test node?: load(@button, "dothis") test_statements... basically just create the scriptfile.py of the @button and append the test(s). Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
