Sl No. |
Test case Id |
Test case description |
Steps |
Expected Result |
Type |
Status |
Is automated |
Is automatable |
Priority |
1 |
Enable_VPN_public_address |
Enable VPN for public IP address |
prerequisite: have a vm provisioned using virtual networking |
1.enabling vpn should succeed |
Functional |
Pass |
no |
TBD |
P1 |
2 |
login_VPN_windows_XP |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
VPN connect should be succesful and should be able to see any hosts on the virtual network |
Functional |
|
no |
TBD |
P1 |
3 |
login_VPN_windows7 |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
VPN connect should be succesful and should be able to see any hosts on the virtual network |
Functional |
Pass |
no |
TBD |
P1 |
4 |
login_VPN_windows_Vista |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
VPN connect should be succesful and should be able to see any hosts on the virtual network |
Functional |
|
no |
TBD |
P1 |
5 |
login_VPN_windows_2003 |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
VPN connect should be succesful and should be able to see any hosts on the virtual network |
Functional |
Pass |
no |
TBD |
P1 |
6 |
login_VPN_windows_2008 |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
Configure VPN client on windows (http://intranet.lab.vmops.com/engineering/release-2.2-features/VPN/?searchterm=VPN) |
VPN connect should be succesful and should be able to see any hosts on the virtual network |
Functional |
|
no |
TBD |
P1 |
7 |
login_VPN_mac |
TBA |
TBA |
TBA |
Functional |
|
no |
TBD |
P1 |
8 |
remove_VPN_user_and_connect |
Remove VPN user and attempt to connect using that user |
1. Enable VPN for public address |
connection should not happen |
Negative |
|
no |
yes |
p1 |
9 |
remove_VPN_user_credentials |
Remove VPN userx and attempt to connect using another usery credentials |
1. Enable VPN for public address |
connection should not happen |
|
|
no |
yes |
p1 |
10 |
remove_VPN_user_when_connected |
remove vpn user, when session is initiated |
1. Enable VPN for public address |
TBA |
negative |
|
no |
TBD |
p1 |
11 |
|
run a client/server through vpn connection (http,mysql,iperf) |
TBA |
TBA |
negative |
|
no |
TBD |
p1 |
12 |
port_accessibility_VPN |
ensure all ports are accessible through vpn. |
TBA |
TBA |
negative |
|
no |
TBD |
p1 |
13 |
VPN_user_limit |
VPN remote access user limit tests |
prerequisite: change management configuration setting of remote.access.vpn.user.limit |
Provisioning of users after the limit should fail |
negative |
|
no |
yes |
p1 |
14 |
VPN_port_forward_enable |
set a port forward for UDP: 1701 and enable VPN |
set a port forward rule for the udp port 1701 over which L2TP works |
port forward should prevent VPN from being enabled |
Functional |
Pass |
no |
yes |
p2 |
15 |
VPN_enable_port_forward |
Enable VPN , add VPN user and set a port forward for UDP port 1701 |
1.Enable a VPN connection on source NAT |
Should result in error saying that VPN is enabled over port 1701 |
Functional |
Pass |
no |
yes |
p2 |
16 |
VPN_disable_enabled |
Diasable VPN access after it was enabled |
1. Have VPN access enabled and have few users added to it. |
1. All the active session of the user should get disconnected. |
Functional |
|
no |
yes |
p1 |
17 |
VPN_enable_disabled |
Enable a VPN access that was disabled perviously. |
1,Have VPN access enabled and have few users added to it. |
1.When VPN access is enabled back , a new key will be generated. |
Functional |
|
no |
yes |
p1 |
18 |
VPN_add_user_existing |
Add new user to VPN when there are already existing users. |
|||||||
Add new user to VPN when there are already existing users. |
.We should be able to successfully establish a VPN connection using the newly added user credential. |
Functional |
no |
yes |
p1 |
||||
|
|
|
|
|
|
|
|
|
|
21 |
VPN_reboot_router_enabled |
Reboot of routers when VPN access is enabled. |
1.Enable VPN access. Add few VPN users. |
After reboot of routers , VPN access should continue to work as expected. |
Functional |
no |
yes |
p2 |
|
22 |
VPN_add_user_router_down |
When Router is down , try to add a VPN user. |
Enable VPN access. Add few VPN users. |
1. Adding the VPN entry should not report failure. |
Functional |
no |
yes |
p2 |
|
23 |
VPN_add_VPN_user_global_admin |
As global admin, add a new VPN user to an existing VPN entry that was created by another account. |
1. Create a new user and deploy few Vms. |
1.The newly added VPN user should get configured to the router of the user account. |
Functional |
no |
yes |
p2 |
|
24 |
VPN_add_VPN_user_domain_admin |
As domain admin, add a new VPN user to an existing VPN entry that was created by another account. |
1. Create a Domain admin user and deploy few Vms. |
1.The newly added VPN user should get configured to the router of the user account. |
Functional |
no |
yes |
p2 |
|
25 |
VPN_user_add_remove_usage |
verify vpn user added /remove usage |
1.Create a account |
1.Verify after step 4 VPN.USER.ADD event is registered for this account in cloud.usage_event table |
Functional |
yes |
yes |
p1 |