Tests/SmokeTest/NetworkConnections: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
|testcase_subcategory=Trying different connection types
|testcase_subcategory=Trying different connection types
|testcase_stream=Any
|testcase_stream=Any
|testcase_objective=Connect with a school server and confirm in terminal
|testcase_objective=Connect with a school server and confirm in terminal; connect to WPA, WPA2, WEP
|testcase_tools=2+ XO units, school server access
|testcase_tools=2+ XO units, school server access
|testcase_setup=If you have done a cleaninstall, then you will not automatically connect to a school server.
|testcase_setup=If you have done a cleaninstall, then you will not automatically connect to a school server.
Line 20: Line 20:
# Note the XO's you see -are they laptops around you, or ones most likely beyond the reach of the laptops wi-fi?
# Note the XO's you see -are they laptops around you, or ones most likely beyond the reach of the laptops wi-fi?
# Do the same with a second or third laptop to ensure that it's in the same configuration
# Do the same with a second or third laptop to ensure that it's in the same configuration

# http://wiki.laptop.org/go/Tests/Network/XO/WEP
# http://wiki.laptop.org/go/Tests/Network/XO/WPA
# http://wiki.laptop.org/go/Tests/Network/XO/WPA2
|testcase_expectedresults=''Verify''
|testcase_expectedresults=''Verify''
* The laptop connects to the school server by default after reboot
* The laptop connects to the school server by default after reboot
Line 35: Line 39:
* If you're running gabble, you see laptops connected to the same jabber server
* If you're running gabble, you see laptops connected to the same jabber server
* NOTE: laptops running gabble cannot see laptops running salut and vise-versa
* NOTE: laptops running gabble cannot see laptops running salut and vise-versa

* WPA, WPA2, and WEP should all connect and provide access to the internet.
}}
}}
{{Test results begin}}
{{Test results begin}}
Line 49: Line 55:
|testresult_passfail=Pass
|testresult_passfail=Pass
|testresult_comments=Cleaninstall gg-766-3.img; had to connect to xstest; connected; rebooted and it connected again to xstest.
|testresult_comments=Cleaninstall gg-766-3.img; had to connect to xstest; connected; rebooted and it connected again to xstest.
}}
{{Test results
|testresult_release=Candidate
|testresult_stream=8.2
|testresult_build=767
|testresult_passfail=Pass
|testresult_comments=cleaninstall gg-767-4.img
}}
{{Test results
|testresult_release=Candidate
|testresult_stream=staging
|testresult_build=24
|testresult_passfail=Pass
|testresult_tickets=http://dev.laptop.org/ticket/9223
|testresult_comments=Started with a cleaninstall. Connected to school server AP; registered properly; also connected to WEP, WPA, and WPA2 access points. They all connected eventually, but sometimes I had to initiate the association multiple times.
|testresult_date=2009/01/29
}}
}}
{{Test results end}}
{{Test results end}}

Latest revision as of 20:38, 29 January 2009

Test case: Short name::Trying different connection types
How to report results

Stream ,|x|Build stream::x}}
Category Test category::SmokeTest Sub-category Test subcategory::Trying different connection types
Component System component::
Feature System feature::
Objective Test objective::Connect with a school server and confirm in terminal; connect to WPA, WPA2, WEP
Tools Test tools::2+ XO units, school server access
Setup [[Test setup::If you have done a cleaninstall, then you will not automatically connect to a school server.

If you have done an 'olpc-upgrade'; and you had been connected to the school server, then you should automatically connect to the school server when it boots up.]]

Procedure [[Test procedure::Actions
  1. The laptop should boot up and connect to either simple mesh 1, or the last AP you were connected to before update
  2. Wait for the circle to stop blinking (in older builds the outer circle goes white to show successful connection, later builds show parentheses to indicate connection) and hover your cursor to ensure connection
  3. If you did not automatically connect to the school server, go to the neighborhood view and click on the appropriate AP icon.
  4. If you needed to connect to the school server, then go to the home screen and register with the school server.
    • To check your connection, go to terminal one (ctrl alt mesh)
    • At the login, type "root", and then type olpc-netstatus (for newer build, type "olpc" instead of "root")
    • Note whether the result of Telepathy/Jabber is salut or gabble
  5. Go to the mesh view (ctrl alt home and then mesh)
  6. Note the XO's you see -are they laptops around you, or ones most likely beyond the reach of the laptops wi-fi?
  7. Do the same with a second or third laptop to ensure that it's in the same configuration
  1. http://wiki.laptop.org/go/Tests/Network/XO/WEP
  2. http://wiki.laptop.org/go/Tests/Network/XO/WPA
  3. http://wiki.laptop.org/go/Tests/Network/XO/WPA2]]
Expected Results
and Pass Criteria 		[[Pass criteria::Verify
  • The laptop connects to the school server by default after reboot
  • (alternatively) The laptop connects to the school server if you click on its portal point in the mesh view
  • The result of running olpc-netstatus is:
    • IP msh0 :
      • 172.x.x.x(172.18.x.x when connected to the School server in OLPC offices)
      • 192.168.x.x
      • 10.x.x.x
    • Config : School server
    • Telepathy/Jabber :
      • salut (means failure to connect to a jabber server
      • gabble (then the result of Jabber is : {name of jabber server you're connected to}
  • If you're running salut, you only see laptops that are around you and also connected to the same server
  • If you're running gabble, you see laptops connected to the same jabber server
  • NOTE: laptops running gabble cannot see laptops running salut and vise-versa
  • WPA, WPA2, and WEP should all connect and provide access to the internet.]]
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::765 PassFail:: ,|x| #x}} Comments::not sure what to do as it was instructed to _not_ register with the school server for smoke tests. please advise. Created::


Software release::Candidate Build stream::8.2 Build number::766 PassFail::Pass ,|x| #x}} Comments::Cleaninstall gg-766-3.img; had to connect to xstest; connected; rebooted and it connected again to xstest. Created::


Software release::Candidate Build stream::8.2 Build number::767 PassFail::Pass ,|x| #x}} Comments::cleaninstall gg-767-4.img Created::


Software release::Candidate Build stream::staging Build number::24 PassFail::Pass ,|x| #x}} Comments::Started with a cleaninstall. Connected to school server AP; registered properly; also connected to WEP, WPA, and WPA2 access points. They all connected eventually, but sometimes I had to initiate the association multiple times. Created::2009/01/29


Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Tests/SmokeTest/NetworkConnections&oldid=193720"