Tests/Activity/TuxPaint

From OLPC

< Tests
Revision as of 12:47, 23 September 2008 by 18.85.18.37 (Talk)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Test case: TuxPaint activity
How to report results

Stream 8.2, Any
Category Activity Sub-category Activities
Component Activity
Feature http://wiki.laptop.org/go/Tux_Paint
Objective Basic functional test of TuxPaint sugar api
Tools XO, internet connection
Setup Activity should be installed by downloading from the Activity page wiki page or from a USB key.
Procedure # Activity starts up
  1. You can re-name the activity
  2. User specific data can be created
  3. You can force a save
  4. Activity closes properly from inside the activity
  5. You can resume the activity from the Journal
  6. You see the user specific data after resume
  7. You can close the activity from the Sugar frame
Expected Results
and Pass Criteria 		Sugar related start, stop, resume, and save should work as expected.
Comments warning.pngEmpty strings are not accepted.
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test
Candidate 8.2 760 Fail Application functionality seemed fine, but lack of sugarized UI made test cases impossible to execute. Application cannot be renamed (no Activity menu), there is no Keep function (I could not find the multiple documents I saved using the application's Save button), and there is no Journal integration. At the moment we seem to pretty consistent in releasing apps with standard Sugar interface tools, and the lack of that interface is confusing for a user who otherwise is familiar with the XO. warning.pngThe date "" was not understood (support for dates is still experimental).


Facts about Tests/Activity/TuxPaintRDF feed
Build number 760  +
Build stream 8.2  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , and Any  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride
Comments Application functionality seemed fine, but … Application functionality seemed fine, but lack of sugarized UI made test cases impossible to execute. Application cannot be renamed (no Activity menu), there is no Keep function (I could not find the multiple documents I saved using the application's Save button), and there is no Journal integration. At the moment we seem to pretty consistent in releasing apps with standard Sugar interface tools, and the lack of that interface is confusing for a user who otherwise is familiar with the XO. ser who otherwise is familiar with the XO.
Created warning.pngThe date "" was not understood (support for dates is still experimental).
More notes warning.pngEmpty strings are not accepted.
Pass criteria Sugar related start, stop, resume, and save should work as expected.
PassFail Fail  +
Short name TuxPaint activity  +
Software release Candidate  +
System component Activity  +
System feature http://wiki.laptop.org/go/Tux_Paint  +
Test category Activity  +
Test objective Basic functional test of TuxPaint sugar api  +
Test procedure # Activity starts up
  1. You can re-name th … # Activity starts up
  2. You can re-name the activity
  3. User specific data can be created
  4. You can force a save
  5. Activity closes properly from inside the activity
  6. You can resume the activity from the Journal
  7. You see the user specific data after resume
  8. You can close the activity from the Sugar frame an close the activity from the Sugar frame
Test setup Activity should be installed by downloading from the Activity page wiki page or from a USB key.
Test subcategory Activities  +
Test tools XO, internet connection  +
Retrieved from "http://wiki.laptop.org/go/Tests/Activity/TuxPaint"
Personal tools
  • Log in / create account
  • Login with OpenID
About OLPC
About the XO
Projects
OLPC wiki
Toolbox