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. locate router/public ip (API: listPublicIpAddresses) for vm provisioned and enable vpn( API: createRemoteAccessVpn)
2. note preshared key
3. create a vpn user using addVpnUser API(using valid username and password)
4. from a standalone windows machine (not within the cloud) configure vpn to point to public ip address
5. connect to vpn connection within windows
6. ssh (using putty or any other terminal client) to the vm provisioned earlier

  1.enabling vpn should succeed
  2.ui should return psk
  3. user should be created successfully
  4. setup of vpn network should succeed
 5. connection to vpn should succeed
  6. user should be able to log into provisioned vm as well as see any hosts on the virtual network the vpn tunnels into.

Functional

Pass

no

TBD

P1

2

Enable VPN_non-sourceNAT IP

Enable VPN for non-sourceNAT IP

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

Fail(CLOUDSTACK-238)

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

 

 

 

 

 

 

 

 

 

 

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

Pass

no

TBD

P1

7

 

 

 

 

 

 

 

 

P1

8

remove_VPN_user_and_connect

Remove VPN user and attempt to connect using that user

1. Enable VPN for public address
2. Add a VPN user
3. Remove the VPN user
4. Now, try to connect using VPN with delete user credentials

connection should not happen

Negative

Pass

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
2. Add a VPN userX.
4. Now, try to connect using VPN with userY(another account vpn user)credentials

connection should not happen

 

Pass

no

yes

p1

10

remove_VPN_user_when_connected

remove vpn user, when session is initiated

1. Enable VPN for public address
2. Add a VPN user.
4. Now, try to connect using VPN with user credentials
5. Delete VPN user created in step 2

TBA(Connection was discoinnected once we delete the user)

negative

Pass

no

TBD

p1

11

VPN_user_limit

VPN remote access user limit tests

prerequisite: change management configuration setting of remote.access.vpn.user.limit

1. provision more users than is set in the limit

Provisioning of users after the limit should fail

negative

Pass

no

yes

p1

12

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

13

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
2.Add a VPN user
3.add a port forward rule for UDP port 1701

Should result in error saying that VPN is enabled over port 1701

Functional

Pass

no

yes

p2

14

VPN_disable_enabled

Diasable VPN access after it was enabled

1.    Have VPN access enabled and have few users added to it.
2.    Have VPN access being used by one of the users curretly.
3.    Disable VPN access from cloudstack UI.

1.    All the active session of the user should get disconnected.
2.    VPN session should get disconnected.

Functional

Pass

no

yes

p1

15

VPN_enable_disabled

Enable a VPN access that was disabled perviously.

1,Have VPN access enabled and have few users added to it.
 2.Disable VPN access from cloudstack UI or Using API.
3.Enable VPN access from cloudstack UI or Using API

1.When VPN access is enabled back , a new key will be generated.
2.All the existing users (from before VPN being disabled) should still be persent in the VPN user list.
3. Using the new key , the existing users should be able to vpn successfully.

Functional

Pass

no

yes

p1

 

 

 

 

 

 

 

 

 

 

 

 

16

VPN_reboot_router_enabled

Reboot of routers when VPN access is enabled.

1.Enable VPN access. Add few VPN users.
2.Make sure that VPN access works as expected.
3.Reboot the router on which this VPN is programmed.

After reboot of routers , VPN access should continue to work as expected.

Functional

Pass

yes

p2

17

VPN_add_user_router_down

When Router is down , try to add a VPN user.

Enable VPN access. Add few VPN users.
2.Make sure that VPN access works as expected.
3.Stop the router.
4. Add new user to an existing VPN entry.

1. Adding the VPN entry should not report failure.
2.When the Router is started , this VPN entry should be programmed successfully.
3.All the existing users and the newly added VPN users should be able to VPN successfully.

Functional

Fail(need to change the testcase and also seeing issue#it deleting all existing vpn users when fail to add vpn users

yes

p2

18

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.
2. Enable VPN access. Add few VPN users.
3.Make sure that VPN access works as expected.
4.As global Admin , add VPN user to this user's existing VPN entry.

1.The newly added VPN user should get configured to the router of the user account.
 2.We should be able to use this newly created user credential to establish a VPN connection that will give access all the VMs of this user.

Functional

Pass

yes

p2

19

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.
2. Create a new user under this domain and deploy few Vms.
3. Enable VPN access. Add few VPN users.
4.Make sure that VPN access works as expected.
5.As Domain Admin , add VPN users to this user's existing VPN entry.

1.The newly added VPN user should get configured to the router of the user account.
2.We should be able to use this newly created user credential to establish a VPN connection that will give access all the VMs of this user.

Functional

Pass

no

yes

p2

20

VPN_user_add_remove_usage

verify vpn user added /remove usage

   1.Create a account
    2.Create a Vm for this account
    3.Create a VPN on  the IP associated with this account
    4.Add user to VPN
    5.Generate usage record
    6.List usage record for this acocunt and for usage type =  14
    7.Delete the created USER of the VPN from the account
    8.Generate usage record
    9.List usage record for this acocunt and for usage type =  14
   10.Delete this account.

1.Verify after step 4 VPN.USER.ADD event is registered for this account in cloud.usage_event table
2.After step 6 Verify correct usage time is recorded for VPN user
 3.Verify after step 7 VPN.USER.Delete event is registered for this account in cloud.usage_event table
 4.After step 9 Verify correct usage time is recorded for removed VPN user

Functional

blocked(cloudstack-81)

yes

p1

  • No labels