Tests/SmokeTest/NetworkConnections

From OLPC

< Tests
Revision as of 20:38, 29 January 2009 by Kimquirk (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Test case: Trying different connection types
How to report results

Stream Any
Category SmokeTest Sub-category Trying different connection types
Component warning.pngEmpty strings are not accepted.
Feature warning.pngEmpty strings are not accepted.
Objective Connect with a school server and confirm in terminal; connect to WPA, WPA2, WEP
Tools 2+ XO units, school server access
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 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
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 warning.pngEmpty strings are not accepted.
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test
Candidate 8.2 765 warning.pngEmpty strings are not accepted. not sure what to do as it was instructed to _not_ register with the school server for smoke tests. please advise. warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 766 Pass Cleaninstall gg-766-3.img; had to connect to xstest; connected; rebooted and it connected again to xstest. warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 767 Pass cleaninstall gg-767-4.img warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate staging 24 Pass #http://dev.laptop.org/ticket/9223 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. 2009/01/29


Facts about Tests/SmokeTest/NetworkConnectionsRDF feed
Build number 765  +, 766  +, 767  +, and 24  +
Build stream Any  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , 8.2  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , and Staging  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride
Comments not sure what to do as it was instructed to _not_ register with the school server for smoke tests. please advise., Cleaninstall gg-766-3.img; had to connect to xstest; connected; rebooted and it connected again to xstest., cleaninstall gg-767-4.img, and 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 warning.pngThe date "" was not understood (support for dates is still experimental). , and 29 January 2009  +
More notes warning.pngEmpty strings are not accepted.
Pass criteria Verify
  • The laptop connects to the sc 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. onnect and provide access to the internet.
PassFail warning.pngEmpty strings are not accepted. , and Pass  +
Short name Trying different connection types  +
Software release Candidate  +
System component warning.pngEmpty strings are not accepted.
System feature warning.pngEmpty strings are not accepted.
Test category SmokeTest  +
Test objective Connect with a school server and confirm in terminal; connect to WPA, WPA2, WEP  +
Test procedure Actions
  1. The laptop should boot up an Actions
  2. The laptop should boot up and connect to either simple mesh 1, or the last AP you were connected to before update
  3. 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
  4. If you did not automatically connect to the school server, go to the neighborhood view and click on the appropriate AP icon.
  5. 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
  6. Go to the mesh view (ctrl alt home and then mesh)
  7. Note the XO's you see -are they laptops around you, or ones most likely beyond the reach of the laptops wi-fi?
  8. 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 //wiki.laptop.org/go/Tests/Network/XO/WPA2
Test setup If you have done a cleaninstall, then you 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. ect to the school server when it boots up.
Test subcategory Trying different connection types  +
Test tools 2+ XO units, school server access  +
Trac bug number 9,223  +info.pngTrac ticket
Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox