Re: [Denemo-devel] First interactive test of Denemo

It seems to work here.

About distribution, well, interactive test won't be checked as regularly as automated ones. It is more to check a regression when we have a doubt about a functionality. So I think the name of the test should be as expressive as possible, so when we will have to check for a feature/bug it is easy to do.

2013/11/7 Richard Shann <address@hidden>

I have created the first of what I hope will be a collection of
interactive tests for Denemo.
If you open the file test/playback_test.denemo the file has a large
button to run the test and tells you what you should expect when you do
this.
In this case, it tests for regression in playback from the cursor when a
large file is involved (and playback is near the end). This was a bug I
fixed recently.

Tests such as this will be needed for things we cannot automate. This
example shows how to do it. The machinery is visible when you load the
file and open the scheme window. In there is the scheme that creates the
button; the script for action of pressing the button is more scheme
(embedded) which includes the code for changing the button to tell the
tester what they should expect.

(CreateButton "Test" "Click to run test")

(d-SetDirectiveTagActionScript "Test"
"(CreateButton \"Test\"
\"You should hear a C major scale\")
(d-DenemoPlayCursorToEnd)")

As you can see, when the scheme is embedded we need to double up the
escaping of the backslashes.

Please try out this test, it works on my machine. I am not sure what the
conventions are for distributing tests with programs ...
and, of course, we will need automated tests too.

Richard

_______________________________________________
Denemo-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/denemo-devel

--
Éloi Rivard - address@hidden

« On perd plus à être indécis qu'à se tromper. »

From:	Éloi Rivard
Subject:	Re: [Denemo-devel] First interactive test of Denemo
Date:	Fri, 8 Nov 2013 11:07:42 +0100