V4/Authentication Indicators/Test Plan
Name: V4/Authentication Indicators/Test Plan
Target version: 4.4.0
Design: V4/Authentication_Indicators
Reviewer: missing
Last updated: 2016-05-31 by Lryznaro
Contents
- 1 Overview
- 2 Test Plan
- 2.1 Test case: Create new service entry with specified authentication indicator
- 2.2 Test case: Update existing service entry to have authentication indicator
- 2.3 Test case: Update existing service entry to different authentication indicator
- 2.4 Test case: Verify that both authentication indicators can be set for a service
- 2.5 Test case: Try to access service without authentication indicators
- 2.6 Test case: Try to access service with insufficient authentication
- 2.7 Test case: Try to access service with sufficient authentication
- 2.8 Test case: Try to access service with different authentication type
- 2.9 Test case: Try to access service with one of possible tokens
Overview
Test Plan
Test case: Create new service entry with specified authentication indicator
Autotest {{{autotest}}} | |
Setup Service entry does not exist. | |
Actions Create new service entry with '--auth-ind=otp' or '--auth-ind=radius' option. |
Expected results Service entry should be added. |
Test case: Update existing service entry to have authentication indicator
Autotest {{{autotest}}} | |
Setup Service entry with no authentication indicator already exists. | |
Actions Update existing entry with '--auth-ind=otp' or '--auth-ind=radius' option. |
Expected results Authentication indicator should be added. |
Test case: Update existing service entry to different authentication indicator
Autotest {{{autotest}}} | |
Setup Service entry with an authentication indicator already exists. | |
Actions Update existing entry with different type of authentication indicator. |
Expected results Authentication indicator should be updated. |
Test case: Verify that both authentication indicators can be set for a service
Autotest {{{autotest}}} | |
Setup Service entry with no authentication indicator already exists. | |
Actions Try to update the service to contain both 'otp' and 'radius' indicators. |
Expected results Should be successfull. |
Test case: Try to access service without authentication indicators
Autotest {{{autotest}}} | |
Setup User already exists with authentication types 'otp', 'radius' and 'password'. Service with no authentication indicators set already exists. | |
Actions
|
Expected results Should grant access for all types of authentication. |
Test case: Try to access service with insufficient authentication
Autotest {{{autotest}}} | |
Setup User already exists with authentication types 'otp', 'radius' and 'password'. Service1 with authentication indicator 'otp' or 'radius' already exists. Service2 with no authentication indicator already exists. | |
Actions
|
Expected results
|
Test case: Try to access service with sufficient authentication
Autotest {{{autotest}}} | |
Setup User already exists with authentication types 'otp', 'radius' and 'password'. Service1 with authentication indicator 'otp' or 'radius' already exists. Service2 with no authentication indicator already exists. | |
Actions
|
Expected results
|
Test case: Try to access service with different authentication type
Autotest {{{autotest}}} | |
Setup User already exists with authentication types 'otp', 'radius' and 'password'. Service with authentication indicator 'otp', alternatively 'radius', already exists. | |
Actions
|
Expected results
|
Test case: Try to access service with one of possible tokens
Autotest {{{autotest}}} | |
Setup User already exists with authentication types 'otp', 'radius' and 'password'. Service with both authentication indicators already exists. | |
Actions
|
Expected results
Run test case again for second authentication type. |