thanks Rob, I will follow these steps and if there are more doubts I will write again.
Yurggent Alfredo. 2013/2/7 Rob Weir <[email protected]> > On Thu, Feb 7, 2013 at 5:49 PM, alfredo chable torrez > <[email protected]> wrote: > > Hi team, > > I have already working on bugs but > > I have doubts that I should be doing now in testlink. > > Someone who is doing something related to this would kindly give me > > guidance on: > > - What do I do now? > > - How I can start? > > -- What subject? > > > > Sure. > > When we have builds of OpenOffice 4.0 that have new features, and are > stable, then we will run the manual test cases defined in Testlink. > These tests are two kinds: > > 1) Tests of new features that have been added to AOO 4.0. New code > tends to have more bugs, so we'll give them a lot of attention. We'll > need to define the test cases first, of course. > > 2) Tests of existing features, even if they are not being modified for > 4.0. This is called "regression testing". We're looking for > regressions, or things that were working before but now are broken. > Why? Because academic studies have shown that 25% of defects come > from introducing new bugs by changing other code. > > But we're not quite there. Most of the test cases were defined by > project volunteers in China, and they are going away for their Chinese > New Year celebration. My guess is we'll start the AOO 4.0 testing in > another 10 days or so. > > So until that time, you don't need to touch Testlink at all. Right > now we're focusing on reviewing bug reports on the already released > versions of OpenOffice, including 3.4.1, 3.4.0, 3.3.0, etc. This is > the work described as "Easy QA Task: Confirm New Defect Reports" here: > > http://openoffice.apache.org/orientation/intro-qa.html > > Regards, > > -Rob > > > > all this questions are about of test cases. > > > > thanks in advance. > > > > Yurggent Alfredo >
