[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 2/4] added autotest support
From: |
Christopher Brannon |
Subject: |
[PATCH 2/4] added autotest support |
Date: |
Wed, 29 Sep 2010 13:27:59 -0500 |
Andrei Kholodnyi <andrei.kholodnyi at gmail.com> writes:
> you mean , w/o make check, make installcheck fails?
Exactly.
> yes, every make *check, e.g. make distcheck will run tests automatically.
It would be nice if we could disable them for make distcheck.
The unfortunate thing is that the tests produce a large quantity of
spoken output. There's no way to verify it automatically.
I suppose we could write a "null" module, for testing purposes.
The null module would simply log everything that it receives, without
speaking anything. We could then compare the log against a file that
describes expected behavior.
Obviously, this would not test the synthesizers, but it would be perfect
for testing libraries, client-server communication, and server-module
communication.
For now, I suspect that the best way to test synthesizers is by
listening. Yes, we could come up with a scheme for recording audio from
an output module, and then compare the output against a sample file.
However, seemingly insignificant changes to the underlying TTS engine could
cause a bit-by-bit comparison to fail. E.G., inserting a pause, or improving
the pronunciation of a word. I think we'd have to use some sort of
heuristic. Are there any good methods of comparing audio clips for
similarity?
-- Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://lists.freebsoft.org/pipermail/speechd/attachments/20100929/05242b11/attachment-0001.pgp>
[PATCH 3/4] added c_api tests to the testsuite, William Hubbs, 2010/09/27
[PATCH 4/4] fix copyright assignment, William Hubbs, 2010/09/27