3,267
edits
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: − <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.''+ − + − ''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''+ − − ''A good "how to test" should answer these four questions:'' − − * ''What special hardware / data / etc. is needed (if any)? − * ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.? − * ''What specific actions do I perform to check that the feature is working like it's supposed to? − * ''What are the expected results of those actions?'' − -->
→How To Test
== How To Test ==
== How To Test ==
* you need several machines running sugar (or several sugar-jhbuild instances)
* run several instances, the buddy should be positioned the same on all the neighborhood views
* restart Sugar, the position should be the same as well
== User Experience ==
== User Experience ==