[Systers-dev] GSoC Test Cycles 3 and 4

Sat Aug 15 08:39:58 PDT 2009

You are going to have to ask more specific questions, as I can't tell what
kind of answer would be helpful.  This is all manual testing.  Have you even
gone to the page you are being asked to test and looked at that page?  You
go to the page, do the actions shown in the test, check against the expected
behavior and report success or failure.
If the above was clear to you, I assume that the specific instructions for
one of the tests was confusing.  But you are going to have to ask really
specific questions for us to help you.

While there are certainly things you could do to set us back several days,
this is a development server, and things you do won't break things for
"real" users.  You should be willing to explore things.  If you haven't
visited the page you are going to test and tried to match what you see there
with what you are being expected to test, you aren't ready to get started.
 (and there were 'hints' in my original message that will be important to
reread at that point.

I'm going off for an errand and should be back about 11 (Pacific time)

Robin

On Fri, Aug 14, 2009 at 10:35 PM, P. A. Grubel <pagrubel at tularosa.net>wrote:

> I did read through the background and then the checklist. I then went to a
> few of the bugs but have no idea how I would test anything. I am probably
> going to need some hand holding or more sleep. I just don't see how you are
> testing things. I'll look at it again tomorrow. Okay so I'm really rusty.
>
> Pat
>
>
>
>  _____
>
> From: Robin Jeffries [mailto:robin at jeffries.org]
> Sent: Wednesday, August 12, 2009 9:16 PM
> To: P. A. Grubel
> Cc: systers-dev+cycles at systers.org <systers-dev%2Bcycles at systers.org>
> Subject: Re: [Systers-dev] GSoC Test Cycles 3 and 4
>
>
>
> Sure, I am about to start some testing (though Anna has really done the
> lion's share of the testing already for this round, but you would get
> familiar for other rounds).
>
>
>
> I'm posting this to the list so it will inspire others to try.  It's really
> not that hard.  And you can send me, anna (anna.granudd at gmail.com) or Jen
> (jenred at gmail.com) email and one of us will answer (Anna is in Sweden, so
> she's most useful in the morning or if you are a night owl).
>
>
>
> First, to get started and understand the background of our custom mailman,
> I
> suggest you read
>
> http://systers.org/systers-dev/doku.php/good_to_know
>
>
>
> At some point you should also read the pages here
> http://systers.org/systers-dev/doku.php/general_how_stuff_works  but I
> think
> you can do the testing we need for this cycle without that info.
>
>
>
> This is the template/checklist for this release
> http://systers.org/systers-dev/doku.php/checklist_for_wishlist_integration
>
>
>
> To be able to update the page (which in their raw form are rather funky,
> but
> it shouldn't be too hard to figure out which is the place you want to enter
> your name, whether the test passed, etc. -- just ask if it's too weird for
> you) you need an account.  Click on the login link at the bottom of the
> page, and then register to create an account.
>
>
>
> We do our testing on abiwt.org  Anna has created a list called wishlist
> which we will use to do most of the testing.  you access that at
> www.abiwt.org/mailman/listinfo/wishlist.  The first thing you want to do
> is
> to join the list (But see below; maybe not given what I am assigning you).
> It should look very similar to what you did when you joined systers.  It's
> probably useful to join under a couple of email addresses (as different
> people), so that you can see what happens as a sender and also a receiver
> of
> the same message.
>
>
>
> Some things you may need to be admin for.  The admin password is admin.
>  (it
> sometimes asks for it twice.  It's a bug we haven't tracked down yet)
>
>
>
> If you can do the set of tests under membership management page, that would
> be great.  that page is
>
> www.abiwt.org/mailman/admin/wishlist and click on membership management in
> the navigation in the top left.  Some of the instructions and the
> signifiers
> that it passed may be a little too terse.  Just ask us.  This one starts
> with mass subscription, so depending on how many email addresses you have
> access to (you might ask your spouse/kids/roommates if you can use them, as
> you will just delete them a few steps later), you might not want to
> subscribe to the list at all and use the mass subscribe to get yourself
> subscribed.
>
>  the places where it asks you to do a "moderator activity", go to the admin
> page listed above, and click on tend to pending moderator requests (top
> right).  It's usually obvious what to do.  Remember, this list exists for
> testing purposes only, so if you mess up, you will just run the test again
> (worse case, if you do something disastrous, we'll create another list).
>
>
>
> When you finish a test, fill out that line in the wiki (after logging in,
> click on edit page).  We want your email to know who did the test, and the
> time, preferably in UTC so that we can check the logs and see if there was
> some invisible problem. P/F for pass/fail should be obvious.  Comments are
> for when it failed, what happened that made you think it failed (send me an
> email the first time that happens, and I will show you how to file a bug
> for
> it, but for now just put it into this document. ) It's OK to put "X
> happened, bt it wasn't clear to me whether that was supposed to or not" and
> someone else can fill in P or F.
>
>
>
> I think that will be enough to get you started.  I'll be online for another
> hour doing my testing, so if you start now I can answer your first couple
> rounds of questions.
>
>
>
> Robin
>
>
>
> On Wed, Aug 12, 2009 at 7:16 PM, P. A. Grubel <pagrubel at tularosa.net>
> wrote:
>
>
> I haven't helped at all because I have been gone but am willing to help on
> something. Is there anything I can come up to speed on and do for you.
> Pat
>
>
>
>
>
> To unsubscribe from this conversation, send email to
> <systers-dev+cycles+unsubscribe at systers.org<systers-dev%2Bcycles%2Bunsubscribe at systers.org>
> <mailto:systers-dev%2Bcycles%2Bunsubscribe at systers.org<systers-dev%252Bcycles%252Bunsubscribe at systers.org>>
> > or visit
> <http://systers.org/mailman/options/systers-dev?override=29
> <http://systers.org/mailman/options/systers-dev?override=29&preference=0>
> &preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to systers-dev+cycles at systers.org<systers-dev%2Bcycles at systers.org>
> <mailto:systers-dev%2Bcycles at systers.org<systers-dev%252Bcycles at systers.org>
> >
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> <mailto:systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>> >
> To unsubscribe entirely from systers-dev, send email to
> <systers-dev-request at systers.org> with subject unsubscribe.
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.392 / Virus Database: 270.13.52/2298 - Release Date: 08/12/09
> 06:09:00
>
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+cycles+unsubscribe at systers.org<systers-dev%2Bcycles%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=29&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to systers-dev+cycles at systers.org<systers-dev%2Bcycles at systers.org>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> >
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>