Dedicated Haiku QA (testing) team
I have brought up this idea in the past on the Haiku mailing list, but didn't get real takers at that time. I decided I'd post the idea here. Is there anybody (including the project leads and developers of the Haiku project) interested in assembling a QA (testing) team? I would like to get involved in the testing side of things and help out where I can. I actually do QA (testing) for a living for a language learning software company here in the US. I actually deal with back-end systems that support various client applications, so I'm always beating around on some random operating system whether it's Windows, Mac OS X and/or Linux with testing integration, etc...
I think the QA (testing) team could...
- help manage the defects cataloged and re-test them to see if they're still valid
- write simplified test cases based on requirements and use cases
- support testing life cycles prior to a release
- help coordinate (and recruit for?) alpha and beta testing
I know some developers would prefer QA testers to also fix bugs and though I have some coding skills myself; I'd prefer not to delve into the Haiku code base until I'm more experienced with C/C++ and have the confidence to do such things.
Anyone else have ideas or opinions on this subject??