[Testing] Fwd: Testing summary - 15 November 2008 Wellington testers

[Caryl Bigenho]

Hi All...

As a NuB tester (and retired teacher) I am also interested in seeing the testing process made easier for new recruits.  Yesterday, while working on a Handy Testing Template for NuBs.  I looked at "Tests/Activity/Analyze" and "Tests/Activity/TamTamEdit." 
The former is much more user-friendly  than the latter which is like the one you listed for for (	http://wiki.laptop.org/go/Tests/Activity/Moon).  The one for Analyze is much more detailed and helpful, and does the exact same thing.  The one
for TamTamEdit assumes you know how to do all the things it is asking
you to do.  I suggest we could edit all of them to match the Basic test for Analyze and make it easier for folks to do the "Basic" test.

BTW, I experimented and found that if I simply used (http://wiki.laptop.org/go/Tests/NameOfActivity) where you fill in the Activity you want to test, you can apparantly go to the test for any activity. I didn't test to see if all are covered, but the 5 or 6 I tried were.

Caryl

> From: gary at garycmartin.com
> To: tabitha.mail at gmail.com
> Date: Sat, 15 Nov 2008 17:16:21 +0000
> CC: testing at lists.laptop.org
> Subject: Re: [Testing] Fwd: Testing summary - 15 November 2008 Wellington	testers
> 
> Hi all,
> 
> On 15 Nov 2008, at 07:14, Tabitha Roder wrote:
> 
> > Moon-8 (Edward led test)
> > Wiki page exists and has good description of the activity. Has  
> > screenshots. Behaviour matches description.
> > Test page exists.
> > Rotate screen function does not display correctly on 90 degree and  
> > 270 degree turn - moon has sides chopped off, though text does  
> > display in full. Does display correctly at 180 degree turn.
> > Feature request - change date function would rock.
> > Ticket #8992 created for rotate function.
> 
> Fab, thanks for the testing :-) I've owned the trac ticket, and added  
> your feature request to the Moon wiki page so I can keep track.
> 
> -- snip -- snip --
> 
> > General comments:
> > Multiple collaboration side of activities does not appear to be  
> > stress tested.
> 
> Yep agreed. I've long thought the big issue here is that developers  
> don't usually have access multiple XOs for testing with, and if they  
> do it's a rare occasion. There are even developers out there trying to  
> work with zero access to an XO, so they can never directly check  
> things like screen size layout, screen rotation, monochrome mode, mesh  
> networking, memory usage, cpu load, power saving, keyboard/game-pad  
> layout! Personally, as a developer, I've avoided collaboration  
> features as I could not reliably test and debug them myself on one XO- 
> B4 (I now have 3 XOs, so that will change).
> 
> > We need a better list of generic things to be tested on each  
> > activity... e.g. rotation, black and white mode, collaborate enabled/ 
> > disabled (if not collaboration enabled then should not be able to  
> > share with neighbourhood), game key functionality, keep/save, re- 
> > enter activity from journal (and state) and re-enter activity from  
> > frame, invite vs join. Separate collaboration tests - simple mesh,  
> > school server, ad hoc network, access point. Test - does this  
> > activity have sound and does it work? Does this activity use webcam  
> > and does it work?
> > How do we test the activity cleanly releases resources (like sound,  
> > webcam).  Run all tests from a clean boot - i.e. the only activity  
> > run since restart. Also we should test how an activity impacts on  
> > other subsequent activities. Run all tests on two XOs if possible  
> > and note XO names (in case hardware differences).
> 
> All v.good stuff! :-)
> 
> > Less pages on the wiki would be easier for newbies. It is hard to  
> > work out what to test and which page to update when there are many.
> 
> Newbies? For us oldbies also! I've only just discovered:
> 
> 	http://wiki.laptop.org/go/Tests/Activity/Moon
> 
> I'd a faint idea there may be one somewhere, but I could never dig up  
> anything authoritative. I've added a link there from the Moon wiki  
> page, I should go work out how to create some extra test cases.
> 
> One general action item (Mel) would be to make sure Testing has a good  
> SINGLE landing page that links and/or describes the authoritative  
> locations and work going on – currently it seems some new set of  
> Testing resource wiki leaf pages appearing every week and it's hard to  
> keep track. The tree should only be a couple of branches deep at most  
> to keep things clear.
> 
> > Ideas on building test/develop relationship:
> > In the community testing meeting can we ascertain who is a tester  
> > and who is a developer at the start of the meeting - it would be  
> > good if both there and mix/mingle a bit.
> 
> Me, me, (puts both hands up) ;-)
> 
> > Thanks to Alastair Munro, Edward Munro, Grant Patterson and Carl  
> > Klitscher for there testing efforts today. If anyone is free please  
> > join the community testing meeting IRC on Friday 11am NZ time.  
> > Details are found at http://wiki.laptop.org/go/Community_testing_meeting 
> > .
> 
> Thanks everyone – I have to say this is the best single chunk of  
> Activity testing effort I've seen in the last 11 months! That's both  
> very sad, and exciting that we may finally be passing some tipping  
> point.
> 
> Ponies all round!
> 
> Regards,
> --Gary
> 
> P.S. Mel, dragon at the ready? ;-)
> 
> > Until next Saturday!
> >
> > Tabitha Roder
> > (64)21482229
> > tabitha.mail at gmail.com
> 
> _______________________________________________
> Testing mailing list
> Testing at lists.laptop.org
> http://lists.laptop.org/listinfo/testing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/testing/attachments/20081115/48583d1d/attachment.htm