Hi all,
Last week at devcon euro 2012 we talked about pre-release testing and
I'm volunteering to help things forward w.r.t. testing.
One of the problems we've seen with the last release was that really
basic functionality like audio file playback and radio playback did
not work on some targets
I just read the email about the test cases: well it is a very good
idea. I completely agree this and actually doing a project with a
methodology can help quite a lot.
I don't know if you guys are aware of the agile methodologies, well
look for user stories and acceptance tests (XP/Scrum and Agile
On Tue, May 29, 2012 at 06:58:53PM +0200, Bertrik Sikken wrote:
With respect to test strategy: In my opinion, we can start with
a set of rather basic tests to verify high-level behaviour, rather
than to go for test completeness. A test suite taking about (say)
one hour should keep the barrier
Yes. Atomic tests. Not just saying playback, you're right, it's too wide.
And yes, plugin or other high level functionalities have to be
debugged later: it's a music player after all :D
Lorenzo
2012/5/29 Frank Gevaerts fr...@gevaerts.be:
On Tue, May 29, 2012 at 06:58:53PM +0200, Bertrik Sikken
On Tue, May 29, 2012 at 08:48:42PM +0200, Lorenzo Miori wrote:
Yes. Atomic tests. Not just saying playback, you're right, it's too wide.
Yes, but that wasn't really my point :) What I mean is that we should
have a *small* basic test suite (which, yes, consists of clear
unambiguous and simple
On Tue, May 29, 2012 at 9:40 PM, Frank Gevaerts fr...@gevaerts.be wrote:
On Tue, May 29, 2012 at 08:48:42PM +0200, Lorenzo Miori wrote:
Yes. Atomic tests. Not just saying playback, you're right, it's too wide.
Yes, but that wasn't really my point :) What I mean is that we should
have a
