Tests/SmokeTest/Chat: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(Add ad-hoc support, 11.2 tag)
 
Line 3: Line 3:
|testcase_category=SmokeTest
|testcase_category=SmokeTest
|testcase_subcategory=Collaboration with Chat
|testcase_subcategory=Collaboration with Chat
|testcase_stream=8.2.1, Any
|testcase_stream=8.2.1, 11.2, Any
|testcase_objective=Initiate a chat within your neighborhood
|testcase_objective=Initiate a chat within your neighborhood
|testcase_tools=2+ XO units
|testcase_tools=2+ XO units
|testcase_procedure=''Actions''
|testcase_procedure=''Actions''
# On both XO's click on the same mesh network
# On both XO's click on the same mesh (or ad-hoc) network
# Confirm that both units are on the same network
# Confirm that both units are on the same network
# Open chat with one XO
# Open chat with one XO
# Share the activity with the neighborhood
# Share the activity with the neighborhood
# Go to the Mesh view of that XO
# Go to the Network view of that XO
# Go to the Mesh view of the second XO
# Go to the Network view of the second XO
# In the mesh view of the second XO click on the chat activity that the first one just shared
# In the network view of the second XO click on the chat activity that the first one just shared
# Type a few lines in the chat activity on each XO
# Type a few lines in the chat activity on each XO
# Close the chat activity on both XOs
# Close the chat activity on both XOs
Line 20: Line 20:
# Follow the same steps, but starting with the second XO. (see that it works both ways)
# Follow the same steps, but starting with the second XO. (see that it works both ways)
|testcase_expectedresults=''Verify''
|testcase_expectedresults=''Verify''
* The shared chat activity shows up in the mesh view of both laptops
* The shared chat activity shows up in the network view of both laptops
* Whatever one laptop types in the chat window after both are connected is seen by both laptops
* Whatever one laptop types in the chat window after both are connected is seen by both laptops
* Chat works both ways and on all three networks
* Chat works both ways and on all three networks

Latest revision as of 19:37, 9 February 2011

Test case: Short name::Collaboration with Chat
How to report results

Stream ,|x|Build stream::x}}
Category Test category::SmokeTest Sub-category Test subcategory::Collaboration with Chat
Component System component::
Feature System feature::
Objective Test objective::Initiate a chat within your neighborhood
Tools Test tools::2+ XO units
Setup Test setup::
Procedure [[Test procedure::Actions
  1. On both XO's click on the same mesh (or ad-hoc) network
  2. Confirm that both units are on the same network
  3. Open chat with one XO
  4. Share the activity with the neighborhood
  5. Go to the Network view of that XO
  6. Go to the Network view of the second XO
  7. In the network view of the second XO click on the chat activity that the first one just shared
  8. Type a few lines in the chat activity on each XO
  9. Close the chat activity on both XOs
  10. Repeat the above steps, this time registered to the school server as the network
  11. Repeat a third time, connected to AP directly to Internet.
  12. Follow the same steps, but starting with the second XO. (see that it works both ways)]]
Expected Results
and Pass Criteria
[[Pass criteria::Verify
  • The shared chat activity shows up in the network view of both laptops
  • Whatever one laptop types in the chat window after both are connected is seen by both laptops
  • Chat works both ways and on all three networks]]
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::759 PassFail::Pass ,|x| #x}} Comments:: Created::


Software release::Candidate Build stream::8.2 Build number::760 PassFail::Pass ,|x| #x}} Comments:: Created::


Software release::Candidate Build stream::8.2 Build number::762 PassFail::Pass ,|x| #x}} Comments::but passes only for xstest school server. no other networks are supporting the chat (which is also prob an xo network issue) Created::


Software release::Candidate Build stream::8.2 Build number::765 PassFail::Pass ,|x| #x}} Comments::olpc-wep was able to chat with olpc-wpa, but neither could with canopy Created::


Software release::Candidate Build stream::8.2 Build number::765 PassFail::Pass ,|x| #x}} Comments::chat fine in ml1CC (the new media lab) Created::


Software release::Candidate Build stream::8.2 Build number::765 PassFail::Pass ,|x| #x}} Comments::chat fine in mesh channel 6 Created::


Software release::Candidate Build stream::8.2 Build number::766 PassFail::Pass ,|x| #x}} Comments::Chat fine with xstest school server and ml1cc, and both ways Created::


Software release::Candidate Build stream::8.2 Build number::766 PassFail::Pass ,|x| #x}} Comments::channel 6 works great, ml1CC works great Created::


Software release::Candidate Build stream::8.2 Build number::767 PassFail::Pass ,|x| #x}} Comments::used a usb upgraded XO from 656 to chat with a clean installed to 767 XO. worked fine on both ml1cc and mesh channel 11 Created::


Software release::Candidate Build stream::8.2 Build number::767 PassFail::Pass ,|x| #x}} Comments::using two XOs that were copy-nand clean installed with gg-767-4 on channel 6. after a slight hiccup in the chat, after reboot it worked fine. Created::


Software release::8.2.0 (767) Build stream::8.2 Build number::767 PassFail::Pass ,|x| #x}} Comments::smoke testing new firmware q2e21, worked fine on mesh channel 11. Created::2008/11/05


Software release::Candidate Build stream::8.2.1 Build number::24 PassFail::Pass ,|x| #x}} [[Comments::Firmware q2e29a, software os24.img

Worked both ways on mesh, on AP and on school server (both unregistered and registered)]]

Created::2009/01/29