Test Case

Show / Hide direct link   <MAIN> 3004PA: AC:Peer to Peer Community Function Test - PP-80397



Version 1.7
Created on 03/12/2004 11:40:41  by Muralidharan Seshadri
Last modified on  07/04/2016 14:27:01  by msesha_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
Locations:Inhouse: AWS and Cambridge, Inhouse: AWS, Inhouse: Cambridge, Compal, Flextronics, Quanta, Wistron Owned By:Eiji Ogata/LENOVO
Objective:To verify Peer to Peer function of AC for all the supported WL adapters
CRITERIA

Successful P2P function

No system malfucntion

EUT QUANTITY

Minimum of two systems

EQUIPMENT

Networking facilities.

Critical Attribute:[0] : WLS - Wireless

CONFIGURATION
REFERENCE PROCEDURE
STATISTIC INFO
Operating System Win7- 64bit Win7- 32bit Total
Test Points
Duration
Workload
# Step actions Win7- 64bitWin7- 32bit
1 Peer to Peer Community Verification AA
2 Wireless Mode (a/b/g) & profile Verification AA
3 Power Management Test AA
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.

Perform all tests in both AC & DC mode.

Perform all test in both Administrator & User mode.

Known Limitations/Restrictions/Information

Known Limitations

1. When two Ethernet adapters are configured, TCP/IP will be obtained by OS. Even if we use IPconfig to release all the IP, then after PM, system will get the IP after searching the DHCP server. To avoid getting the IP address when we use Access Connection, select the option "Disconnect from the Network when I switch to a different location Profile".

2. When user create the profile, automatic location switching is enabled by the default for both wired and wireless adapter. The "Automatic location switching" option will not be available to select. This is working as design.

3. Windows Firewall is only available for windows XP SP2.

Restriction

1. Even "Allow all users of this system to create and apply loation profiles" Global settings option check box is checked, limited user account can not modify or create the setting for TCP/IP settings or security settings of local driver share, firewall settings due to Widnows security protection. Such setting is used with Windows default settings. Default is not checked.

2. Global settings can be only modified by the user when the logon privilege is administrator privilege.

3. The global settings option "Disable Adhoc connection type option in wireless LAN profiles" is not applicable, if the user create the profile using WIndows wireless LAN property window.

4. While joining or leaving Peer to Peer community, GUI may blank for a few seconds several times, this is by AC design (CMVC # 94378f_1)

5. Send File, Chat and Whiteboard are not supported in Windows 7 and Vista because Netmeeting is not available for those OS. Access Connections uses Netmeeting function for those operation. (Reference defects: ECR56658, ECR56652)

6. Access Connections will not give sound effect when P2P connected in Windows 7.Its working as design and same as old version of AC [Reference Defect: ECR103423]

Information

1. When "Allow all users of this system to create and apply loation profiles" check box is checked, it allows user to create the location profiles and enables location switching regardless of the windows logon privilege (administrator or limited users). However, the limited user will not be able to edit the profiles created in the user mode with administrator privilege.

2. Wireless profiles will be listed in the upper part of the profile list and the Ethernet profiles will be displayed at the lower part of the location profile list on "Automatic switching profile priority window". Due to the faster speed, the Ethernet profiles have higher priority than the wireless profiles.

3. Secure Peer to Peer connection mode require IPSec security protocol (Windows Support Tools supplicant), which can be installed from ThinkPad preload directory C:\Support\Tools.

4. Atheros WL mode is SKU specific. US SKU doesnt support "802.11a" mode for AdHoc, however JP SKU supports "802.11a" mode for Atheros.

Peer to Peer Community Verification

Test Item
Check Item / Criteria
Configuration
Result
Win 7
GUI Verification [UR-03280AP]

1.Launch Access Connection

2.Click Advanced

3.Go to Tools>Global Settings

4.Uncheck "Disable the Peer to Peer community feature"

5.Go to P2P tab

6.Click P2P Community

7.Check the content of the p2p community

For Windows 7 - "Use Peer to Peer Community to wirelessly chat, send files, and whiteboard with nearby ThinkPad computers" should not be displayed

For Windows 7,"Use Peer to Peer Community to wirelessly chat, send files, and whiteboard with nearby ThinkPad computers"

should not be displayed

Creating/Joining a Peer to Peer community

Use 2 systems and follow the below procedures to join the Peer to Peer Community.

1. Launch Access Connections.

2. Switch to Advanced Mode

3. Enter a passphrase (Passphrase must be at least 8 digits, and should be identical on both systems).

4. Click on "Join" button.

5. The Peer to Peer Community's connection will be established successfully

Windows Remote Assitance (Win 7)

On both System A and System B

1. Start >> Control Panel >> System and Security >> under System click "Allow remote access"

2. Under "Remote" tab make sure following options are checked :

- Allow Remote Assistance connections to this computer

- Allow connections from computers running any version of Remote Desktop (less secure)

3. Click Apply >> Ok.


(Allowremoteassistance.jpg)

Perform below procedures while both System A and System B are connected through Peer to Peer community in access connections.

1. System B : Start >> in search box type "Windows Remote Assistance" >> click "Windows Remote Assistance".

2. System B : Under "Do you want to ask for or offer help?" choose "Invite someone you trust to help you"

3. System B : Under "How do you want to invite your trusted helper" choose "Save this invitation as a file".

4. System B : Save the invitation file in a removable memory key and note of the password shown.

5. System A : Start >> in search box type "Windows Remote Assistance" >> click "Windows Remote Assistance".

6. System A : Under "Do you want to ask for or offer help?" choose "Help someone who has invited you".

7. System A : Under "Choose a way to connect to the other person's computer" choose "Use an invitaion file"

8. System A : Attached the removable memory key with invitation file from system A.

9. System A : Open invitation file from System A and input correct password. Click Ok.

10. System B : In "Would you like to allow System A to connect to your computer" click Yes.

11. system A : Confirm you can see System B desktop in Windows Remote Assitance through AC P2P community.

12. System A : In Windows Remote Assitance menu, click "Request control"

13. System B : Allow System A to control desktop.

14. System A : Confirm system A can control System B through AC P2P community.

15. System A : In Windows Remote Assitance menu, click "Chat".

16. System A/B : Confirm both System A and B can do Chat with each other.

Repeat Procedure 1-16 with System B controling System A.

Windows Remote Assitance GUI

.

  • Make sure that no error message appears while connecting to the Peer to Peer community.
  • Make sure connnection is successful and each system can ping the other system.
  • Verify that no error appears by clicking on "Stop" button while the the Peer to Peer community is establishing connection.
  • The connected systems should be seen on the Peer to Peer community status window.
  • Make sure that the GUI display correctly and no text are truncated.

Make sure AC P2P community connection is stable during Windows Remote Assistance

Standalone
A
A
Leaving a Peer to Peer community

1. While connected in a Peer to Peer community, click on "Leave" button.

2. Both systems should be disconnected from the Peer to Peer community.

3. While connected in a Peer to Peer community, create any wireless profile and apply it.

4. Click "Yes" button when the popup "You will leave the current Peer to Peer community. Do you want to proceed?" window comes.

5. Verify that no error appears while switching to a wireless profile from Peer to Peer community and the wireless profile shoud establish connection to the access point.

  • Make sure that no error message appears while leaving the Peer to Peer community.
  • Make sure that the systems are disconnected form the Peer to Peer community properly and verify that the system does not appear on the Peer to Peer community status window after leaving.
Standalone
A
A
Disabling Peer to Peer community feature [UR-2025]

1. Launch Access Connections

2. Switch to Advanced Mode, Go to Tools-> Global Settings > Network tab

3. Select the option "Disable the Peer to Peer community feature" and click OK

4. Confirm that the Peer to Peer tab is removed from Access Connections GUI

  • No error msg appears
  • Confirm Disable Peer to Peer community feature option is working properly
Enabling Peer to Peer Community feature

1. Launch Access Connections

2. Switch to Advanced Mode, Go to Tools-> Global Settings > Network tab

3. Unselect the option "Disable the Peer to Peer community feature" and click OK

4. Confirm that the Peer to Peer tab is available on Access Connections GUI

5. Verify if Peer to Peer function is working

  • No error msg appears
  • Confirm Enable Peer to Peer community feature option is working properly
  • Verify Peer to Peer function works
Send File..

Perform the below procedures to send file, while both systems are connected through Peer to Peer community.

1. On "System A", highlight "System B" and click on "Send File.." button.

2. Windows Netmeeting's "File Transfer" window will appear.

3. Click on "Add Files" button or "File => Add Files" Menu.

4. Click on "Send All" button or "File => Send All/Send A File" Menu.

5. Once the file transfer process is completed, click on "Received Files" button on "System B" and verify that the files were successfully transferred.

Perform the above mentioned operations at least 5 times to transfer 10 Mbytes file.

Note:

Send File, Chat and Whiteboard are not supported in Windows 7 and Vista because Netmeeting is not available for those OS. Access Connections uses Netmeeting function for those operation. (Reference defects: ECR56658, ECR56652)

But AC GUI for P2P will still display "Use Peer to Peer Community to wirelessly chat,send files, and whiteboard with nearby Thinkpad computers" in Win 7

[UR-02931SG]

Note:

When Sending file from System A to System B, there will not be a prompt for Received file notification in "System B" after the first time.

(Reference Defects :ECR77631)

  • Make sure that no error messages appear during the file transfer process and verify that the files are successfully transfereed.
Standalone
A
A
Chat...

Perform the below procedures to "chat" with the other system, while both systems are connected through Peer to Peer community.

1. On "System A", highlight "System B" and click on "Chat.." button.

2. The "Chat" window will appear.

3. Type the messages through chat and communicate with "System B".

4. Close the "Chat" window to end the chatting.

Note:

Send File, Chat and Whiteboard are not supported in Windows 7 and Vista because Netmeeting is not available for those OS. Access Connections uses Netmeeting function for those operation. (Reference defects: ECR56658, ECR56652)

But AC GUI for P2P will still display "Use Peer to Peer Community to wirelessly chat,send files, and whiteboard with nearby Thinkpad computers" in Vista ,Win 7

Note:

When Sending file from System A to System B, there will not be a prompt for Received file notification in "System B" after the first time.

(Reference Defects :ECR77631)

  • Make sure that "System A" can communicate with "System B" and vice versa.
  • Make sure that no error messages appear during chatting.
Standalone
A
A
Whiteboard...

Perform the below procedures to launch "Netmeeting's Whiteboard" application, while both systems are connected through Peer to Peer community.

1. On "System A", highlight "System B" and click on "Whiteboard.." button.

2. The "Whiteboard" application window will appear.

3. Draw shapes or write text on the "Whiteboard" window.

4. Verify that the same text and shapes appear on "System B".

5. Close the "Whiteboard" application window.

6. Save the file and verify that the file's contents are not corrupted.

Note:

Send File, Chat and Whiteboard are not supported in Windows 7 and Vista because Netmeeting is not available for those OS. Access Connections uses Netmeeting function for those operation. (Reference defects: ECR56658, ECR56652)

But AC GUI for P2P will still display "Use Peer to Peer Community to wirelessly chat,send files, and whiteboard with nearby Thinkpad computers" in Win 7

Note:

When Sending file from System A to System B, there will not be a prompt for Received file notification in "System B" after the first time.

(Reference Defects :ECR77631)

  • Make sure that the systems can share the whiteboad application and veify that the same text and shapes appear on the other system.
  • Make sure that the file's contents are not corrupted and the file is saved properly.
Standalone
A
A
Received Files... [UR-2650SG]

1. Launch Access Connections

2. Switch to Advanced Mode

3. Go to Tools tab--> Click P2P button

4. On Peer to Peer Options box, click the '...' button to choose the location of the 'Received Files' folder

5. Select desired location or leave default then click OK

6. Perform the procedures to send file, while both systems are connected through Peer to Peer community.

7. Once the file transfer process is completed, Received button on System B should not be greyed-out. Click on "Received Files" button on "System B" and verify that the files were successfully transferred.

8. Check the location of the received file if it is the right location you assigned

P2P Notifications [UR-03097SG]

1. Launch Access Connections

2. Switch to Advanced Mode

3. Go to Global Settings --> Notification --> "Show ThinkVantage Access Connection Status icon in task tray" is checked.

4. Go to Global Settings > Network tab --> Unselect the option "Disable the Peer to Peer community feature" and click OK

5.Confirm that the Peer to Peer tab is available on Access Connections GUI.

6.Type a passphrase and click Join.

7.Notice that AC tray icon shape is changed and baloon notifications come up.

Note:

In Avanced --> Tools --> User Preferences --> "Do not show balloon tips from Access Connections system tray icon" .

Even if this option is checked or unchecked, balloon notifications will be noticed as long as"Show ThinkVantage Access Connection Status icon in task tray" is checked.

Balloon notifications will be popping up when joining to a peer in P2P as long as

"Show ThinkVantage Access Connection Status icon in task tray" is checked.

Wireless Mode (a/b/g) & profile Verification

Test Item
Check Item / Criteria
Configuration
Result
(Perform in both AC & DC mode)
Win 7 32bit
Win 7
64 bit
Wireless Mode (a/b/g) Verification

1. Launch Access Connections on two systems "System A" & "SystemB"

2. Switch to Advanced Mode

3. Click on "Configure => Tools tab --> P2P button" file menu.

4. On Peer to Peer Options box, change the Wireless Mode to "802.11a" and click "OK".

5. Enter a passphrase (Passphrase must be at least 8 digits, and should be identical on both systems).

6. Click on "Join" button.

7. The Peer to Peer Community's connection will be established successfully.

Perform the same procedure for 802.11b & 802.11g mode by changing the wireless mode to "802.11b" and "802.11g" at step 3.

(802.11b & 802.11 g are operating at the same frequency and they are compactable with each other).

Note:

Atheros WL mode is SKU specific. US SKU doesnt support "802.11a" mode for AdHoc, however JP SKU supports "802.11a" mode for Atheros.

As such some Atheros cards will have "802.11a" mode whereas some Atheros cards will not have "802.11a" mode in Access Connections (which is due to the SKU).

  • Make sure that no error message appears while connecting to the peer to peer community.
  • Make sure connnection is successful and each system can ping the other system.
  • Make sure that the connection is established with the configured wireless mode (802.11a/b/g).
Standalone
A
A
Wireless Profile Verification after P2P

1. Launch AC and connect two systems, "System A", "System B", using

AC through Peer to Peer community.

2. Create any wireless profile in "System A" and apply it.

3. Make sure that the wireless profile gets connected properly and there is no error message.

4. Join back to Peer to Peer community.

5. Make sure that the Peer to Peer community connects properly and

there is no error message.

6. Leave Peer to Peer community

7. WL profile should connect automatically

  • Confirm that the status shown in system Tray is consistent with the main GUI.
  • Make sure that no error message appears while switching beteen wireless profile and P2P community and the connectivity is working properly.
Standalone
A
A

Power Management

Test Item
Check Item / Criteria
Configuration
Result
(Perform in both AC & DC mode)
Win 7
Power Management

1. Launch AC and connect two systems, "System A", "System B", using AC through Peer to Peer community.

2. Suspend/Resume the "System A", while Peer to Peer community connection is established.

3. Hibernate/Resume the "System A", while Peer to Peer community connection is established..

Perform PM operation item at least 5 times

  • Make sure that there is no connection to Peer to Peer community after power management.
  • Make sure that "System A" does not appear on System B's Peer to Peer community status window when "System A" is in Standby/Hibernate mode.
  • Make sure that "System B" should be disconnected from the Peer to Peer community after a few seconds when "System A" is in Standby/Hibernate mode.
  • After resume , Verify the functionality of the Peer to Peer community.
  • On Resuming from PM, check the system tray for balloon information.
  • Confirm that the status shown in system Tray is consistent with the main GUI.
Standalone
A
A
Restart / Shutdown

1. Launch AC and connect two systems, "System A", "System B", using AC through Peer to Peer community.

2. Restart the "System A", while Peer to Peer community connection is established.

3. Shutdown the "System A", while Peer to Peer community connection is established.

Perform this operation at least 5 times

  • Make sure that there is no connection to Peer to Peer community after restart/shutdown.
  • Make sure that "System A" does not appear on System B's Peer to Peer community status window while "System A" is restarting or shutdown.
  • Make sure that "System B" should be disconnected from the Peer to Peer community after a few seconds when "System A" is restarting/shutingdown.
  • After restart/shutdown , Verify the functionality of the Peer to Peer community.
  • After shutdown/restart, check the system tray for balloon information.
  • Confirm that the status shown in system Tray is consistent with the main GUI.
Standalone
A
A

OTHER DETAILS

EUT Quantity : Minimum of 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) Peer to Peer Community Function Test (While doing JP coverage, verify the japanese characters, error messages and help menu contents)

Test Item
Configuration
Result
Win 7 32bitq
Win 7 64 bit
1. Peer to Peer Community Verification
Standalone / Docking station
A
A
2. Wireless Mode (a/b/g) & profile Verification
Standalone / Docking station
A
A
3. Power Management Test
Standalone / Docking station
A
A

TEMS Reviewer Log:
Review Logs
Keywords:   None
Requirements :   None
Attached files :

Update History:
Modified last: 2016-04-07 14:27:01.86, by Muralidharan Seshadri_nw
Modified last: 2016-04-07 14:27:00.721, by Muralidharan Seshadri_nw