Announce: New dba QA projekt

James Mckenzie wrote:
> -----Original Message-----
> 
>>From: chris lukasiak <christoph.lukasiaksun.com>
>>Sent: Aug 15, 2006 2:24 AM
>>To: devqa.openoffice.org
>>Subject: Re: [qa-dev] Announce: New dba QA projekt
>>
>>James Mckenzie wrote:
>>
>>
>>>-----Original Message-----
>>
>>in this case i want to know the different needs:
what is interesting to 
>>test and what is interesting to know, who can do
that and how we can 
>>present the results
>>
> 
> We need tests for all Base functionality, not just a
few parts of the product.

good motivation, but nevertheless we have to start with just
a few parts 
and after that we can expand and complete them step by step

> 
>>>
>>>>I do like this idea, so there are definitely
scenarios that can be 
>>>>developed for testing. I would have one
question though : would it be 
>>>>possible to have some kind of db entry form
for the results rather than 
>>>>having to e-mail them to you, with the
inevitable mailbox overload that 
>>>>might cause ?
>>>
>>>
>>>Might I suggest an issue for this?  I think that
the code should be Enhancement
>>>or Task.
>>
>>the tcm tooling like it is right now, is definetly
not adequate for test 
>>scenarios beyond language testing - this has to be
improved in any way 
>>(among others, andre schnabel is working on that
problem)
>>
> 
> The Base test scenarios are basically there to test
localization.  However, if expanded,
> they could be a good start for a full test sequence for
Base (as well as the other parts
> of OpenOffice that interface with Base.)
> 
> The 'bottom line' is that all of the test cases
should be located in one place.  If that one
> best place is TCM, then that is where they should go. 
I'm in favor of TCM as test cases
> can be broken down into pieces (cases) and then
evaluated on their own.  Also, test
> cases that have problems can have issues attached to
them.  Since I test the 'base' 
> product's language (American English) I should be able
to test for problems and 
> not worry about localization problems.  Thus an issue
produced by my team should
> apply to all languages, not just one.  This expands the
use of TCM from only localization
> issues to program issues.  Also, I have found problems
with some of the menus and
> other items because they are/were created by someone
who does not use English as
> their primary language.  I appreciate their attempts
and try to gently correct minor
> problems (such as the use of informations vice the
correct information (it is plural by
> itself).)

due to the fact that i am not a native english speaker, but
an 
experienced function tester, my intentions goes more
technical ways, but 
i would be glad if you could also have a 'language driven'
look on this 
project.

> 
> Hopefully, I see the TCM as a method to track
completeness of testing (where are we
> at with a certain test cycle as far as testing for
localization and program issues) and 
> who is testing what part.  This was lacking prior to
the incorporation of TCM or took
> much time and communications to complete.
> 
> I appreciate your work on developing a set of test
cases for Base and hope that your
> work is the start of efforts by other teams to improve
there testing to include interaction
> between the various parts of OpenOffice.org.

thank you

> 
> James McKenzie
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
> For additional commands, e-mail: dev-helpqa.openoffice.org
> 

bye chris

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org