Tests/Activity/Terminal

Revision as of 17:19, 25 September 2008 by Kimquirk (Talk | contribs)

(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

Test case: Terminal Activity
How to report results

Stream	Any
Category	Activity	Sub-category	Terminal
Component	Terminal
Feature	http://wiki.laptop.org/go/Terminal
Objective	basic functional test
Tools	n/a
Setup	n/a
Procedure	# Activity installs from download (if not part of default installation) from website or USB key Activity starts up You can re-name the activity User specific data can be created You can force a save Activity closes properly from inside the activity You can resume the activity from the Journal You see the user specific data after resume You can close the activity from the Sugar frame
Expected Results and Pass Criteria	warning.pngEmpty strings are not accepted.
Comments	warning.pngEmpty strings are not accepted.

Release	Stream	Build	Pass/Fail	Trac Ticket(s)	Comment(s)	Date of Test
Candidate	8.2	763	Pass		terminal-18	warning.pngThe date "" was not understood (support for dates is still experimental).

Build number	763 +
Build stream	Any +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , and 8.2 +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride
Comments	terminal-18
Created	warning.pngThe date "" was not understood (support for dates is still experimental).
More notes	warning.pngEmpty strings are not accepted.
Pass criteria	warning.pngEmpty strings are not accepted.
PassFail	Pass +
Short name	Terminal Activity +
Software release	Candidate +
System component	Terminal +
System feature	http://wiki.laptop.org/go/Terminal +
Test category	Activity +
Test objective	basic functional test +
Test procedure	# Activity installs from download (if not … # Activity installs from download (if not part of default installation) from website or USB key Activity starts up You can re-name the activity User specific data can be created You can force a save Activity closes properly from inside the activity You can resume the activity from the Journal You see the user specific data after resume You can close the activity from the Sugar frame an close the activity from the Sugar frame
Test setup	n/a
Test subcategory	Terminal +
Test tools	n/a +