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
https://github.com/livecode/livecode/tree/develop/tests/lcs/core.
This blog post is still worth a look even though it is now two years out of
date: https://livecode.com/testing-1-2-28534/ - nothing fundamental
has changed about test structure since then. If you're planning on writing
(LCS) tests, this document describes the API of the test library
https://github.com/livecode/livecode/blob/develop/docs/development/testing.md
I still need to write a bit about integrating Travis CI at some point!
On Wed, 2 Oct 2019 at 22:06, Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:
> 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 <
> use-livecode@lists.runrev.com>, 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.
> >
> > Kee Nethery
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
