test on debian 64bit and windows 7 64bit

[esasystem <te...@esasystem.com>]

Hello Rob, in addition to doing the test on windows 7 64bit I can do the 
test even on debian 64bit, so if there is work for me I'm ready

Re: test on debian 64bit and windows 7 64bit

[Rob Weir <ro...@apache.org>]

On Fri, Jan 18, 2013 at 5:09 PM, Lucas Burson <lj...@gmail.com> wrote:
> Hi Rob,
>
> On Fri, Jan 18, 2013 at 10:30 AM, Rob Weir <ro...@apache.org> wrote:
>> 1) Start with this query in Bugzilla:
>> https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&namedcmd=unconfirmed-defects&list_id=42178
>
> I've never been able to open a Bugzilla URL that has a search command
> (namedcmd=unconfirmed-defects). I usually perform my own search, but
> is there a trick to using your url? I haven't seen how to create my
> own command.
>

My mistake.  I forgot to share the query in BZ.  If you login now to
Bugzilla you should see to saved queries in your footer:   "new in
last week" and "unconfirmed-defects"  Either one can be a good source
of reports to review.

> Also why some rows of the bugs list colored red? I thought I would see
> the pattern by now but it seems random.
>

It is based on the "importance" field.  Critical and blocker issues
are red and bold red.  When we get into testing a new dev releases
we'll use "blocker" to say that a bug blocks us from testing other
functionality.  For example, a bug in the File/Open dialog would block
many other tests.

But for end-user submitted bugs, these values signify something more
like "it is blocking my work".  If there is a known workaround I then
either quickly explain it to them or send them to the support forums
and then reset the importance to something more accurate.

-Rob


>
> Thanks,
> Lucas

Re: test on debian 64bit and windows 7 64bit

[Lucas Burson <lj...@gmail.com>]

Hi Rob,

On Fri, Jan 18, 2013 at 10:30 AM, Rob Weir <ro...@apache.org> wrote:
> 1) Start with this query in Bugzilla:
> https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&namedcmd=unconfirmed-defects&list_id=42178

I've never been able to open a Bugzilla URL that has a search command
(namedcmd=unconfirmed-defects). I usually perform my own search, but
is there a trick to using your url? I haven't seen how to create my
own command.

Also why some rows of the bugs list colored red? I thought I would see
the pattern by now but it seems random.


Thanks,
Lucas

Re: test on debian 64bit and windows 7 64bit

[Rob Weir <ro...@apache.org>]

On Thu, Jan 17, 2013 at 4:22 PM, esasystem <te...@esasystem.com> wrote:
> Hello Rob, in addition to doing the test on windows 7 64bit I can do the
> test even on debian 64bit, so if there is work for me I'm ready

I reviewed the bugs from your previous batch.  Good job!

Some quick observations:

1) Be sure to set the "needmoreinfo" field if you are waiting for
information from the user, like a sample file or more details.  I see
you did this in most cases, but not in this one:
https://issues.apache.org/ooo/show_bug.cgi?id=121410

2) Are you setting the "difficulty" field?  I see it set in many of
the ones you were looking at.  We should actually leave that one
blank.  It is for the developers to use, to classify how hard the bug
is to fix.  QA doesn't touch that field.

3)  Did you look at this one:
https://issues.apache.org/ooo/show_bug.cgi?id=121440

In any case, I see that you understand the process, so rather than me
assigning you work,  I'd like you to self-assign some bugs to confirm.
 This will allow you to focus on areas of interest and be more
efficient.  For example, you can have a session where you only work on
spreadsheet bugs, rather than switching around applications on every
bug.

Here's what to do:

1) Start with this query in Bugzilla:
https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&namedcmd=unconfirmed-defects&list_id=42178

That has all unconfirmed bugs.

You can either pick from that list or edit the query to narrow it
down.  To edit go to the bottom and click the "edit search" button.
You might want to specify operating systems, products, etc.

2) Look for bugs that have an assignment of
issues@openoffice.apache.org, or *.openoffice.org or *.oracle.com.
Those are ones that no one is looking at.

3) Assign some interesting ones to yourself

4) Have fun

5) Post if you have any questions

Thanks!

-Rob