I'm curious about participating in this project. Let me give some background and then some specific questions.
(Background) I have some testing experience ( http://www.kaner.com ) and I teach courses on software testing ( http://www.testingeducation.org -- see especially http://www.testingeducation.org/BBST for the black box testing course). Every term, my students join an open source testing project, replicate some bugs, create some tests and file some bug reports. We have not uploaded any of our tests ideas because we don't create step-by-step test specifications. In general, I think this approach to test design is useful for very basic smoke testing that you would do to check individual builds for the most straightforward functionality, but that it is counterproductive for even slightly more advanced testing. ( http://www.testingeducation.org/BBST/bbstScripting.html ) Instead, I try to teach my students to think in terms of test ideas. For example, what are the risks associated with a certain type of functionality? How could we test for those? Another example, how could we combine variables and what combinations might be most efficient or most interesting? We tend to present these ideas in outlines, tables, and other charts. Someone who knows how to test can work from the idea to the details of the test. Obviously, not everyone can do this well (not the test design nor the development / execution of tests from test ideas). On the other hand, following scripted tests is something that no skilled tester will work on -- especially as a volunteer -- for long. Nor is it something useful for my students on their resumes. (Being able to show off what they did on a project like this is a great way for students to demonstrate clue during an interview for their first testing job). Are you interested in pulling together a library of test ideas? I'm asking this in a discussion of database testing, but my question is general, across all of the applications of open office. - Cem Kaner -----Original Message----- >From: Andre Schnabel <[EMAIL PROTECTED]> >Sent: Aug 5, 2006 11:25 AM >To: [email protected] >Subject: Re: [qa-dev] Announce: New dba QA projekt > >Hi Chris, * > >and sorry for the (very) late answer. > > >Chris Lukasiak schrieb: >> hallo all, >> >> i proudly present the new qa pages* as addition to the dba area - they >> contain (or will contain in future time) sections for different kinds >> of testcases and everything around this - the main idea behind it is >> to center the qa of structured manual testing in this point, make it >> better overviewable and shareable for better quality of oo. >> >> please support this project - the project contain many roles, from >> database beginners to specialists, from some minutes sparetime to ... >> we search for people from the community (not only oo qa): writing, >> reviewing and executing testcases (translate testcases). the results >> will be inputted into the tcm tool (bugtracking tool) after the >> process is cleared (comming soon). > >> *(available over the dba side or directly here: >> http://dba.openoffice.org/QA/index.html) >I'll use your test cases at our OOo camp at the next weekend. So at >least we should be able to contribute some results. > >I think, afterwards we should go on and advertize this a little more. So >we could use this as a starter for more regular product feature tests. > >What do you think .. would it be a good idea to set up a wiki-page for >that? We could link the test case specification templates that J�rg has >proposed from there and gather comments on the process. (e.g. how to >suggest new test cases, how to handle them in TCM ...) > >It would be great, if you could set up such a page. > >Andr� > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
