Testing summary - Auckland New Zealand, 19 June 2010<br><br>Who - Tabitha, Tom, John, Fabiana, Leslie, Calvin, Nevyn, (Vinny and guest)<br>Purpose of the day was: test FreefromMalaria, test os260py, test os180py<br><br><br>
Tested FreeFromMalaria on os802b6. The activity is on a limited CC licence that may not allow local modifications? What does that mean for localisation? Can it be translated? Can you add local Malaria variations? On starting the activity you see a list of game controls that are not clickable, and after wondering what to do, eventually someone found the "lets play" in grey at the bottom of the screen. Felt a bit weird being a mosquito and one tester just couldn't do it, biting children. Would be good if you could click on the map of your country and see if it said yes or no malaria. Good adaption of a book. Its not so much a game, but an interactive story. I hope there can be more in a series of health interactive stories. <br>
<br>_____<br><br>Caught up with Vinny on Team OneBeep - with exams out of the way the team is back in full swing working on their software for radio data transmission and preparing for Imagine Cup in Poland. Wish them luck! <br>
<br>_____<br><br>Tested os260py build on 7 XOs<br><br><br>Memorize 34 shared but no one can see it in neighborhood, all on mesh 11. Tried shifting between views and found big delays. Stopped activity but it stays in my own neighborhood (still not appearing in others). Switched to local WiFi and we could then see the shared activities and we could play against each other (even those that had been put into the neighborhood prior to connecting to wifi). <br>
<br>Write 67 - Already open Write did not share in Mesh, even when moved to the WiFi, but quitting activity and starting a new share once in WiFi, share worked. Then the activity dropped off and quit on of the XO, and so the sharing dropped on the other two, after which we weren't able to share any more. The three XOs then quit all instances of write, and Moodle tried to start a new shared instance and we were able to share again. The default font size is really small. Doesn't go all the way across the screen. 100% is too small. <br>
<br>We found that if an activity is shared then closed, even if all players close the activity, it might not disappear from the neighbourhood view. <br><br>Speak 16 - tried some languages successfully. Wanted a language not listed - how do we add languages? <br>
<br>Created a network (didnt know we could do that on XO-1.0) and played two player Memorize 34 - cool :-)<br><br>Started these activities and successfully played on your own: Infoslicer 8, Implode 9, Paint 27, Physics 4, Turtle blocks 89, Speak 16, Labyrinth 9, TamTam Mini 52<br>
Started Browse 112 but not connected to the internet - default page was in spanish (as expected in paraguay build), need to test when connected<br>Cool new shut down screen :-)<br><br>point to frame gets no frame - we know this was done on purpose but we have learned behaviour from previous builds<br>
<br>Writing in AbiWord in Gnome - Found an option to save as Word Doc, opened in open office and table cells are incorrectly formatted. <br><br>We created an adhoc network, colaboration worked well in memorize. We had trouble disconnecting from the network once connected. We had some trouble cooridinating which network we would join. Twilight eventually left simba's network and created a new network. Tux joined twilight's network. Twilight joined moodle's network. Chaos.<br>
<br>We tried the resistive touch pad option and the result was "different" and probably better but not compellingly so.<br><br>Monkey's keyboard stopped working, everything else works, but without access to the frame in the corner of the screen i was unable to leave the nieghbourhood view, other than to join shared activities. ctrl-alt-f1 didn't work. Restarting fixed it.<br>
<br>XaoS activity doesn't seem well integrated with sugar. The menu doesn't have the normal sugar layout. After you quit, the launch pulser with the mandelbrot is still going and you have to wait for it to time out. Eventually you get a "XoaS failed to start" with a stop prompt. Inside XaoS, the frame key does not open the frame. The nieghbourhood, ring and activity view navigation keys work. The "Load Random Example" option from the file menu doesn't work -- it complains that it could not load the examples. It doesn't seem necessary to have two options off the quit in the file menu. This is previously reported I think. <br>
<br>Liked stopwatch and Measure in this build. <br><br><br>_____<br><br><br>Changed build - tested os180py.img<br><br>Had 6 XO-1.0s in Write 63 using a network created by an XO. We worked out we all had different colours. Could add a table and change font size. Could not change font colour.<br>
<br>Tried Record 66 but could not take photos or record audio.<br><br>Tried Memorize 34. Made own activity (counting in two languages with 6 pairs making 12 cards). Had 5 players in total, but first two to join had a conflict of whose turn, so one had to leave and rejoin then all 5 could play successfully. Played game through to conclusion successfully and then other players made new cards to learn other topics. This was a good opportunity for the testers to step more deeply into a learner role as they became the content creators and they decided the curriculum. One person wanted four cards the same, not two cards matching (he wanted to teach us math equivalents: 1/4, quarter, .25, 25/100) so he made four cards that all equalled the same but then when the others tried to play they felt that it was not fair, as they could see matching pairs on their screen but not win (e.g. match 1/4 and quarter or match .25 and 25/100, but that means 1/4 and 25/100 don't match) - after a conversation between participants, we took a moment to talk about the learning opportunity created. The other learners could give feedback to the "game maker" which helped them all learn. Another player "cheated" (his word, you could also call it a strategy) by using 2 XOs so he could learn the card places and win on one laptop. Interesting moments to observe, and not what I usually write in the testing feedback, but I felt it worth noting this today as it connects the tester and the learner, so I think makes for better testers. <br>
<br>Tried Distance test but too much noise interference in the cafe. <br><br>Had issues with disconnecting from the networks that we made but eventually we managed to get connected on just one. Sorry we didn't test this as I did not want to stop the learning and conversations that were happening at the time. <br>
<br><br><br>Thanks volunteers :-)<br><br>Tabitha<br>