Re: [LAU] Linux Audio podcast. episode002

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Louigi Verona <louigi.verona@...>
Cc: linux-audio-user <linux-audio-user@...>
Date: Wednesday, August 14, 2013 - 2:17 pm

--089e0160b7beb2b02c04e3e9026b
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 14, 2013 at 9:00 AM, Louigi Verona
wrote:

here:
http://www.louigiverona.ru/?page=projects&s=writings&t=linux&a=linux_pod...

You most certainly have a point: thanks for bringing this up for discussion.

I'll introduce a few concepts I feel are relevant to this discussion:
1. Developer time is best spent developing, not doing testing.
2. As a developer I know how that a lot of time goes into testing.
3. If testing is not done, the software suffers.
4. The developer will test their uses for the software while writing it.

My background is writing Luppp, a live performance software. I've had it
crash before getting on stage to do a performance, I now know the
"users-perspective" of a crash: it simply is not acceptable.
That said, I cannot possibly test every hardware control surface, every
effect plugin etc with it. How can the testing be performed to a good
standard?

One idea that comes to mind is a group of "testing-buddies". Basically,
I'll spend 5 minutes doing bug-reports for you, if you do the same for me.
Since each tester will try to accomplish different things (and on a
different system etc), perhaps this could help?
A downside to this idea is that essentially developers test for each other:
in the end of the day developer time is spent testing.

I'm open to suggestions, criticism etc :) -Harry

--089e0160b7beb2b02c04e3e9026b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 14, 2013 at 9:00 AM, Louigi Verona <louigi.verona@gmail.com> wrote:<=
br>> This time talking of getting tired to file bug reports, get the pod=
cast here:

rojects&s=3Dwritings&t=3Dlinux&a=3Dlinux_podcastYou=
most certainly have a point: thanks for bringing this up for discussion.
I'll introduce a few concepts I feel are relevant to this discussio=
n:1. Developer time is best spent developing, not doing testing.2. =
As a developer I know how that a lot of time goes into testing.3. If te=
sting is not done, the software suffers.
4. The developer will test their uses for the software while writing it.My background is writing Luppp, a live performance software. I've =
had it crash before getting on stage to do a performance, I now know the &q=
uot;users-perspective" of a crash: it simply is not acceptable.
That said, I cannot possibly test every hardware control surface, every eff=
ect plugin etc with it. How can the testing be performed to a good standard=
?One idea that comes to mind is a group of "testing-buddies&qu=
ot;. Basically, I'll spend 5 minutes doing bug-reports for you, if you =
do the same for me.
Since each tester will try to accomplish different things (and on a differe=
nt system etc), perhaps this could help?A downside to this idea is that=
essentially developers test for each other: in the end of the day develope=
r time is spent testing.
I'm open to suggestions, criticism etc :) -Harry

--089e0160b7beb2b02c04e3e9026b--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Linux Audio podcast. episode002, Louigi Verona, (Wed Aug 14, 8:00 am)
Re: [LAU] Linux Audio podcast. episode002, Devin Anderson, (Tue Aug 20, 7:03 pm)
Re: [LAU] Linux Audio podcast. episode002, Louigi Verona, (Tue Aug 20, 9:10 pm)
Re: [LAU] Linux Audio podcast. episode002, Dave Phillips, (Wed Aug 14, 10:14 pm)
Re: [LAU] Linux Audio podcast. episode002, Chris Bannister, (Fri Aug 16, 11:36 am)
Re: [LAU] Linux Audio podcast. episode002, Ralf Mardorf, (Thu Aug 15, 12:17 am)
Re: [LAU] Linux Audio podcast. episode002, Julien Claassen, (Wed Aug 14, 7:52 pm)
Re: [LAU] Linux Audio podcast. episode002, J. Liles, (Wed Aug 14, 4:10 pm)
Re: [LAU] Linux Audio podcast. episode002, david, (Wed Aug 14, 5:49 pm)
Re: [LAU] Linux Audio podcast. episode002, Chris Bannister, (Fri Aug 16, 11:32 am)
Re: [LAU] Linux Audio podcast. episode002, drew Roberts, (Fri Aug 16, 2:05 pm)
Re: [LAU] Linux Audio podcast. episode002, Ralf Mardorf, (Fri Aug 16, 1:34 pm)
Re: [LAU] Linux Audio podcast. episode002, Chris Bannister, (Fri Aug 16, 2:09 pm)
Re: [LAU] Linux Audio podcast. episode002, Ralf Mardorf, (Fri Aug 16, 2:36 pm)
Re: [LAU] Linux Audio podcast. episode002, Chris Bannister, (Sun Aug 18, 7:05 am)
Re: [LAU] Linux Audio podcast. episode002, Ralf Mardorf, (Wed Aug 14, 4:42 pm)
Re: [LAU] Linux Audio podcast. episode002, Dan MacDonald, (Wed Aug 14, 4:26 pm)
Re: [LAU] Linux Audio podcast. episode002, J. Liles, (Wed Aug 14, 4:44 pm)
Re: [LAU] Linux Audio podcast. episode002, Paul Davis, (Wed Aug 14, 4:49 pm)
Re: [LAU] Linux Audio podcast. episode002, J. Liles, (Wed Aug 14, 4:53 pm)
Re: [LAU] Linux Audio podcast. episode002, Dan MacDonald, (Wed Aug 14, 4:57 pm)
Re: [LAU] Linux Audio podcast. episode002, J. Liles, (Wed Aug 14, 5:03 pm)
Re: [LAU] Linux Audio podcast. episode002, Russell Hanaghan, (Wed Aug 14, 5:40 pm)
Re: [LAU] Linux Audio podcast. episode002, J. Liles, (Wed Aug 14, 4:48 pm)
Re: [LAU] Linux Audio podcast. episode002, Harry van Haaren, (Wed Aug 14, 2:17 pm)
Re: [LAU] Linux Audio podcast. episode002, Paul Davis, (Wed Aug 14, 2:21 pm)
Re: [LAU] Linux Audio podcast. episode002, Dan MacDonald, (Wed Aug 14, 9:29 am)
Re: [LAU] Linux Audio podcast. episode002, Barney Holmes, (Wed Aug 14, 1:36 pm)