On 10/27/05, Dave Johnson <[EMAIL PROTECTED]> wrote: > Allen asked: "how exactly are we planning to deal with various > databases as we move forward?" > > I think we need to designate a person for each database. I'll take > PostgreSQL, since I use it on one of my main dev boxes. Testing for > HSQLDB is partially built-in, because the unit tests run against it > (and everybody runs those unit test before doing a commit, right?). I > say partially, because we're testing HSQLDB database create but not > upgrade.
I'll take DB2 and Derby. I might need a little walkthrough the test suite at some point. > > But that question brings up the larger issue of how to divide up > testing responsibilities. > > We don't have a dedicated QA person in our group, so Allen, Linda and I > have been doing most of the testing. This is not enough, we're not QA > pros and we need some help. I think it would probably be in the best > interest of all Roller users/developers if we could coordinate our > testing efforts. How can we do that? So far, I only have a couple of > ideas here: > > - Test plan: come up with comprehensive test plan/matrix in spreadsheet > form that lists all of the test cases for Roller UI features, the unit > tests, installation issues, etc. > > - When approaching release time, attempt to get complete coverage by > asking for volunteers to be assigned different parts of the matrix. > > Any other ideas here? Any QA engineers that want to help out? > > - Dave
