I have been asked the reasonable question
   how formal the testing will be. Are there any set procedures, or is
   it just "mess around and report bugs" arrangement?

The answer is both.  There will be specific areas that need testing
where we have disturbed the code substantially.  We will be producing
a list of these as we think of them, but replacing instruments, arrays
and analysis programs/opcodes are obvious candidates.  But also as
every opcode that creates or reads an audio value has changed we will
need undirected testing.  There are 1490 opcodes in all (i think) and
of these about 600 fall into this category, each of which needs
checking in normal and sample-accurate cases. (I have done some of
these but I it takes too much time; I have a list....)

==John ffitch

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'd also like to ask that if a bug is found, please consider
submitting a full CSD when reporting an issue.  It will make it easier
for us test and we can add it to the automated test suite, so that we
will continue to test against it for the future.

Thanks!
steven

On Mon, Feb 18, 2013 at 12:10 PM, john ffitch  wrote:
> I have been asked the reasonable question
>    how formal the testing will be. Are there any set procedures, or is
>    it just "mess around and report bugs" arrangement?
>
> The answer is both.  There will be specific areas that need testing
> where we have disturbed the code substantially.  We will be producing
> a list of these as we think of them, but replacing instruments, arrays
> and analysis programs/opcodes are obvious candidates.  But also as
> every opcode that creates or reads an audio value has changed we will
> need undirected testing.  There are 1490 opcodes in all (i think) and
> of these about 600 fall into this category, each of which needs
> checking in normal and sample-accurate cases. (I have done some of
> these but I it takes too much time; I have a list....)
>
> ==John ffitch
>
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
> is your hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials, tech docs,
> whitepapers, evaluation guides, and opinion stories. Check out the most
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

i got a build on gentoo64 (on intel core2) without much trouble. i was
fishing through the source for some test sets. its there a make test
somewhere?
k.

On 02/18/13 07:44, Steven Yi wrote:
> I'd also like to ask that if a bug is found, please consider
> submitting a full CSD when reporting an issue.  It will make it easier
> for us test and we can add it to the automated test suite, so that we
> will continue to test against it for the future.
>
> Thanks!
> steven
>
> On Mon, Feb 18, 2013 at 12:10 PM, john ffitch  wrote:
>> I have been asked the reasonable question
>>    how formal the testing will be. Are there any set procedures, or is
>>    it just "mess around and report bugs" arrangement?
>>
>> The answer is both.  There will be specific areas that need testing
>> where we have disturbed the code substantially.  We will be producing
>> a list of these as we think of them, but replacing instruments, arrays
>> and analysis programs/opcodes are obvious candidates.  But also as
>> every opcode that creates or reads an audio value has changed we will
>> need undirected testing.  There are 1490 opcodes in all (i think) and
>> of these about 600 fall into this category, each of which needs
>> checking in normal and sample-accurate cases. (I have done some of
>> these but I it takes too much time; I have a list....)
>>
>> ==John ffitch
>>
>> ------------------------------------------------------------------------------
>> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
>> is your hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials, tech docs,
>> whitepapers, evaluation guides, and opinion stories. Check out the most
>> recent posts - join the conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
> is your hub for all things parallel software development, from weekly thought 
> leadership blogs to news, videos, case studies, tutorials, tech docs, 
> whitepapers, evaluation guides, and opinion stories. Check out the most 
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Kelly,

Currently there are two suites of tests, one written in C and the
other in Csound CSD's.  You can run them after building Csound6 by
using:

make test
make csdtests

You can also optionally run cunit instead of make test to get a more
verbose output (and there are options on how to run cunit you can pass
it too).

All of the tests are in csound6/tests/c or csound6/tests/commandline.

Thanks!
steven

On Tue, Feb 19, 2013 at 3:11 AM, Kelly Hirai  wrote:
> i got a build on gentoo64 (on intel core2) without much trouble. i was
> fishing through the source for some test sets. its there a make test
> somewhere?
> k.
>
> On 02/18/13 07:44, Steven Yi wrote:
>> I'd also like to ask that if a bug is found, please consider
>> submitting a full CSD when reporting an issue.  It will make it easier
>> for us test and we can add it to the automated test suite, so that we
>> will continue to test against it for the future.
>>
>> Thanks!
>> steven
>>
>> On Mon, Feb 18, 2013 at 12:10 PM, john ffitch  wrote:
>>> I have been asked the reasonable question
>>>    how formal the testing will be. Are there any set procedures, or is
>>>    it just "mess around and report bugs" arrangement?
>>>
>>> The answer is both.  There will be specific areas that need testing
>>> where we have disturbed the code substantially.  We will be producing
>>> a list of these as we think of them, but replacing instruments, arrays
>>> and analysis programs/opcodes are obvious candidates.  But also as
>>> every opcode that creates or reads an audio value has changed we will
>>> need undirected testing.  There are 1490 opcodes in all (i think) and
>>> of these about 600 fall into this category, each of which needs
>>> checking in normal and sample-accurate cases. (I have done some of
>>> these but I it takes too much time; I have a list....)
>>>
>>> ==John ffitch
>>>
>>> ------------------------------------------------------------------------------
>>> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
>>> is your hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials, tech docs,
>>> whitepapers, evaluation guides, and opinion stories. Check out the most
>>> recent posts - join the conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> ------------------------------------------------------------------------------
>> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
>> is your hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials, tech docs,
>> whitepapers, evaluation guides, and opinion stories. Check out the most
>> recent posts - join the conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net