Test Case

Show / Hide direct link   <ROOT> 4897PA: =ROOT==Obsolete=Google Chrome Network team items - PP-80462



Version 1.4
Created on 04/07/2012 10:54:16  by PSI_PA_NW_Japan
Last modified on  10/06/2016 18:52:51  by m_komatsu_nw
Summary
Preconditions
Status:   New
Priority:   Medium
BASIC INFORMATION
Section:S/W Test Require attachment:No
Team:Network Group:Basic Function
Lessons Learned:No Phase:FVT, SIT
Locations:Inhouse: AWS and Cambridge, Inhouse: AWS, Inhouse: Cambridge, Compal, Flextronics, Quanta, Wistron Owned By:Eiji Ogata/LENOVO
Objective:To verify the Network functions under Google Chrome OS
CRITERIA

All network functions to work correctly

No system performance degradation / system malfunction

EUT QUANTITY

Two systems

EQUIPMENT

PA Networking facilities including wireless security environment

Critical Attribute:[0] : WLS - Wireless

CONFIGURATION
REFERENCE PROCEDURE
STATISTIC INFO
Operating System Chrome OS Total
Test Points
Duration
Workload
# Step actions Chrome OS
1 Ethernet Verification A
2 Wireless LAN Verification A
3 Wireless Security Verification A
4 Power Management (WLAN/Ethernet) A
5 Wireless WAN Verification A
6 Power Management (WWAN) A
DETAILS
ATTENTION!! Please follow below information.
1. Please check Error and Warning message in Event Viewer before you start the test case and after you complete the test case, and report it to your team lead, then arrange to open defect, if needed.

2. Perform All Test in Battery Mode (Some of the test items need to perform in AC Mode, follow each Test Case).

3. All Test Activity should be performed with AMT Enabled as Default (applicable on vPro enabled systems).

4. Please check Usability / Cosmetic issues (correct sentence/appropriate display/etc.) and open defect, if needed.

Ethernet Function Basic Functions

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
Basic Function Verification
Connecting to a Wired Network

1. Attach wired cable into machine's ethernet port.

2. From lower right portion of Chrome Desktop (taskbar), click taskbar.

3. Confirm Connected to Ethernet is shown.

  • Ethernet profile should be connected successfully without any errors.
  • Confirm IP address and Ethernet MAC address are listed after clicking information icon (if network icon is disabled)
Stand alone
A

Wireless Security Certificate Download [UR-03501AP]

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
Connection to Server
Connecting to a Wired Security Network

1. Attach wired cable to Security Network

2. From lower right portion of Chrome Desktop (taskbar), click taskbar.

3. Confirm Connected to Ethernet is shown.

4. Go to browser Ctrl+Alt+T to display crosh

5. ping the server's IP address

  • Ethernet profile should be connected successfully without any errors.
  • Confirm IP address and Ethernet MAC address are listed after clicking information icon (if network icon is disabled)
  • Ping on Server's IP address should be successful
Stand alone
A
Connecting to a Wired Network1. Make sure that ethernet is connected

2. go to browser> enter address/cert/srv

(e.g. 192.168.10.1/cert/srv)

3. Then download server certificate

Server certificate installation:

To install your user certificate after you've downloaded it, follow the steps below.

1. In a new tab, enterchrome://settings/certificatesinto your browser's address bar.

2. Click theYour Certificatestab.

3. If you have a .pfx or .p12 file to import, click theImport and Bind to Devicebutton.

4. In the dialog box that opens, select the certificate file and clickOpen.

5. When prompted, enter the password for your certificate. If you don't know the password,

contact your network administrator.

6. The certificate will open and install itself on your Chrome device.

To install your server certificate authority after you've downloaded it, follow the steps below.

1. In a new tab, enterchrome://settings/certificatesinto your browser's address bar.

2. Click theAuthoritiestab.

3. Press theImportbutton and choose the certificate authority file, which is usually a

file with a .pem, .der, .crt, or .p7b extension.

4. In the dialog that appears, fill out the information on how this certificate authority should

be trusted.

5. The certificate will open and install itself on your Chrome device.

  • Downloading of Server certificate should be successful
  • The downloaded certificate should be successfully installed not corrupted
Stand alone
A

File Upload / Download using Wired Network

TEST ITEM
Result
Chrome OS
File Download
TCP/IP (Static IP)

1. Attach wired cable into machine's ethernet port.

2. From lower right portion of Chrome Desktop (taskbar), click taskbar.

3. Confirm Connected to Ethernet is shown.

4. Click Connected to Ethernet

5. Click Ethernet

6. Browser will show with Ethernet details.

7. In Network tab, choose Use static IP.

8. Enter the following:

- IP Address

- Subnet mask

- Gateway

- DNS server

9. Click Close

10. Download files using ftp (>300MB files)

TCP/IP (DHCP)

1. Attach wired cable into machine's ethernet port.

2. From lower right portion of Chrome Desktop (taskbar), click taskbar.

3. Confirm Connected to Ethernet is shown.

4. Click Connected to Ethernet

5. Click Ethernet

6. Browser will show with Ethernet details.

7. In Network tab, choose Use DHCP, click Close.

8. Download files using ftp (>300MB files)

A
File Upload
TCP/IP (Static IP)

1. Attach wired cable into machine's ethernet port.

2. From lower right portion of Chrome Desktop (taskbar), click taskbar.

3. Confirm Connected to Ethernet is shown.

4. Click Connected to Ethernet

5. Click Ethernet

6. Browser will show with Ethernet details.

7. In Network tab, choose Use static IP.

8. Enter the following:

- IP Address

- Subnet mask

- Gateway

- DNS server

9. Click Close

10. Upload files using ftp (>300MB files)

TCP/IP (DHCP)

1. Attach wired cable into machine's ethernet port.

2. From lower right portion of Chrome Desktop (taskbar), click taskbar.

3. Confirm Connected to Ethernet is shown.

4. Click Connected to Ethernet

5. Click Ethernet

6. Browser will show with Ethernet details.

7. In Network tab, choose Use DHCP, click Close.

8. Upload files using ftp (>300MB files)

A
File Upload and Download Simultaneously
  1. Connect Chrome machine to a Wired network.
  2. Make sure the profile gets connected successfully.
  3. Connect to an FTP site and upload a 100 MB file
  4. Meanwhile start downloading a file greater than 100MB from the website.
  5. Confirm the uploading and downloading proceeds simultaneously.
  6. Make sure files are uploaded and downloaded successfully without any error message.
  7. Make sure there is no connection drop at any point of time during upload and download.
A

Wireless Function Basic Functions

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
Installation / Configuration
Chrome - Wi-Fi Enabled

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Confirm that network icon beside Network section is not striked out.

4. Available WLAN profiles will show.

5. Select the correct Access point and configure the same with SSID, Encryption, etc.

  • WLAN profiles should be shown and can be connected without errors
  • Confirm IP address, Ethernet and WiFi MAC address is listed after clicking information icon (beside network icon)
Stand alone
A
Chrome - WiFi Disabled From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Click network icon beside Network section. It should be striked out.

4. No Access Points should be available.

5. Wi-Fi button should be disabled.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Confirm that network icon is striked out.

4. Click Settings button.

5. Browser will show.

6. Confirm under Internet Connection portion, Wi-Fi network is Disabled.

  • WLAN profiles should not be shown and cannot be connected without errors.
  • Wi-Fi button should be disabled in Desktop and Browser.
Stand alone
A
Basic Function Verification
Connecting to a Wi-Fi NetworkFrom Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Check if Wi-Fi is ON. (Network Icon is not striked out)

4. Available WLAN profiles will show.

5. Select the available access point and connect. Enter password and other credentials if prompted.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Available WLAN profiles will show.

8. Select the available access point and connect. Enter password and other credentials if prompted.

  • WLAN profile should be connected successfully without any errors.
  • Confirm IP address, Ethernet and WiFi MAC addresses are listed after clicking information icon (beside network icon)
Stand alone
A
Modify a Wi-Fi Network1. Click the status area in the lower right corner of the desktop, where your account picture appears.

2. Select Settings and Help.

3. Under Internet Connection section > click Wireless Network menu. (Make sure WLAN profile is connected)

4. Select Network options.

5. Check the Automatically connect to this network.

6. Click Close.

  • Confirm that wireless profile will auto-connect after pm functions.
  • Confirm that wireless profile details shown correct in Connection tab.
Stand alone
A
Forget a Wi-Fi Network1. Click the status area in the lower right corner of the desktop, where your account picture appears.

2. Select Settings and Help.

3. Under Internet Connection section > click Wireless Network menu.

4. Select Preferred networks

5. Mouse hover the saved wireless profile and click X.

  • Confirm that wireless profile will not connect after deleting the saved profile.
Stand alone
A
Making a Preferred Network - UR35601. Click the status area in the lower right corner of the desktop, where your account picture appears and select settings

3.Click on Add Connection>Add Wifi>Add your wireless network and connect

4. After connecting click again on Wi-Fi network and select Preferred networks.

5.Select now the recently created profile as a preferred network.

Note:

It’s not possible to specify an order of connection preference among multiple wireless networks.

Bug ID: 13658

  • Confirm that wireless profile should connect after selecting it as a preferred network
Stand alone
A
Connect and Disconnect a Wireless Profile

1. In a new tab, enter chrome://settings/ into your browser's address bar.

2. Add connection>Add Wifi>Put the SSID and Password

3. Connect the profile> Establish a successful connection4. Verify the connection status (e.g. crosh>ping [website])

5. Put system into Sleep/S3 (lid close) then resume after 1-2 minutes

6. Verify the connection status (e.g. crosh>ping [website])

7. Go to settings>Internet Connection> Wi-Fi network

8. Choose your connected network>Disconnect

Reference:

Issue 13646:Stout:JettChromeSIT1:System restarts when network disconnect after sleep

Issue 13415: Stout: JettChromeSIT1:Wireless network with WPA2 authentication won't establish a connection

  • Connection and disconnection should not affect any of the ongoing session
  • Connections should be stable after PM (internet browsing)
Stand alone
A
Invalid Profile for wireless network

1. In a new tab, enter chrome://settings/ into your browser's address bar.

2. Add connection>Add Wifi>Put the invalid SSID and Password

3. Connect the profile> the profile should not connect

4. Go to Wireless Status icon>click on the profile connection

Reference:

Issue 23807:If the SSID is inavlid while we join "Other Wi-Fi network", connect fails but network is remembered

  • Invalid profile (SSID) should not be saved
Stand alone
A

File Upload / Download using Wi-Fi Network

TEST ITEM
Result
Chrome OS
File Download
TCP/IP

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Check if Wi-Fi is ON. (Network Icon is not striked out)

4. Available WLAN profiles will show.

5. Select the available access point and connect. Enter password and other credentials if prompted.

6. Download files using ftp (>300MB files)

A
File Upload
TCP/IP

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Check if Wi-Fi is ON. (Network Icon is not striked out)

4. Available WLAN profiles will show.

5. Select the available access point and connect. Enter password and other credentials if prompted.

6. Upload files using ftp (>300MB files)

A
File Upload and Download Simultaneously
  1. Connect Chrome machine to a Wi-Fi network.
  2. Make sure the profile gets connected successfully.
  3. Connect to an FTP site and upload a 100 MB file
  4. Meanwhile start downloading a file greater than 100MB from the website.
  5. Confirm the uploading and downloading proceeds simultaneously.
  6. Make sure files are uploaded and downloaded successfully without any error message.
  7. Make sure there is no connection drop at any point of time during upload and download.
A

Wireless Security Results

Test Item
Check Item / Criteria
Chrome OS
No WEP
Standalone
A
WEP
Standalone
A
PSK (WPA or RSN)
Standalone
A
LEAP
Standalone
A
PEAP
Standalone
A
EAP-TLS
Standalone
A
EAP-TTLS
Standalone
A

Wireless Security Basic Functions

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
Configuring Wireless for NoWEP

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Wi-Fi button.

5. Enter SSID.

7. Choose None in Security drop down box.

6. Click Connect.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Enter SSID.

8. Choose None in Security drop down box.

9. Click Connect.

  • Make sure connection is successful without any error
  • Should connect after performing PM scenarios
Stand alone
A
Configuring Wireless for WEP

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Wi-Fi button.

5. Enter SSID.

7. Choose WEP in Security drop down box.

8. Enter password.

9. Click Connect.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Enter SSID.

8. Choose WEP in Security drop down box.

9. Enter password.

10. Click Connect.

Perform PM scenarios 5 times each(Shutdown,Restart,Lid Close

  • Make sure connection is successful without any error
  • Should connect after performing PM scenarios
Stand alone
A
Configuring Wireless for PSK (WPA or RSN)

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Wi-Fi button.

5. Enter SSID.

7. Choose PSK (WPA or RSN) in Security drop down box.

8. Enter password.

9. Click Connect.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Enter SSID.

8. Choose PSK (WPA or RSN) in Security drop down box.

9. Enter password.

10. Click Connect.

Perform PM scenarios 5 times each(Shutdown,Restart,Lid Close

  • Make sure connection is successful without any error
  • Should connect after performing PM scenarios
Stand alone
A
Configuring Wireless for LEAP

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Wi-Fi button.

5. Click Advanced button.

6. Enter SSID.

7. Choose LEAP in EAP Method drop down box.

8. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

9. Click Save identity and password, if you want to save user credentials

10. Click Share this network with other users, if you want to share internet connectivity to other users.

11. Click Connect.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Click Advanced button.

8. Enter SSID.

9. Choose LEAP in EAP Method drop down box.

10. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

10. Click Save identity and password, if you want to save user credentials

11. Click Share this network with other users, if you want to share internet connectivity to other users.

12. Click Connect.

Perform PM scenarios 5 times each(Shutdown,Restart,Lid Close

  • Make sure connection is successful without any error
  • Should connect after performing PM scenarios
Stand alone
A
Configuring Wireless for PEAP

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Wi-Fi button.

5. Click Advanced button.

6. Enter SSID.

7. Choose PEAP in EAP Method drop down box.

8. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

9. Click Save identity and password, if you want to save user credentials

10. Click Share this network with other users, if you want to share internet connectivity to other users.

11. Click Connect.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Click Advanced button.

8. Enter SSID.

9. Choose PEAP in EAP Method drop down box.

10. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

10. Click Save identity and password, if you want to save user credentials

11. Click Share this network with other users, if you want to share internet connectivity to other users.

12. Click Connect.

Perform PM scenarios 5 times each(Shutdown,Restart,Lid Close

  • Make sure connection is successful without any error
  • Should connect after performing PM scenarios
Stand alone
A
Configuring Wireless for EAP-TLS

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Wi-Fi button.

5. Click Advanced button.

6. Enter SSID.

7. Choose EAP-TLS in EAP Method drop down box.

8. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

9. Click Save identity and password, if you want to save user credentials

10. Click Share this network with other users, if you want to share internet connectivity to other users.

11. Click Connect.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Click Advanced button.

8. Enter SSID.

9. Choose EAP-TLS in EAP Method drop down box.

10. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

10. Click Save identity and password, if you want to save user credentials

11. Click Share this network with other users, if you want to share internet connectivity to other users.

12. Click Connect.

Perform PM scenarios 5 times each(Shutdown,Restart,Lid Close

  • Make sure connection is successful without any error
  • Should connect after performing PM scenarios
Stand alone
A
Configuring Wireless for EAP-TTLS

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Wi-Fi button.

5. Click Advanced button.

6. Enter SSID.

7. Choose EAP-TTLS in EAP Method drop down box.

8. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

9. Click Save identity and password, if you want to save user credentials

10. Click Share this network with other users, if you want to share internet connectivity to other users.

11. Click Connect.

From Browser:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Available WLAN profiles will show.

4. Click Settings button.

5. Browser will show.

6. On Internet connection portion, click Add Connection > Add Wi-Fi

7. Click Advanced button.

8. Enter SSID.

9. Choose EAP-TTLS in EAP Method drop down box.

10. Enter also the following if required:

- Phase 2 authentication

- Server CA certificate

- User Certificate

- Identity

- Password

- Anonymous identity

10. Click Save identity and password, if you want to save user credentials

11. Click Share this network with other users, if you want to share internet connectivity to other users.

12. Click Connect.

Perform PM scenarios 5 times each(Shutdown,Restart,Lid Close

  • Make sure connection is successful without any error
  • Should connect after performing PM scenarios
Stand alone
A

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
PM Functions

Note: Suspend/Hibernate is not supported

  1. Check Ethernet/Wireless profile is working fine before PM
  2. Lid Close/Resume the system
  3. Confirm that the connection is established after Resume from Lid Close

Perform this item at least 5 times

  • Make sure connection is successful without any error
Stand alone
A
Shutdown
  1. Connect a ethernet/wireless profile
  2. Shutdown the system
  3. Power On the system
  4. Confirm that the connection is established

Perform this item at least 5 times

  • Make sure connection is successful without any error
Stand alone
A

Long Run

Test Item Check Item / Criteria Results / Remarks
Chrome Native

1. With connection established, leave the system idle for few hours (5 -10 hours) overnight.

2. After long runs perform PM scenarions(Shutdown Restart Lid Close)

3. Resume the system and connect again to WLAN profile.

4. Download data from web (around 50 - 100 MB)

5. Check the speed and throughput of the WAN connection at www.speedtest.net

6. To check the speed and throughput click on the location arrow at www.speedtest.net

- OS or WLAN softwares should not crash or give error while long runs

- Connection should not drop during long hours connection

- Should connect successfully after idling for several hours

-Confirm that data can be downloaded successfully

(please enter Check Item / Criteria results here)

New Features List for Verification : Added on 03/11/2014.

Test number Test title Test steps Automated test (path)
1.2.1 Authenticate network key when connecting to a secure network [tcm:3631005] Objective

Provide network key when connecting to secure network. Prompt for network key if it is not stored, or if the stored key is incorrect.

Precondition

1) Authenticated Wifi Networks available and within the range.

Procedure

1) Go to Sign in screen on Chrome OS.

2) Click connectivity menu icon, on top right of screen.

3) Enable Wifi services.

4) Select any secured network.

5) Click connect button on the network settings dialog.

Note: If necessary, enter the network password in the Network key field on the network settings dialog.

Verification

If the network has been connected to before, and the correct password for that network has been specified in its network settings:

5) Clicking connect button connects the device to the secure network.

If the network has not been connected to before, or if the password specified before for that network is incorrect:

5) Clicking connect button should NOT connect the device to the secure network, and a notification should be displayed informing the user that the connection failed.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

Change: Need to change "Login" word to "connect"

1.2.2 Connectivity menu lists all the local Wireless networks within the range. [tcm:3611007] Objective

Connectivity menu lists all the local Wireless networks within the range.

Precondition

Wifi Networks available within the range.

Install Chrome OS

Procedure

1) Login to Chrome OS.

2) Click the connectivity icon located at the top right of the screen.

3) Enable Wifi service if it is not already enabled.

4) Examine the WiFi networks listed on the drop-down menu.

Verification

1) The drop-down list contains all the available wireless networks within the range.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

1.2.3 Extremeties: ChromeOS can handle 0 AP's within range [tcm:3699006] Objective

When there are no APs within range, chromeos should still function properly.

Precondition

A ChromeOS device and an area with no AP's present

Procedure

1) Enable WiFi in an area where no networks are present and wait for a bit.

Verification

Verify that no networks show up in the network dropdown or network settings page.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

1.2.4 Extremeties: ChromeOS can handle large number of AP's within range. [tcm:3725001] Objective

When put in an area with a lot of different AP's, we should not see issues with ChromeOS.

Precondition

An area where many SSID's are broadcasted

Procedure

1) Place the device in an area where many SSID's are broadcasted and let it sit there for a while

Verification

Verify that the list of networks is complete and that the network dropdown menu and the chrome://settings/internet page displays all of them properly.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

1.2.5 Extremeties: SSID Limits [tcm:3624013] Objective

To test that ChromeOS properly handles the SSID character length and limits.

Precondition

A programmable router

Procedure

1) Set the router to 1 ascii character

2) Connect to router

3) Disconnect from router

4) Set the router to 32 ascii characters

5) Connect to router

6) Disconnect from router

Verification

Verify that the device successfully connects to all the desired networks.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

1.2.6 ChromeOS can transition between multiple Wifi connections. [tcm:3654004] Objective

Ensure ChromeOS can change Wifi connections successfully.

Precondition

Netbook with ChromeOS installed.

At least two Wifi networks available (Say GoogleGuest and GoogleGuest-V6).

Procedure

1. Login to ChromeOS

2. If not already connected, using the UI in the upper right-hand corner, connect to a Wifi network.

3. Using the UI again, connect to a different Wifi connection.

Verification

* Ensure the connection is still alive after every network change, and the user is able to access the internet.

* Verify that switching between different Wifi connection should not affect the netbook internet connection.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

1.7.26 "Disable/Enable Mobile Data" appears only when 3G modem is present [tcm:6986997] Objective

Verify "Disable Mobile Data" appears only when 3G modem is present

Precondition

A chromebook

Gobi2k, Gobi3k, Y3300, Y3400, E362 modems

Procedure

Machine with modem:

1. Boot modem with any of the required modems

2. Open chrome://settings/ , and verify enable/disable modem works

3. Click on the ash menu and check the enable/disable modem icon works.

Machine without Modem :

1. Boot chromebook without modem

2. Verify that the UI for modem in chrome://settings is not available

3. Verify that the UI for the ash tray is not available.

Verification

Run the verification as Guest User, Owner User, Sign in screen, OOBE, No Network Available menu.

If there is a working modem ( Any state if activation) the Enable/Disable Mobile data button should appear in chrome://settings/internet page and in the menus and should be functional.

If there is no working modem, Enable/Disable Mobile data button should not appear in chrome://settings/internet page and in the ash tray.

1.7.31 3g download while in motion [tcm:6316360] Objective

To ensure the device can successfully finish a download while moving through an area where cellular signal is weak or absent

Precondition

1) An area where connectivity is strong/weak at different points. http://www.deadcellzones.com/ to look for areas.

2) A way to move the device through the area

3) An activated modem

4) All interfaces are disabled except for the cellular interface

Procedure

1) Begin the download of a large file in an area where cellular signal is strong

2) While the download is occurring, move the device through the zone where signal is weak/non-existent

3) Continue to move the device back to an area where the signal is strong

Verification

1) Verify that the download completes successfully or,

2) If download times out, verify that a download can be re-initiated again.

1.7.34 A device with no modem does not display the Enable/Disable mobile data option [tcm:10468411] Objective

To verify that no 3g UI is present when a modem is not present in the device

Precondition

1) A device with no modem such as a stumpylike device or a xx-he device.

Procedure

1) Power on device

2) Go to chrome://settings/internet page

Verification

1) Verify that the network dropdown does not contain an option to enable the modem.

2) Verify that the chrome://settings/internet page does not contain an option to perform any modem related commands.

1.7.39 Auto-connect to Cellular Network (CDMA/GSM) [tcm:3710004] Objective

On Startup, device should auto-connect to cellular when it is available.

Precondition

1) A device that has an active modem/sims

2) Gobi2k, Gobi3k, Y3300, Y3400, E362 modems

3) Cellular autoconnects to a particular carrier.

Procedure

1) Enable wifi and cellular on device and have both connected to something

2) Reboot the device.

3) Perform verification

4) Suspend/Resume the deivce with varying suspend times.

5) Perform verification

6) Disable WiFi

7) Reboot device and verify

8) Suspend/Resume the device and verify.

Verification

1) Verify that cellular network always auto-connects on boot/resume even if not the network with priority.

1.7.52 GSM: Reboot [tcm:6818290] Objective

To verify the correct GSM carrier is persistent even after device reboot

Precondition

1) A GSM sim card

2) Set up the GSM by using instructions in GSM compatibility test (http://google-testcasemanager.appspot.com/home#!view=test&ti=6760336)

Procedure

Perform the following steps for the Y3300, Y3400, Gobi2k and Gobk3k modems.

1) Make sure device is working over the correct GSM carrier

2) Power off the machine

3) Power on the machine

Verification

Verify the device is using the correct carrier after boot

1.7.53 GSM: Suspend Resume [tcm:6811013] Objective

To verify behavior of the modem in GSM mode after device resumes from a suspend.

Precondition

A GSM carrier/sim card that is unlocked and unlocked.

A ChromeOS Notebook

Gobi2k, Gobi3k, Y3300, Y3400 modems

Procedure

1) Follow instructions for setting up GSM using the instructions on the GSM compatibility test (http://google-testcasemanager.appspot.com/home#!view=test&ti=6760336)

2) With the unlocked sim, connect to the mobile carrier.

3) Suspend device for up to 1 minute

4) Resume device.

5) Repeat test but have the mobile carrier disconnected before suspending/resuming.

6) Repeat test with a sim that uses a pin. Unlock the sim, connect to the carrier, and perform steps 2-4

7) Repeat test where the pin of the locked sim is changed prior to suspend/resume. Perform steps 2-4 after changing the pin.

8) This test need needs to be repeated (at least steps 1-5) across various different platforms using different modems.

Verification

1) Verify the modem device comes up

2) Verify the correct network name is displayed in the dropdown/chrome://settings/internet page.

3) Verify that the connection state of the modem matches that prior to suspend/resume.

4) Verify that users are not required to enter the pin regardless of whether or not the pin has been changed.

5) Verify traffic flow through modem.

1.7.56 modem factory-reset works [tcm:16207140] Objective

A gobi modem

Precondition

1) A gobi modem that is in a partially activated or activated state

2) Gobi2k, Gobi3k modems

*Note, if there is a VZW plan on the modem, make sure the plan has been cancelled in Verizon's end before this test is run.

Procedure

1) Boot device an run modem status

2) Verify the modem state is > 0

3) Run modem factory reset

Verification

1) Verify after factory reset that the modem state is 0.

2) Verify that modem can now be re-activated.

1.7.57 Modem with no SIM inserted [tcm:16094118] Objective

To verify the behavior of the device in GSM mode when no sims are inserted.

Precondition

A chromebook that supports 3G/4G.

Y3300, Y3400, Gobi2k, Gobi3k, E362 modems

Procedure

1) Boot the chromebook with the modem in GSM (or LTE) mode with no SIM. Perform Verification.

2) Suspend the device then resume

3) Perform verification.

4) Power off the device and insert a SIM card.

6) Power on the device and perform verification.

7) Suspend the device and take out the SIM card.

8) Resume the device and perform verification.

Verification

1) Verify that when no SIM card is inserted, the option to enable mobile data in chrome://settings or the ash tray should appear.

2) When a SIM is present, the mobile data option should appear

3) When the SIM is removed while suspended, the mobile data option should disappear upon reboot but there should be no indications of crashes, etc.

1.7.58 modem_set_carrier works in crosh on gobi modems [tcm:11561426] Objective

Verify modem_set_carrier works in crosh for gobi modems (gobi 2k and gobi 3k)

Precondition

A netbook (x86 and arm) with an embedded modem module .

A gobi2k and gobi3k modem.

Procedure

1) Open crosh and run crosh> "modem_set_carrier Verizon Wireless".

2) Run crosh>"modem status"

3) Run crosh>"modem_set_carrier Generic UMTS".

4) Run crosh>"modem status"

Repeat the steps 1-4 for both gobi 2k and 3k modems across arm and x86 architectures.

Verification

2) Verify "modem_set_carrier Verizon Wireless" is successful and carrier is set to Verizon Wireless and it is reflected accurately in the modem status.

4)Verify "modem_set_carrier Generic UMTS" is successful and carrier is set to Generic UMTS and it is reflected accurately in the modem status info.

1.7.67 Suspend: Disconnect from Cellular network when device suspends/sleeps [tcm:3705005] Objective

Cellular network is automatically disconnected when the device suspends (or sleeps).

Precondition

1) A network connected to a cellular network

2) Gobi2k, Gobi3k, Y3300, Y3400

Procedure

1) Connect device to cellular network

2) run tail -f /var/log/messages in vt2 or shell tab.

3) Suspend/resume the device

4) Verify

Verification

1) Verify that the logs indicate a disconnect message for cellular service

2) Verify that on resume, device needs to re-connect (auto-connect or not) to the cellular network, and is not already connected.

1.7.71 Transition: Disable cellular shall gracefully disconnect from 3G network. [tcm:3723003] Objective

Verify disabling cellular gracefully disconnect 3g with no cromo/ModemManager/shill crash.

Precondition

Chromebook

Gobi2k, Gobi3k, Y3300, Y3400, E362 modems

Procedure

1) Enable cellular, and connect to 3G network.

2) Disable cellular. Observe cellular connection and status.

3) Enable cellular, and connect to 3G network.

4) While 3G network is "connecting...", quickly disable cellular.

5) Examine var/log/messages file for cromo or flimflam crashes.

Note: Cellular may be enabled/disabled from the Settings -> Internet page, or from the Connectivity menu. To enable, click [Enable Cellular] button, or select "Enable Cellular" menu item. To disable, click [Disable Cellular], or select "Disable Cellular" menu item.

Verification

2) When user disables cellular, 3G disconnects gracefully, and then is disabled.

4) When user disables cellular while cellular is in the process of connecting to a network, the following happens:

a) 3G stops connecting

b) 3G disconnects gracefully

c) Cellular is disabled

5) Enable, Connect, Disconnect, and Disable all succeed with out any cromo, ModemManager, or shill crash.

6) Verify that disconnect to service is called in the /var/log/messages when cellular is disabled.

Notes from TestScribe Importer

TestScribe component path: Network > Cellular (3G) Network > Embedded Modem

Component "Cellular (3G) Network": added as label "Cellular_3G_Network"

1.7.72 Transition: Disconnecting from Ethernet LAN automatically connects to selected Cellular network. [tc Objective

Device automatically switches to Cellular network when Ethernet LAN is disconnected.

Precondition

1) A chromebook with a modem

2) A device connected via cellular. Then an ethernet cable is inserted.

Procedure

1) Examine the UI and verify it shows the default connection as Ethernet

2) Unplug the ethernet device and verify the verizon connection is still up

3) Try to use the internet and verify that it still works.

Verification

1) Verify that internet still works

2) Verify the UI shows the default connection as cellular.

1.7.73 User can Connect and Disconnect from Mobile network [tcm:4680201] Objective

Connect/Disconnect from Mobile Data

Precondition

A chromebook with activated cellular

Gobi2k, Gobi3k, Y3300, Y3400

Procedure

1) Open the Internet Settings panel.

2) Click the Mobile Data Dialog and verify Cellular enables.

3) Click the connectivity icon and select the Cellular network and connect to that network.

4) Click the [Disconnect] button for the Cellular Network selected in step 3. Wait ~2 seconds for network to completely disconnect. Examine the connectivity menu. User may need to view details of the cellular network to disconnect from the network.

5) Click the [Connect] button for the Cellular Network selected in step 3. Wait ~5 seconds for network to completely connect. Examine the connectivity menu.

Verification

3.1) Connectivity menu shows active network from internal modem.

3.2) Selecting the Celluar Network shall connect to that network. The connectivity Icon shall change to "3G" (green).

4) Clicking [Disconnect] button will disconnect from selected 3G network. The connectivity icon shall change to null (x), indicating no connection.

5) Clicking [Connect] button shall connect to selected 3G network. The connectivity icon shall change to a "3G" (green).

1.14.1 802.11a Support [tcm:6717003] Objective

Verify the dut can connect to an 802.11a network

Precondition

An 802.11a ap within range with any encryption type

Procedure

Connect to the 802.11a network (Buffalo 5Ghz)

Verification

Verify there are no problems connecting to the network.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.2 802.11b Support [tcm:6678515] Objective

Verify device can connect to 802.11b networks.

Precondition

A router configured with 802.11b.

Procedure

Connect to the 802.11b router. - CrOS_WPA_LinksysWRT54GL (Hidden)

Verification

Verify dut can connect to the router.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.3 802.11g Support [tcm:6719001] Objective

To verify that the device can connect to 802.11g 2.4ghz channel networks.

Precondition

An 802.11g router.

Procedure

Connect to the 802.11g router - (Buffalo 2.4GHz)

Verification

Verify device connects to the router with no problems.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.4 802.11n Support [tcm:6672609] Objective

To verify device can connect to 802.11n mimo (multiple input multiple output) router on 5ghz channel.

Precondition

An 802.11n mimo router

Procedure

Connect to the router. - Trendnet Router.

Verification

Verify connection is successful.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.5 ChromeOS can connect to WiFi network after Suspend/Resume [tcm:10738802] Objective

Verify that ChromeOS can connect to WiFI network after suspend/resume.

Precondition

Netbook with ChromeOS installed.

Wifi connection available.

Procedure

1) When logged in, connect to an open network A.

2) Suspend the device for some time (30 minutes or more) and Resume the device.

3) Perform verification steps.

Verification

Verify that ChromeOS connects to network A and make sure that connection is not slow on resume.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.6 Connect to EAP-TTLS network [tcm:11577187] Objective

Verify a EAP-TTLS network connection

Precondition

Procedure

1.Login as a user

2.Connect to a 802.11x channel with EAP-TTLS

3.From the login screen connect to a 802.11x channel with EAP-TTLS

Verification

Verify that connection is successful in case 2 & 3 above

- Also verify that the network is remembered and we are able to reconnect without entering the network credentials

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.7 Connect to EAP-PEAP network Objective

Verify a EAP-PEAP network connection

Precondition

An 802.1x enterprise network

Procedure

1.Login as a user

2.Connect to a 802.1x channel with EAP-PEAP and radius user credentials

Verification

1.Verify that connection is successful

2.The network should be remembered across login/logout and reboots and we should be able to reconnect without re-entering credentials.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.8 Connect to EAP-TLS network Objective

Verify a EAP-TLS network connection

Precondition

An 802.1x enterprise network

Procedure

1.Login as a user

2.Install the required certificates from www.radius.com/certs

3.Connect to the network with the radius user credentials and certificate

Verification

-Verify that connection is successful

-The network is remembered and we are able to reconnect without entering the network credentials

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.9 Connect to 802.1x network with incorrect credentials Objective

Verify that we fail connection to 802.1x with incorrect credentials

Precondition

An 802.1x enterprise network

Procedure

1.Login as a user

2.Connect to a 802.1x with EAP-TLS providing incorrect certificate and/or user credentials

3.Repeat the same for PEAP and TTLS

Verification

Connection should fail and user should be notified of the reason for failure

Also verify that the network is remembered and we are able to reconnect after editing the network credentials

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.11 Power Cycle: ChromeOS connects to WiFi network after Suspend and Resume. [tcm:10736782] Objective

Ensure that ChromeOS connects to a WiFi network when power cycle is performed on AP during suspend and resume.

Precondition

Netbook with ChromeOS installed.

Wifi connection available.

Procedure

1) When logged in, connect to any WiFi network 'A'.

2) Suspend the device.

3) Power cycle the AP.

4) Resume the device.

5) Perform verification steps

Verification

Verify that ChromeOS connects to network 'A' and make sure that connection should is not slow on resume.

1.14.12 Reliability: Connection should be able to connect to and hold a connection reliably under stationar Objective

We want to make sure that if a laptop is stationary and connected, it stays connected, and there are no problems with DNS.

Precondition

Procedure

1) Connect to any WiFi network

2) Loop through connecting to the first 10,000 websites of the 1 million most popular websites (as obtained from http://www.alexa.com/topsites)

Verification

1) Ensure that throughout the duration, we keep connectivity.

2) Due to possible server side errors, pre-determine an acceptable error level percentage for number of allowed failed page retrievals, and verify that the number of pages failed to retrieve is less than this.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.13 Roaming: ChromeOS can connect to WiFi network after suspend/resume [tcm:10743772] Objective

Ensure that ChromeOS connects to a WiFi network after suspend and resume from one end of the building to another.

Precondition

An area where roaming is applicable such as any building in Google Campus.

Procedure

1) Start on one end of the building.

2) Connect to a WiFi network 'A'.

3) Suspend the device (for about 30 minutes).

4) Walk to the other side of the building.

5) Resume the device.

Verification

Verify that device connects to WiFi network 'A' successfully upon resume and connect on resume should not be slow.

src/third_party/autotest/files/server/site_tests/network_WiFi_RoamSuspendSSID
1.14.14 Roaming: Smooth transfer between two open network AP's with the same SSID [tcm:3706005] Objective

When in motion from one AP to the next, we should not experience connectivity problems. Transition should be smooth for the user.

Precondition

An area where roaming is applicable such as any building Google Campus

Procedure

1) Start on one end of the building

2) Connect to any website

3) Walk to the other side of the building

4) Connect to another website

5) Connect to Youtube and select a video that is several minutes long and begin loading it. Then begin playing it.

6) Walk back to the other side of the building.

Verification

1) Verify that all websites connect successfully

2) Verify that the loaded video finishes loading and plays completely

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network

1.14.15 Security/Encryption: Chrome OS can connect to WiFi network using WPA-PSK w/TKIP [tcm:3628005] Objective

ChromeOS can connect to Wifi network with TKIP encryption.

Precondition

ChromeOS can connect to Wifi networks with WEP encryption.

ChromeOS is installed on a netbook.

Need TKIP Wifi network to connect

Procedure

1. Launch chrome.

2. Enable Wifi network.

3. Try connecting to a Wifi connection that uses TKIP encryption (i.e, WPA-PSK with TKIP)

Verification

Should be able to connect to the network. Able to "ping 192.168.2.254" from netbook.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network > Security/Encryption

Change

Verification : Should be able to connect to the network. Able to connect to network

CrOS_Identical has WPA-PSK (TKIP)

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.16 Security/Encryption: ChromeOS can connect to Wifi networks that use certificate based encryption [tc Objective

Make sure system can connect to networks that require some sort of certificate, like Google-A

Precondition

Procedure

TBD

Verification

TBD

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network > Security/Encryption

Change

Procedure:

1) Log in the netbook with cable network connection.

2) Install the Google A certificate.

3) Enable Wifi and connect to Google A.

4) Remove the cable network connection and observe the network connection

Verification:

2) Google A certificate should get installed successfully

3) Google A should get connected

4) Verify user can access the various sites

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.17 Security/Encryption: ChromeOS can connect to Wifi networks that use WPA-PSK with AES-CCMP encryption Objective

ChromeOS can connect to Wifi networks that use WPA-PSK with AES-CCMP encryption.

Precondition

ChromeOS can connect to Wifi networks with WEP encryption.

ChromeOS is installed on a netbook.

Need AES-CCMP Wifi network to connect

Procedure

1. Launch chrome.

2. Enable Wifi network.

3. Try connecting to Wifi network that uses WPA-PSK with AES-CCMP encryption.

Verification

Should be able to connect to the network. Able to "ping 192.168.2.254" from netbook.

CrOS_WPA2_trendnet_tew639gr

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network > Security/Encryption

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.18 Security/Encryption: ChromeOS can connect to Wifi networks using WPA2 with TKIP and AES. [tcm:360700 Objective

Ensure ChromeOS can connect to a Wifi connection using WPA2 with TKIP and AES encryption.

Precondition

Netbook with ChromeOS installed.

Wifi connection secured by WPA2 with TKIP and AES encryption.

Procedure

1) Login to ChromeOS

2) Choose the Wifi connection using WPA2 with TKIP and AES encryption.

3) Enter the network key and wait for it to connect.

Verification

3a) Should be able to connect to Wifi network protected by WPA2 using TKIP and AES encryption.

3b) Able to "ping 192.168.2.254" from netbook.

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network > Security/Encryption

Change CrOS_NONE_trendnet_tew639gr to have TKIP/AES encryption.

Change

Verification:

3b) Able to ping to connected network through gate way

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.19 Security/Encryption: ChromeOS can connect to Wifi networks with Shared Key WEP encryption. [tcm:3718 Objective

ChromeOS can connect to Wifi networks with Shared Key WEP encryption.

Precondition

ChromeOS can connect to Wifi networks with WEP encryption.

ChromeOS is installed on a netbook.

Need Shared Key WEP Wifi network to connect

Procedure

1. Launch chrome.

2. Enable Wifi network.

3. Try connecting to Wifi connection that uses shared key WEP encryption

Verification

Should be able to connect to the network. Able to "ping 192.168.2.254" from netbook.

CrOS_WEP_trendnet_tew639gr

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network > Security/Encryption

Change

Verification :

Able to ping to connected network

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.20 Security/Encryption: ChromeOS can connect to Wifi networks with WEP encryption. [tcm:3663004] Objective

ChromeOS can connect to Wifi networks with WEP encryption.

Precondition

ChromeOS is installed on a netbook.

Need WEP Wifi network to connect

Procedure

1. Launch chrome.

2. Enable Wifi network.

3. Try connecting to Wifi connection that uses WEP encryption

Verification

Should be able to connect to the network and access websites.

CrOS_WEP_Linksys_WRT54G2

Notes from TestScribe Importer

TestScribe component path: Network > WiFi Network > Security/Encryption

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.21 Security/Encryption: Invisible/Hidden network handle invalid Passphrase Handling [tcm:6817162] Objective

Hidden handles invalid passphrase gracefully and displays error message.

Precondition

Procedure

1) Boot machine and look at network list

WEP:

2) Connect to WEP hidden network by selecting option "Join other Network" from the list

3) Provide wrong password (nvalid passphrase of lengths 0, 1, 7, 9, 12, 25, 27, 30 characters) and Wait for the connection.

4) Enter wrong password having length other than 5,10,13,26 character.

WPA:

WPA

2) Attempt to connect to a WPA network using an invalid phrase of length 0, 1, 7, 64 characters.

3) Perform verification steps.

4) Repeat above steps but try to connect to WPA protected network by entering wrong pass phrase other than length 0, 1, 7, 64 characters.

Verification

WEP:

1) For WEP network if password is less than 5 than the connect button should not enabled

2) For invalid passphrase having a valid length of 5,10,13,26 the network will try to connect for 45 sec but due to invalidity of passphrase it should pop up the network error message

3) The network should not get added in remembered network after having the failed attempt of connection.

4) Wifi Icon on upper right should stop oscillating (scanning for networks) at some point and display an x on the bottom corner indicating connection failed. Device should then attempt to auto-connect to a known network if it exists.

5. Chrome OS should prompt a error/warning message to enter correct password to connect authenticated network in the case of WPA.

WPA:

1) For WPA network if password is less than 5 than the connect button should not enabled

2) For invalid passphrase having length in between 8 and 63, the network try to connect for 45 sec but due to invalidity of passphrase it should pop up the network error message

3) The network should not get added in remembered network after having the failed attempt of connection

4) Wifi Icon on upper left should stop oscillating (scanning for networks) at some point and display an x on the bottom corner indicating connection failed

5) Chrome OS should prompt a error/warning message to enter correct password to connect authenticated network in the case of WPA.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.22 Security/Encryption: Invisible/Hidden WEP Network [tcm:3677003] Objective

The user should be able to add invisible WEP networks

Precondition

In an area with WEP encrypted network that is hidden but not in remembered networks list

Procedure

1) Boot machine and look at network list

2) Connect to WEP hidden network by selecting option "Join other Network" from the list

3) Reboot the machine

4) Connect to the hidden network

Verification

1) Verify that before we add the hidden network, the network does not show up on the network list

2a) User should able to add the hidden network by selecting "Join Other network"

2b) User should be able to provide encryption type

3) After disconnecting the hidden network , verify the network is get added in remembered network list

4) Verify after rebooting the hidden network are visible to user and he should able to connect it directly and should not have to re-enter credentials for the hidden network.

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.23 Security/Encryption: Invisible/Hidden WPA Network [tcm:3698005] Objective

Verify that the user can successfully connect to an invisible WPA network

Precondition

Procedure

1) Boot machine and look at network list

2) Connect to WPA hidden network by selecting option "Join other Network" from the list

3) Reboot the machine

4) Connect to the hidden network

Verification

1) Verify that before we add the hidden network, the network does not show up on the network list

2a) User should able to add the hidden network by selecting "Join Other network"

2b) User should be able to provide encryption type

3) After disconnecting the hidden network , verify the network is get added in remembered network list

4) Verify after rebooting the hidden network are visible to user and he should able to connect it directly and should not have to re-enter credentials for the hidden network

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.24 Security/Encryption: Invisible/Hidden WPA2 Network [tcm:6670603] Objective

Verify that the user can successfully connect to an invisible WPA2 network

Precondition

Procedure

Procedure

1) Boot machine and look at network list

2) Connect to WPA hidden network by selecting option "Join other Network" from the list

3) Reboot the machine

4) Connect to the hidden network

Verification

Verification

1) Verify that before we add the hidden network, the network does not show up on the network list

2a) User should able to add the hidden network by selecting "Join Other network"

2b) User should be able to provide encryption type

3) After disconnecting the hidden network , verify the network is get added in remembered network list

4) Verify after rebooting the hidden network are visible to user and he should able to connect it directly and should not have to re-enter credentials for the hidden network

src/third_party/autotest/files/server/site_tests/network_WiFi_SimpleConnect
1.14.25 Smooth transfer between two open network AP's after suspend and resume [tcm:10777083] Objective

Ensure that ChromeOS can connect to WiFi network after suspend and resume. Transition should be successful from one AP to another.

Precondition

Netbook with ChromeOS installed.

Wifi connection available.

Two AP's available.

Procedure

1) Turn on AP 'A', and turn off the other AP 'B'.

2) Connect to AP 'A' and Suspend the device.

3) Turn off AP 'A' and turn on AP 'B'.

4) Resume the device.

Verification

Verify that ChromeOS connects successfully and make sure that connection should is not slow on resume.

1.14.26 Stress Suspend/Resume (WiFi) [tcm:16486094] Objective

To verify that wifi returns via autoconnect after many iterations of suspend/resume

Precondition

Many different types of WiFi Networks arround including

1) Open

2) WEP

3) WPA-PSK

4) WPA-Enterprise

5) Hidden WPA

A copy of the suspend/resume test from www/~stanleyw/test_scripts/suspend-resume. The script should suspend/resume, then ping and timeout after 30 seconds of failure. (it is also attached here).

Procedure

1) Pick a network defined in the precondition. Assume Open. There should be no other remembered networks on the list.

2) Connect to the network and ensure auto-connect is enabled.

3) Run the suspend/resume stress.

4) Repeat with each of the above listed wifi networks.

Verification

Verify that the script succeeds for some duration of time

1.15.5 Ethernet Disconnnected (Onboard ethernet) [tcm:16908765] Objective

To verify device behavior when ethernet has been disconnected.

Precondition

A chromebook with an onboard ethernet port.

Procedure

1) Connect device to ethernet

2) Disconnect device from ethernet.

3) Re-connect ethernet.

Verification

* System should not hang when either ethernet cable or ethernet dongle are disconnected.

* When ethernet is re-connected, verify connectivity is back up and running.

1.15.6 Ethernet to maintain Connectivity (onboard) [tcm:16817493] Objective

To verify onboard ethernet can maintain stable internet connection.

Precondition

A chromebook with onboard ethernet

A wired LAN.

Procedure

Repeat http://google-testcasemanager.appspot.com/home#!view=test&ti=8608498 with onboard ethernet.

Verification

Repeat http://google-testcasemanager.appspot.com/home#!view=test&ti=8608498 with onboard ethernet.

1.15.9 Reboot Ethernet Behavior (onboard ethernet) [tcm:16751681] Objective

To verify ethernet behaves properly when device reboots.

Precondition

A chromebook with onboard ethernet.

Procedure

1) Insert wired ethernet.

2) Reboot the device several times using different intervals of when to reboot.

Verification

* Verify dhcp request goes out on every boot, and that device obtains dhcp address if we wait long enough for this to happen.

* Verify there is a route for ethernet and functional ethernet on boot if we wait long enough for this to happen.

1.15.11 Suspend/Resume Ethernet (onboard ethernet) [tcm:16709671] Objective

To verify the onboard ethernet behaves properly after suspend/resume.

Precondition

A wired ethernet connectioin

Procedure

1) Connect to onboard ethernet

2) Perform many suspend/resume cycles.

Verification

* On every resume, verify device requests and obtains a dhcp address (if we wait long enough for this to occur before next suspend cycle)

* Verify that default route goes to ethernet when both ethernet and wireless are provided and verify function ethernet (if we wait long enough to verify this)

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
PM Functions

Note: Suspend/Hibernate is not supported

  1. Check Ethernet/Wireless profile is working fine before PM
  2. Lid Close/Resume the system
  3. Confirm that the connection is established after Resume from Lid Close

Perform this item at least 5 times

  • Make sure connection is successful without any error
Stand alone
A
Shutdown
  1. Connect a ethernet/wireless profile
  2. Shutdown the system
  3. Power On the system
  4. Confirm that the connection is established

Perform this item at least 5 times

  • Make sure connection is successful without any error
Stand alone
A

Note: Before starting the test,Make sure you've activated your access to the mobile network. If you're using a SIM card, make sure it is inserted.

For using SIM card(CDMA-3G):

1.PressCtrl+Alt+Tto open a terminal window.

2.Change your carrier association by entering this command:"modem set-carrier Generic UMTS"

3.Enterexitto return to your browsing window.

4.Turn off the Chromebook and insert the SIM card.

For using Verizon Mobile broadband (3G-CDMA):

1.PressCtrl+Alt+Tto open a terminal window.

2.Change your carrier association by entering this command:"modem set-carrier Verizon Wireless "

3.Enterexitto return to your browsing window.

4.Turn off the Chromebook and restart.

Wireless Function Basic Functions

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
Installation / Configuration
Chrome - WWAN Enabled

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Confirm that network icon beside Network section is not strike out.

4.If shows , that means you are ready to connect to mobile networks.

5. Select the mobile network's name from the network menu to connect to it .

  • WWAN profiles should be shown and can be connected without errors.
  • Confirm Carrier name & status is listed after clicking information icon (beside network icon)
Stand alone
A
Chrome - WWAN Disabled

From Desktop:

1. From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Click network icon beside Network section.

4. No mobile network's name should be available.

From Browser:

1.Launch Chrome browser,open settings from the customize and control Google chrome menu.

2. Click "Show Advanced settings"-> Click "Change proxy settings" under Network section.

3. Confirm under Internet Connection portion, mobile network is not listed.

  • WWAN profiles should not be shown and can be connected without errors.
Stand alone
A
Basic Function Verification
Connecting to Mobile Network/3G (Make sure WLAN is disabled)

From Desktop:

1.From lower right portion of Chrome Desktop (taskbar), click network icon.

2. Click Network section.

3. Confirm that network icon beside Network section is not strike out.

4.If shows , that means you are ready to connect to mobile networks.

5. Select the mobile network's name from the network menu to connect to it ,Enter PIN number and other credentials if prompted.

From Browser:

1.Launch Chrome browser,open settings from the customize and control Google chrome menu.

2. Click "Show Advanced settings"-> Click "Change proxy settings" under Network section.

3.Select the available Mobile network and connect. Enter PIN number and other credentials if prompted.

Note:If available WWAN profiles will not shows.,On Internet connection portion,->click Add Connection > Add Dail-up connection.

  • WWAN profile should be connected successfully without any errors.
  • Connectivity Status:
  1. --> While connecting to the mobile network.
  2. -> Successful connecting to a mobile network. The number of lit signal bars indicates the strength of your network signal.
  3. ->With low mobile data.
  • Confirm Carrier name & status is listed after clicking information icon (beside network icon)
Stand alone
A
Modify a Mobile Network/3G

1. Click the status area in the lower right corner of the desktop, where your account picture appears.

2. Select Settings and Help.

3. Under Internet Connection section > click Wireless Network menu/Mobile data.(Make sure WWAN profile is connected)

4. Check the Automatically connect to this network.

5. Click Close.

  • Confirm that mobile network will auto-connect after PM functions.
  • Confirm that mobile network details shown correct in Connection tab.
Stand alone
A
SIM Lock function verification

PIN Verification:

1.From lower right portion of Chrome Desktop (taskbar), click network icon.

2.Make sure you're connected to the mobile network. Once you're connected, click its name in the network menu.

3.In the dialog that appears, click theSecuritytab.

4.Select the "Lock SIM card" checkbox to require a PIN. To set a custom PIN, selectChange PIN.

PUK Verification:

1.From lower right portion of Chrome Desktop (taskbar), click network icon.

2.Connect to mobile network ,it will prompt for PIN number.

3.Enter Wrong PIN number for twice,the SIM card will be disabled.

4.Enter the PUK number provided by the mobile carrier to Enable the SIM.

  • Confirm Customization of the PIN number.
  • Confirm PIN number prompt appears for the next time you connect to the mobile network./after PM operations or Disconnect and connect.
  • Confirm SIM card is disabled on entering wrong PIN twice.
  • Confirm SIM card Enables after successful entry of PUK
Stand alone
A
Mobile network/3G and Wi-Fi network Co-existence:

1.From lower right portion of Chrome Desktop (taskbar), click network icon.

2.From the Network section,select the correct Access point and configure the same with SSID, Encryption.

3.From lower right portion of Chrome Desktop (taskbar), click network icon.

4.Select the mobile network's name from the network menu & connect to it.

5.Make sure both Wi-Fi profile and the mobile network connected at the same time.

6.Download/Upload files to FTP(>300MB files)

  • Make sure there is no connection drop at any point of time during upload and download.
  • Make sure Wi-Fi network is used for data transmission
Stand alone
A

Test Item
Check Item / Criteria
Configuration
Result (Chrome OS)
PM Functions

Note: Suspend/Hibernate is not supported

  1. Check Mobile network is connected & working fine before PM
  2. Lid Close/Resume the system
  3. Confirm that the connection is established after Resume from Lid Close

Perform this item at least 5 times

  • Make sure connection is successful without any error
Stand alone
A
Shutdown
  1. Connect a Mobile network.
  2. Shutdown the system
  3. Power On the system
  4. Confirm that the connection is established

Perform this item at least 5 times

  • Make sure connection is successful without any error
Stand alone
A

OTHER DETAILS

EUT Quantity : Two systems 1. "Please check Error and Warning message in Event Viewer before you start the test case and after you complete the test case, and report it to your team lead."

2. "Perform All Test in Battery Mode (Some of the test items need to perform in AC Mode, follow each Test Case)" (All Test Activity should be performed with AMT Enabled)

  • [Communication] Support WAN? =E0 No WAN support Yes
  • [Communication] Scope of wireless authentication support =E0 Current PCR request system certification for US only.
  • [Communication] Scope of wireless adapter support =E0 Intel 2230BNHMW (Broadcom BCM943228HMB backup)
  • [Communication] Carrier certification required? =E0 No WAN, no carrier
TEMS Reviewer Log:
Review Logs
Keywords:   None
Requirements :   None
Attached files :

Update History:
Modified last: 2016-06-10 18:52:51.304, by Miyuki Komatsu_nw