Tests/Activity/Write/Public sharing: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(7 intermediate revisions by 3 users not shown)
Line 2: Line 2:
|testcase_name=Public Collaboration in Write
|testcase_name=Public Collaboration in Write
|testcase_category=Activity
|testcase_category=Activity
|testcase_subcategory=Write
|testcase_stream=Any
|testcase_stream=Any
|testcase_component=Write
|testcase_component=Write
|testcase_feature=http://wiki.laptop.org/go/Write#Collaboration
|testcase_feature=http://wiki.laptop.org/go/Write#Collaboration
|testcase_objective=Verify that several users can collaborate publickly with Write.
|testcase_objective=Verify that several users can collaborate publicly with Write.
|testcase_tools=None.
|testcase_tools=None.
|testcase_setup=Several XOs running the same version of Write.
|testcase_setup=Several XOs running the same version of Write.
Line 25: Line 26:
|testresult_stream=8.2
|testresult_stream=8.2
|testresult_build=757
|testresult_build=757
|testresult_passfail=Pass
|testresult_passfail=Fail
|testresult_tickets=8225
|testresult_tickets=8225, 8226, 8227
|testresult_comments=After of ~ 2 hours of running Chat, Record and Write on 10 laptops over the mesh network, Write (and only Write!) crashed (disappeared) in several machines (while Chat and Record were still running); one of the machines performed the Sugar's reset.
|testresult_comments=This test was performed using 30+ laptops connected to a school server with AP and running Chat and Browse, in addition to Write.


The same happened after 5+ hours of running Write (in combination with Chat and Browse) in the school server network (almost all the machines were affected).
While there were some problems (see the tickets), the result can be considered as "pass".

Also, in another running of the same test in the mesh network, Sugar suddenly restarted synchronously in several machines who joined Write before. It has happened when the other laptop joined sharing of Write.
}}
}}
{{Test results
{{Test results
|testresult_release=Candidate
|testresult_release=Candidate
|testresult_stream=8.2
|testresult_stream=8.2
|testresult_build=757
|testresult_build=763
|testresult_passfail=Fail
|testresult_passfail=Pass
|testresult_comments=shared write with 3 laptops on simple mesh... added text and pictures. After about 2 hours of continuous testing -- tamtam jam, shared chat and many other things, one of the write instances crashed. I went to the neighborhood view and clicked on the shared write icon and it started right up again where it left off.
|testresult_tickets=8226, 8227
|testresult_comments=After of ~ 2 hours of running Chat, Record and Write on 10 laptops over the mesh network, Write (and only Write!) crashed (disappeared) in several machines (while Chat and Record were still running); one of the machines performed the Sugar's reset.

Also, in another running of the same test, Sugar suddenly restarted synchronously in several machines who joined Write before. It has happened when the other laptop joined sharing of Write.
}}
}}
{{Test results end}}
{{Test results end}}

Latest revision as of 03:44, 25 September 2008

Test case: Short name::Public Collaboration in Write
How to report results

Stream ,|x|Build stream::x}}
Category Test category::Activity Sub-category Test subcategory::Write
Component System component::Write
Feature System feature::http://wiki.laptop.org/go/Write#Collaboration
Objective Test objective::Verify that several users can collaborate publicly with Write.
Tools Test tools::None.
Setup Test setup::Several XOs running the same version of Write.
Procedure [[Test procedure::
  1. Have laptops connected to the same school server or sharing the same channel over the mesh network.
  2. In one of the laptops, start the Write activity.
  3. While in the Write's window, click on the button "Activity" and choose "My neighborhood" in the "Share with" options window.
  4. Click on the "Text" button and type something.
  5. In the laptop that will share Write, go to the "Group" and see whether the Write's icon appears on the screen.
  6. Hover over the "Write Activity's icon and click on "join".
  7. The "Write" window should appear, showing the text transferred from the initiating machine.
  8. Type some text and check out whether it appears in the Write's window of the initiating machine.
  9. Repeat the steps 5 - 8 in other machines.]]
Expected Results
and Pass Criteria
Pass criteria::After the sharing of Write has been established, typing of text in any of the machine should have the same text appear in the Write's window of all other machines.
Comments More notes::
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test
Software release::Candidate Build stream::8.2 Build number::757 PassFail::Fail ,|x| #x}} [[Comments::After of ~ 2 hours of running Chat, Record and Write on 10 laptops over the mesh network, Write (and only Write!) crashed (disappeared) in several machines (while Chat and Record were still running); one of the machines performed the Sugar's reset.

The same happened after 5+ hours of running Write (in combination with Chat and Browse) in the school server network (almost all the machines were affected).

Also, in another running of the same test in the mesh network, Sugar suddenly restarted synchronously in several machines who joined Write before. It has happened when the other laptop joined sharing of Write.]]

Created::


Software release::Candidate Build stream::8.2 Build number::763 PassFail::Pass ,|x| #x}} [[Comments::shared write with 3 laptops on simple mesh... added text and pictures. After about 2 hours of continuous testing -- tamtam jam, shared chat and many other things, one of the write instances crashed. I went to the neighborhood view and clicked on the shared write icon and it started right up again where it left off.]] Created::