Test Case

Show / Hide direct link   <MAIN> 5122PA: Remote Wake Technology (RW) Function Test - PP-80456



Version 1.5
Created on 21/03/2013 15:30:11  by Kristian Galacgac
Summary
Preconditions
Status:   New
Priority:   Medium
BASIC INFORMATION
Section:S/W Test Require attachment:No
Team:Network Group:Basic Function
Lessons Learned:Yes Phase:FVT, SIV (BBFV), SIT, SVT
Locations:Inhouse: AWS and Cambridge, Inhouse: AWS, Inhouse: Cambridge, Compal, Flextronics, Quanta, Wistron Owned By:Eiji Ogata/LENOVO
Objective:To qualify ISCT-Remote Wake.
CRITERIA
Check Remote Wake works fine in various scenarios.
EUT QUANTITY
Two Systems
EQUIPMENT
System-A: EUT with ISCT installed & Remote Wake enabled.
System-B:Any Lenovo system.

*Make Sure both system must have valid internet connection.
Critical Attribute:[0] : WLS - Wireless

CONFIGURATION
REFERENCE PROCEDURE
STATISTIC INFO
Operating System Win81-64bit Win81-32bit Win10-32bit Win10-64bit Total
Test Points
Duration
Workload
# Step actions Win81-64bitWin81-32bitWin10-32bitWin10-64bit
1 Intel-Remote Wake verification using Mesh Central AAAA
2 Remote Wake & Access Verification using Splashtop AAAA
3 ISCT-Remote Wake using 3rd part Apps AAAA
4 Intel-Remote Wake negative testing AAAA
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.

Applicable to Sharkbay Products only.. BIOS support is needed:

Note :For ISCT- Remote wake to work, following are mandatory,
- iSCT-RW supported BIOS/ECFW/MEFW for each product
- iSCT-RW latest driver(with Remote wake function Enabled)
- iSCT-RW supported driver for the adapters.
- iSCT-RW supported Power Manager.
- iSCT-RW is supported only on Window-8 OS.
- Remote Wake feature needs Intel? ME Firmware enabled.
- Intel Remote Wake Test Application & Wake Service client.
- Mesh Central-(Meshcentral.com;Windows mesh agent,Mesh policy file).

POINTS TO REMEMBER BEFORE START TESTING:

1.Set "Wake on LAN" to "AC and Battery" in BIOS settings.(Config->Network).
2.Make sure POP/SVP/HDP not set in BIOS.
3.Make sure "Allow this device to wake the computer" option checked(Enabled) for WLAN/LAN adapters.(Properties->Power Management)
->Note:Don"t check(Enable) "Only allow magic packer to wake the computer" option.
4.Enable "Allow wake timers" for both On battery & Plugged in OS-Power options.
(Control panel->Hardware & sounds->Power Options->Edit plan settings->Change Advance power settings->Sleep)

For troubleshooting:

Enable additional logging information by adding two registry entries:
? ?LoggingLevel? with a DWORD value of 0x10
? ?LoggingEnabled? with a DWORD value of 0x2
In the path:ComputerHKLMSoftwareWow6432NodeIntelIntel Smart Connect Technology
-Log files are created in the C:ProgramDataInteliSCT directory

Limitations
Restrictions

[UR-03727SG]
1. Remote Wake is not supported for 3rd Party Applications
Reference:
ECR167783 RG2:W864:Remote Wake using 3rd party App fails to wake the system
ECR167998 RG2:W8:Remote Wake using 3rd party App fails to wake the system

2. Remote Wake is not supported using SplashTop
Reference:
ECR167538 ECR167539:RG2:W8:Splashtop connects but loses connection aft Video/Game play
ECR167539 RG2:W864:Splashtop connects but loses connection aft Video/Game played

. The Remote Wake feature will always be grayed out on Windows 7 as remote Wake is
currently not supported on Windows7.
Reference:
ECR211762 W7:2QR:GM4: Remote Wake button is grayed-out
http://download.intel.com/support/services/smartconnect/sb/installandconfigure.pdf
Information

1. When iSCT is enabled, 30 days standby is disabled in Power Manager.
2. NetDetect will not work if Airplane Mode is OFF.
3. Wireless LED is ON during S3.



Refer support statement for each platform before start of the test

Product Support:
ME
ME 9.0 (SHB-2 chip)
ME 9.5 (SHB-ULT)
ME Firmware SKU
5MB
1.5MB
5MB
Applicable Products Oasis
Kome
Rogue-2 w/o Dock
Sting Non-vPro
Cobain Non-vPro
Mystique Non-vPro
Rogue-2 w/ Dock
Wolverine
Sting vPro
Cobain vPro
Mystique vPro
S3
S4
S3
S4
S3
S4
WLAN
YES
NO(*1)
YES
NO(*1)
YES
NO(*1)
LAN
YES
YES(*2)
NO
NO
NO
NO


Notes:
1. Power to WLAN is not supplied per Lenovo Classic Design.
2. It wakes only when AC power is supplied (ME is in M3) and both POP and HDP are not present.

WLAN adapter support
WLAN Adapter Name
Remote Wake
Intel Kilmer Peak
NOT Supported
Intel Puma Peak
NOT Supported
Intel Taylor Peak
NOT Supported
Intel Marble Peak
NOT Supported
Realtek
NOT Supported
Broadcom
NOT Supported
Intel Jackson Peak
Edge team to confirm
Intel Wilkins Peak-2
Supports only S3 / S4 not supported


LAN adapter support
LAN Adapter Name
Remote Wake
Intel LAN-(WGI218V)
Refer Product support table
Intel LAN-(WGI218LM)
Refer Product support table


WWAN adapter support
WWAN Adapter Name
Remote Wake
Ericssion
NOT Supported
Gobi-5K
NOT Supported


Note: Per Intel"s recommendation, we should use Mesh Central instead of Remote Wake Test App for our tests. If any case found reliable app from Store, please inform MMC NW Team.


Intel-Remote Wake verification using Mesh Central:
TEST ITEM
RESULT
Remarks & Criteria
Win-8 32 bit
Win 8 64 bit

Please refer "Mesh central-Setup Doc" before starting the test.
Attachment "Mesh Central_setup.pptx" is available below under Attached files section.

1. Ensure the system under testing was listed in Meshcentral site.
2. In ISCT GUI, Basic Tab > click Enable Updating button.& Enable Remote Wake button.
3. Use Meshcentral website on System A to connect SUT.
4. Ensure the connection successfully established.

RW verification from Sleep-sate (S3):

1. Select SUT under Device tab.
2. Click "Power Actions" button under General tab->Select "Sleep" option.
3. Ensure SUT goes to Sleep (S3).
4. Click "Power Actions" button under General tab->Select "Wake" option.
5. Ensure SUT wakes form Sleep (S3).

RW verification from Hibernate-sate (S4):(Intel LAN-(WGI218LM)

1. Select SUT under Device tab.
2. Click "Power Actions" button under General tab ->Select "Hibernate" option.
3. Ensure SUT goes to Hibernate (S4).
4. Click "Power Actions" button under General tab ->Select "Wake" option.
5. Ensure SUT wakes form Hibernate (S4).

RW verification for Restart-sate (R-S5):

1. Select SUT under Device tab.
2. Click "Power Actions" button under General tab ->Select "Reset" option.
3. Ensure SUT get restarted (R-S5).

RW verification from Shutdown (S5):

1. Select SUT under Device tab.
2. Click "Power Actions" button under General tab ->Select "Power off" option.
3. Ensure SUT goes to Shutdown (S5).

Alert Message :

1. Select SUT under Device tab.
2. Click "Power Actions" button under General tab ->Select "Alert" option.
3. Type any Message in the empty text area & select the time for Alert message to display on SUT,Press confirm.
4. Ensure the Alert Window with message was able to see on the SUT.

*Note:Repeat all operations for 5 Trails in AC.


Trial Results:-
Battery Level Sleep(S3) Hibernate(S4) Restart(R-S5) Shutdown (S5) Alert message
AC-mode Trial 1:
Trial 2:
Trial 3:
Trial 4:
Trial 5:
Trial 1:
Trial 2:
Trial 3:
Trial 4:
Trial 5:
Trial 1:
Trial 2:
Trial 3:
Trial 4:
Trial 5:
Trial 1:
Trial 2:
Trial 3:
Trial 4:
Trial 5:
Trial 1:
Trial 2:
Trial 3:
Trial 4:
Trial 5:

1.Confirm Client system wakes from S3/S4 using Meshcnetral wake.
2.Confirm Restart and shutdown operation.
3.Confirm alert message receiving on Client machine.
A
A
Multiple Host system access to the client at the same time.

1.Create two more Mesh central login"s.(Mesh-1 & Mesh-2)
2.Log in to the Mesh central ID in System A.
3.Go to My Account->Select the current Mesh under Administrative Meshes->select ADD.
4.Enter Mesh-1 username & select access type to Viewer & click Add access.
5.Provide Access to one more Mesh,enter Mesh-2 username & select access type to Administrative &click Add access.
6.Prepare two more systems with System -1 login with Mesh-1 & System-2 login with Mesh-2
7.Log-in to Mesh-1 in System-1 and confirm the client machine listed under devices.
8.Confirm the System-1 can able to view the Remote desktop & files,but unable to Wake & Transfer the files to&from the Client machine.
9.Log-in to Mesh-2 in System-2 & confirm the client machine listed under devices.
10.Confirm System-2 can access desktop/files/able to put & wake from S3/S4,able to transfer the files to&from the client machine.
11.Put the system to S3/S4 using the System-A & wake the system using System-A.
12.Make Simultaneous file transfer to&from the client machine to System A & System-2.
1.Confirm System A & System-2 can have the equal access to the Client machine.
2.Confirm System A & System-2 can able to wake the Client system.
3.Confirm System A & System-2 can transfer files to& from the client system at the same time.
4.Confirm System-1 can only able to view the desktop & files in the client system & unable to wake & access the client system.
A
A
Remote Desktop verification:

1.Select SUT under Device tab.-> Go to Desktop tab.
2.Connect to the SUT desktop using "Connect" button.
3.Ensure SUT desktop got displayed on Meshcentral-website(on System A).
4.Use Full screen button to get the Full screen view of the SUT.
5.Click "Ctrl+Alt+Del" button on the website to get the additional startup options on SUT.
6.Click "Charms" button on the Website to launch Charms bar on the SUT.
7.Click "Start" button on the Website to launch Metro screen on the SUT.
8.Open Internet Explorer & open multiple tabs/open & play youtube video.

*Note:Repeat the test in DC mode.
Confirm no hang in remote desktop & no connectivity loss
A
A

File Transfer verification with Remote system:

1.Select SUT under Device tab.-> Go to Files tab.
2.Connect to the SUT desktop using "Connect" button.
3.Ensure drives on SUT got displayed on Meshcentral-website (on System A).
4.Select any Folder/File & Verify the operation of Rename/Delete/Cut/Copy/NewFolder/Search/Refresh/Select None/Up/paste/Sort options.
5.Ensure all the options working as expected.
6.Check Hidden option to view the hidden files of SUT.
7.Copy Files/Folders from the SUT and paste in the System A.
8.Use "Upload" button to upload Folders/Files to SUT from System A.
9. To download, Double-click on the file or Right-click the file and select Download option

Result Table:-
File Size
Upload
Download
512MB
1GB
2GB
3GB
4GB
5GB


*Note:Repeat the test in DC mode
Confirm successful files transfer & no connectivity loss during file transfer.
A
A
Remote-Wake & access verification with LID close:

1.Prepare two systems,
System A:With Mesh central & System B added under Mesh
System B:With Intel-Remote Wake function enable & LID closed
2.Set the LID close action to "Do-nothing" in System B
3.Get the Access to the System B using Mesh central in System A.
4.Close the System B LID,confirm no loss in connectivity.
5.Transfer file ,get Remote desktop access of system B from System A.
6.Put the system to S3/S4 using Mesh central on System A.
7.confirm system B enters in to S3/S4.
8.Wake the system B from S3/S4 from System A.
9.Confirm System B wakes and can access the System B desktop & files.

*Note:
1.Repeat the test steps with LID close action set to Sleep/Hibernate/Shutdown.
2.Perform S3 & S4 operations supported.
1.Confirm system can Wake & access client desktop & files with client machine LID close.
2.Confirm no hang in remote desktop.
A
A
Remote Wake & access verification during Mobile Hotspot.:

1.Prepare two systems,
System A:With Mesh central & System B added under Mesh
System B:With Intel-Remote Wake function enable.
2.In System B create Mobile hotspot account(use Lenovo settings) & connect maximum of 5 clients to System B Mobile Hotspot.
3.Get the Remote desktop access of System B using Mesh central in System A.
4.Transfer files of variable size to&from the System B.
5.Confirm there will be no loss in connectivity.
6.Put System B to S3/S4 using System A.
7.Remotely Wake the System B from S3/S4 using system A.
8.Confirm system B wakes from S3.S4 & get the Remote access of System B.
1.Confirm there will no lost and drop in connectivity during remote desktop access and variable file transfer.
2.Confirm no hang in remote desktop.
A
A
Remote Wake & access from iOS /Android/Win using Mesh central :

1.Prepare System A with Remote Wake function Enable.
2.Open https://meshcentral.com//mobile on Ipad/Iphone(iOS).
3.Login to the Mesh central & access the Client machine desktop & files.
4.Put the system A to S3/S4 and remotely Wake using the Ipad/Iphone.
5.Make sure System A wakes from S3/S4.
6.Transfer variable file size to&from the System A using Mesh central on Ipad/Iphone.

Note:Perform same test steps with Android & Windows 8 OS.

1.Confirm there will no lost and drop in connectivity during remote desktop access and variable file transfer.
2.Confirm no hang in remote desktop.
A
A
Remote Wake & access verification with various Wireless modes & speed :

1.Prepare two systems,
System A:With Mesh central & System B added under Mesh
System B:With Intel-Remote Wake function enable.
2.On system B change value of the Wireless Mode of WLAN adapter.(DM->Network adapters->Intel WLAN adapter->Advance->Wireless Mode).
3.Change the value to other than default.
4.Open Mesh central on System A and get get the access of the System B.
5.Confirm System A can able to access the remote desktop/files of the System B.
6.Put System B to S3/S4 using System A.Confirm the System B enters to the respective state.
7.Wake System B from S3/S4 using System A.
8.Confirm System B wakes from S3/S4.

Note: Repeat the steps for all available Wireless Modes & speeds other than Auto(if applicable) for WLAN for 5 trials.
1.Confirm no loss in remote desktop & connectivity.
2.Confirm Smooth file transfer in all available modes.
3. Confirm Remote Wake of client machine from S3/S4.
A
A
Remote access verification with various Panel fit /Screen resolution/Rotation :

*Confirm Latest Intel Video driver installed prior to the Test

1.Prepare two systems,
System A:With Mesh central & System B added under Mesh
System B:With Intel-Remote Wake function enable.
2.Get the access of Remote Desktop of System B from System A.
3.Change the Screen resolution of System B other than default.
4.Confirm no loss in Remote Desktop & Connectivity.


Note: Repeat test steps for all available Screen Resolutions / Panel fits(if available) & Screen Rotations(from Intel Graphic properties)
1.Confirm no hangs & loss in remote desktop & connectivity.
2.Confirm Panel fit/Screen resolution/Rotation applied correctly on client system.

A
A
Remote access verification of Metro Apps :

1.Prepare two systems,
System A:With Mesh central & System B added under Mesh
System B:With Intel-Remote Wake function enable.
2.Get the access of Remote Desktop of System B from System A.
3.Launch the Metro screen of System B using "Start" button on System A.
4.Launch all Metro Apps available.
5.Confirm all Metro Apps launch properly & no loss of Remote desktop & connectivity.
1.Confirm no hangs & loss in remote desktop & connectivity.
2.Confirm all Metro Apps of client system can be accessed on Host machine
A
A
Remote Wake & access with Host & client on VPN connectivity.

1. Prepare two systems.
System A: Office network connection
System B: ADSL network connection
2. Let System B connect to VPN.
3. Confirm that System B connects successfully to VPN by pinging office network.
4. Get the access of Remote Desktop of System B from System A.
5. Perform again the above procedures/test items. (ISCT-Remote Wake verification using Mesh Central)
6. Confirm that the above procedures works fine, no loss of Remote Desktop & VPN connectivity
1.Confirm no hangs & loss in remote desktop & VPN connectivity.
2.Confirm no problem encountered while performing the above test items while System B is connected via VPN.
A
A



Intel-Remote Wake negative testing:
RESULT
Remarks & Criteria
Win-8 32 bit
Win 8 64 bit
Remote Wake & access with power-on or administrator password set in BIOS :

1.Prepare two systems,
System A:With Mesh central login & system B added under meshes.
System B:With Intel Remote Wake enabled & Mesh files installed.
2.Set BIOS Power-On-Password in BIOS,Save & Restart.
3.Boot to System B & enable Remote Wake option.
4.Get the access of System B from System A using Mesh Central.
5.Put System B to S3 state using System A.
6.Confirm System B enters to Sleep.
7.Wake the System B from S3 using System A(Meshcentral).
8.Confirm System B wakes from S3.
9..Put System B to S4 state using System A.
6.Confirm System B enters to S4-state.
7.Wake the System B from S4 using System A(Meshcentral).
8.Confirm System B do not wakes from S4.

Note:Repeat the test steps for system B Hard Disk password set in BIOS.

1.Confirm Client system wake from S3 using mesh central on host system even with BIOS passwords set.
2.1.Confirm Client system not wake from S4 using mesh central on host system even with BIOS passwords set.
A
A[Attachment-01]
Remote Wake verification with client system in DC mode. :

1.Prepare two systems,
System A:With Mesh central login & system B added under meshes.
System B:With Intel Remote Wake enabled & Mesh files installed.
2.Uplug the AC adapter & Boot the System B in DC mode.
3.Get the access of System B using System A(Mesh central).
4.Put System B to S3/S4 from System A.
5.Confirm System B enters to S3/S4.
6.Try to Wake System B from S3/S4 using System A-Mesh central.
7.Confirm System B not wakes from S3/S4

Note:Perform test steps for S3 & S4 supportably.
Confirm Client system wake from S3?S4 using mesh central on host system when Client system on DC-mode.
A
A
Remote Wake & access verification with 3G/4G connectivity:

1.Prepare two systems,
System A:With Mesh central login & system B added under meshes.
System B:With Intel Remote Wake enabled & connected to Mobile broadband internet.(WLAN/LAN not connected)
2.Get the access of System B from System A (Mesh central).
3.Confirm System A can access the System B desktop/files.
4.Perform variable file size transfer to/from System B.
5.Confirm File transfer occurs with out any loss in connectivity.
6.Put System B to S3/S4 using System A Meshcentral.
7.Confirm System B enters to S3/S4.
8.Wake System B from S3/S4 using System A meshcentral.
9.Confirm System B do not Wakes from S3/S4.

Note:Confirm the shutdown & restart operations on System B from System A Mesh central.


1.Confirm host system can access the files & desktop of the Client system.
2.Confirm host system can put the system to S3/S4/Shutdown/restart the client machine.
3.Confirm the host system unable to wake the Client system from S3/S4 using host system.
A
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)
TEMS Reviewer Log:03/21/2013 04:01:32 PM by Muralidharan Seshadri/LENOVO (Review Comment: Reviewed)
Review Logs
Keywords:   None
Requirements :   None
Attached files :
Mesh Central_setup.pptx - Mesh Central_setup.pptx (2798348 bytes, ) 07/03/2015

Update History:
This document is not yet modified.