Actually the exec-tests folder should probably be removed - that was our
initial attempt at adding a test for each syntax variant while we were
doing the refactoring project. They were translated at some point into the
new test format at
This may be what you are looking for. Specific pieces of the engine are tested
for every build.
https://github.com/livecode/livecode/tree/develop/engine/exec-tests
Thanks,
Brian
On Oct 2, 2019, 3:06 PM -0400, kee nethery via use-livecode
, wrote:
> I assume RunRev does unit tests for
On 10/2/19 12:05 PM, kee nethery via use-livecode wrote:
I assume RunRev does unit tests for LiveCode.
Is there a test harness where we can submit a stack to be in the unit test set
of tests that they use?
Hypercard was hella reliable, I’d love for Livecode to be as reliable.
>> pinging
I assume RunRev does unit tests for LiveCode.
Is there a test harness where we can submit a stack to be in the unit test set
of tests that they use?
Hypercard was hella reliable, I’d love for Livecode to be as reliable.
Kee Nethery
___
use-livecode
