TEST CASE Example

Administration

Owner:
Scope: To validate known functions of the Administration features.
Originator:
Status: Active
Document ID:
Location:

Change History

Issue Date Handled by Comments

Created. dd-mmm-yyyy
 Table of Contents
1. Introduction.......................................................................................................................... 4
2. Scope................................................................................................................................... 4
3. Requirements....................................................................................................................... 4
4. Related Documents.............................................................................................................. 4
5. Traceability Matrix................................................................................................................4
6. Notes................................................................................................................................... 5
7. Test Cases - Administration..................................................................................................5
7.1 Test Item: Registration Request Form..............................................................................5
7.2 Test Item: Admin Login.................................................................................................10
7.3 Test Item: Create User..................................................................................................10
7.4 Test Item: Edit User......................................................................................................14
7.5 Test Item: Basic Delete and Disable...............................................................................17
7.6 Test Item: Test user.....................................................................................................19
7.7 Test Item: Admin creates user(s) and assign(s) to group(s) using batch scripts....................19
7.8 Test Item: Delete and Disable users logged into Company................................................20
7.9 Test Item: Email to All Users.........................................................................................28
7.10 Test Item: Logout.....................................................................................................30
7.11 Test Item: Multiple browser window usage..................................................................31
7.12 Test Item: Change Admin password............................................................................31
7.13 Test Item: SRC user list.............................................................................................33
7.14 Test Item: Sending log files to Company Support..........................................................34
7.15 Test Item: Refresh after submits..................................................................................36
7.16 Test Item: User/Admin Level Privileges.......................................................................36
7.17 Test Item: Session validation......................................................................................37
7.18 Test Item: Provision.......................................................................................................38
7.19 Test Item: Client Admin Function....................................................................................39
1. INTRODUCTION

The purpose of this test case is to test and validate the functionality of the Company Administration
features.

2. SCOPE

To validate all known functions of the Company administration features.

3. REQUIREMENTS

Discuss any derived requirements and/or requirements that need clarification or are necessary for
completion prior to the execution of the test cases listed in this document.
For example:
The input criteria necessary for the Golden Master CD testing includes:
 Satisfactory completion of the agreed upon QA testing requirements – including project relevant test
plans, procedures, and test cases.
 Creation of Golden Master CD from the Software Maintenance Group.
 Software Release Matrix as delivered from the Product Marketing and Software Maintenance
Groups.

4. RELATED DOCUMENTS

Add a list and links to supporting documents here, e.g., RFCs, other design documents, standards
specifications, etc…

5. TRACEABILITY MATRIX

The following table describes the relation mapping between requirements from the requirement
specification documents (Company Extensions Design.v02, UserAdminDesign.v04.doc) and
corresponding test items, which validate their implementation

Requirement Validated by:

# Req-1 Test Item xxx
# Req-2
# Req-3
# Req-4
# PRV-1 Test Item xxx
Bug #1234 Test xxx.xxx
Bug #1235 Test xxx.xxx
Bug #1236 Test xxx.xxx
Bug #1237 Test xxx.xxx
# REQ5 Test Items from xx.xx to
xx.xx
# REQ6
 # REQ7
# REQ8
# REQ9
# REQ10

6. NOTES

Add any generally relevant notes here.

7. TEST CASES - Administration

This section should provide the set of test cases that are used in the process of testing specific features
and functions. Include the following checklist.

Follow the checklist in order and perform each test. Check the Pass work Fail box to the left according to
the results. Note bugzilla number if/when a bug is submitted resulting from a failed test

Test Tester Name Date Browser & Execution Time Did all the Tests Pass?
Run # Version

7.1 Test Item: Registration Request Form.

Scope: Test various field input on the Registration Request Form.

Action: Submit Registration request.
Test Notes and Preconditions: Open the user registration request form from the users tab.
Verification Steps: Verify the user has been registered with the given details.
Scenario 1: Test leaving a required field blank on the new user registration
S# Action Input Value Expected Results Actual P/F Autom
Results ated
7.1.1 Submit Registration First Name = blank, Error message should be
request… Other fields valid displayed for invalid First Name.
7.1.2 Submit Registration Last Name = blank, Error message should be
request… Other fields valid displayed for invalid Last Name.
7.1.3 Submit Registration Email = blank, Error message should be
request… Other fields valid displayed for invalid Email.
7.1.4 Submit Registration Phone number = blank, Error message should be
request… Other fields valid displayed for invalid Phone
number.
7.1.5 Submit Registration Company = blank, Error message should be
request… Other fields valid displayed for invalid Last Name.
7.1.7 Submit Registration User ID = blank, Error message should be
request… Other fields valid displayed for invalid User ID.
S# Action Input Value Expected Results Actual P/F Autom
Results ated
7.1.8 Submit Registration Password = blank, Error message should be
request… Other fields valid displayed for invalid Password.
7.1.9 Submit Registration Confirm Password = Error message should be
request… blank displayed for invalid
Other fields valid confirmation password
7.1.10 Submit Registration All fields blank Error message should be
request… displayed.

Scope: Test various field input on the Registration Request Form.

Scenario 2: Test minimum number of characters accepted for each field.
S# Action Input Value Expected Results Actual P/F Autom
Results ated
7.1.11 Submit Registration First Name = max chars Registration request
request… Last Name = max chars should be accepted.
Email = max chars incl @
Phone # = max chars
Company = max chars
Reason = max chars
User ID = max chars
Password = max chars
Confirm pwd = max chars
7.1.12 Submit Registration First Name = max chars Registration request
request… Last Name = max chars should be accepted.
Email = max chars incl @
(Bug#10224) Phone # = max chars
Company = max chars
Additional information for the
admin =Max Chars
User ID = max chars
Password = max chars
Confirm pwd = max chars

7.1.12 Login as Admin and None User is enabled.

enable this user…
7.1.13 Login as the new None User successfully logs in.
user…
7.1.14 Login as Admin and None User is deleted.
delete this user…

Scope: Test various field input on the Registration Request Form.

Scenario 3: Test maximum number of characters accepted for each field.
S# Action Input Value Expected Results Actual P/F Automat
Results ed
7.1.15 Submit Registration request… First Name = 1 char Registration request
Last Name = 1 char should be accepted.
Email = [email protected]
Phone # = 1 char
Company = 1 char
Additional information
for the admin = 1 char
User ID = 1 char
Password = 6 chars
Confirm pwd = 6 chars
7.1.16 Login as Admin and enable None User is enabled.
S# Action Input Value Expected Results Actual P/F Automat
Results ed
this user…
7.1.17 Login as the new user… None User successfully logs in.
7.1.18 Login as Admin and delete this None User is deleted.
user…

Scope: Test various field input on the Registration Request Form.

Test Notes & Preconditions: Field input should limit the user to some maximum value. If not, an error
should be produced.
Scenario 4: Test exceeding maximum field input lengths on the new user registration form.
S# Action Input Value Expected Results Actual P/F Automate
Results d
7.1.19 Submit Registration First Name = max + 1 Field input is limited to max
request… chars, allowable chars.
Other fields valid
7.1.20 Submit Registration Last Name = max + 1 Field input is limited to max
request… chars, allowable chars.
Other fields valid
7.1.21 Submit Registration Email = max + 1 Field input is limited to max
request… chars, allowable chars.
Other fields valid
7.1.22 Submit Registration Phone number = max Field input is limited to max
request… + 1 chars, allowable chars.
Other fields valid
7.1.23 Submit Registration Company = max + 1 Field input is limited to max
request… chars, allowable chars.
Other fields valid
7.1.24 Submit Registration Additional information Field input is limited to max
request… for the admin = max + allowable chars.
1 chars,
Other fields valid
7.1.25 Submit Registration User ID = max + 1 Field input is limited to max
request… chars, allowable chars.
Other fields valid
7.1.26 Submit Registration Password = max + 1 Field input is limited to max
request… chars, allowable chars.
Other fields valid
7.1.27 Submit Registration Confirm Password = Field input is limited to max
request… max + 1 chars allowable chars.
Other fields valid

Scope: Test various field input on the Registration Request Form.

Scenario 5: Test special characters on the new user registration form. This test is for all fields except
Email and User ID, which are addressed separately.
S# Action Input Value Expected Actual P/F Automate
Results Results d
7.1.28 Submit Registration Enter all special chars in Registration request
request… each field, i.e. `~! @#$ should be accepted.
%^&*()-=_+[]{}\|;’”<>/?
Except for Email and User
ID, which should be some
valid entry for this test.
7.1.29 Submit Registration Enter pound char in each Registration request Bug
request… field, i.e. should be accepted. #123456
Asd##ads32%^&*( 7
Except for Email and User
S# Action Input Value Expected Actual P/F Automate
Results Results d
ID, which should be some
valid entry for this test.
7.1.30 Login as Admin and enable None User is enabled.
this user…
7.1.31 Login as the new user… None User successfully logs
in.
7.1.32 Login as Admin and delete None User is deleted.
this user…

Scope: Test various field input on the Registration Request Form.

Scenario 6: Test Email field input.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.1.33 Submit Registration Email = a Appropriate error
request… should be displayed
saying the email is
invalid.
7.1.34 Submit Registration Email = a.b Appropriate error
request… should be displayed
saying the email is
invalid.
7.1.35 Submit Registration Email = a@b Appropriate error
request… should be displayed
saying the email is
invalid.
7.1.36 Submit Registration Email = [email protected] Email address should
request… be accepted.
7.1.37 Submit Registration Email = [email protected] Appropriate error
request… should be displayed
saying the email is
invalid.
7.1.38 Submit Registration Email = a @b.com Email address should
request… be accepted.
7.1.39 Submit Registration Email = [email protected] Appropriate error
request… should be displayed
saying the email is
invalid.
7.1.40 Submit Registration Email = [email protected] Appropriate error
request… should be displayed
saying the email is
invalid.
7.1.41 Submit Registration Email = a [email protected] Email address should
request… be accepted.
7.1.42 Submit Registration Email = a b @c.com Email address should
request… be accepted.
7.1.43 Submit Registration Email = Appropriate error
request… a@[email protected] should be displayed
saying the email is
invalid.
7.1.44 Submit Registration Email = a`~!@#$ Appropriate error
request… %^&*()-=_+[] should be displayed
{}\|;’:”,.<>/? saying the email is
invalid.
7.1.45 Submit Registration Email = a`##~!$ Appropriate error
request… (Bug #6855) %^&*()-=_+[] should be displayed
{}\|;’:”,.<>/[email protected] saying the email is
invalid.
7.1.46 Submit Registration Email = a`~!#$ Appropriate error
request… %^&*()-=_+[] should be displayed
{}\|;’:”,.<>/[email protected] saying the email is
invalid.
Scope: Test various field input on the Registration Request Form.
Test Notes & Preconditions: The User ID can only contain numbers and letters.
Scenario 7: Test User ID field input.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.1.47 Submit Registration User ID = all letters Input should be
request… accepted.
7.1.48 Submit Registration User ID = all numbers Input should be
request… accepted.
7.1.49 Submit Registration User ID = alpha-numeric mix Input should be
request… accepted.
7.1.50 Submit Registration User ID = contains a space Input should be
request… char accepted.
7.1.51 Submit Registration User ID = contains a period. Input should be
request… accepted (user id
must be begin with an
alpha-numeric char).
7.1.52 Submit Registration User ID = contains a dash - Input should be
request… accepted (user id
must be begin with an
alpha
7.1.53 Submit Registration User ID = contains a plus Input should be
request… char + accepted (user id
must be begin with an
alpha
7.1.54 Submit Registration User ID = contains a slash Input should be
request… char / accepted (user id
must be begin with an
alpha
7.1.55 Submit Registration User ID = contains a pound Input should be
request… char twice i.e. ## accepted.
7.1.56 Submit Registration User ID = Duplicate of an Appropriate error
request… already registered ID message should be
displayed.
7.1.57 Submit Registration User ID = unique Input should be
request… alphanumeric entry but all accepted.
other fields are duplicate of
a registered user.
7.1.58 Submit Registration Additional information for Registration request
request… (Bug 10224) the admin = Less than 256 should be accepted.
character The requested user
will get an alert mail
from N1bs Admin
7.1.59 Submit Registration Additional information for Registration request
request… (Bug 10224) the admin: 256 character should be accepted.
The requested user
will get an alert mail
from N1bs Admin
7.1.60 Submit Registration Additional information for Registration request
request…(Bug 10224) the admin: = More than 256 should be accepted.
character The requested user
will get an alert mail
from N1bs Admin
7.1.61 Submit Registration Additional information for Registration request
request…(Bug 10224) the admin: = Maximum should be accepted.
characters The requested user
will get an alert mail
from N1bs Admin

Scenario 8: Password field tests are exercised in the TestCase_TPAS.doc test case document.
7.2 Test Item: Admin Login

Scope: Test valid and invalid login attempts to the Administration page.
Action: User submits Login form.
Test Notes and Preconditions: Open the admin login page.
Verification Steps: Verify the user has been entered in to the admin page after given the correct details.
Scenario 1: Test User ID field input.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.2.1 Admin User submits User Name=Invalid It should display an
Login form error message saying
(Bug#10455) Password=Invalid “The User ID or
Password you entered
is invalid. Please try
again”
7.2.2 Click on ‘try again’ SRC admin login page
hyper link (Bug # should be displayed
10455)
7.2.3 Admin User submits User Name=valid It should display an
Login form error message saying
(Bug#10455) Password=Invalid “The User ID or
Password you entered
is invalid. Please try
again”
7.2.4 Click on ‘try again’ SRC admin login page
hyper link (Bug # should be displayed
10455)
7.2.5 Admin User submits User Name=Invalid It should display an
Login form Password=valid error message saying
(Bug#10455) “The User ID or
Password you entered
is invalid. Please try
again”
7.2.6 Click on ‘try again’ SRC admin login page
hyper link (Bug # should be displayed
10455)
7.2.7 Admin User submits Password = Valid Admin user should be
Login forrm User Name=valid logged in successfully
in the admin page

7.3 Test Item: Create User.

Scope: Test various field input on the Create User Form.

Action: Submit Create User form.
Test Notes and Preconditions: Open the User registration form from the users tab.
Verification Steps: Verify the user has been registered with the given details.
Scenario 1: Test various field input on the Create User Form
S# Action Input Value Expected Actual P/F Automated
Results Results
7.3.1 Submit Create User First Name = blank, Error message should
form… Other fields valid be displayed for invalid
First Name.
7.3.2 Submit Create User Last Name = blank, Error message should
form… Other fields valid be displayed for invalid
S# Action Input Value Expected Actual P/F Automated
Results Results
Last Name.
7.3.3 Submit Create User Email = blank, Error message should
form… Other fields valid be displayed for invalid
Email.
7.3.4 Submit Create User User ID = blank, Error message should
form… Other fields valid be displayed for invalid
User ID.
7.3.5 Submit Create User Password = blank, Error message should
form… Other fields valid be displayed for invalid
Password.
7.3.6 Submit Create User Confirm Password = Error message should
form… blank be displayed for invalid
Other fields valid confirmation password
7.3.7 Submit Create User All fields blank Error message should
form… be displayed.
Submit Create User Client Version = User successfully
form… Standard Client Ceated.
Submit Create User Client Version = User successfully
form… Professional client created.
7.3.8 Creating new user First Name = valid User successfully
(Bug account Last Name = valid created.
8147 Email = valid
and User ID = valid
10475) Password = valid
Confirm pwd = valid
chars
Scope: Test various field input on the Create User Form.
Scenario 2: Test minimum number of characters accepted for each field.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.3.8 Submit Create User First Name = 1 char Create User form
form… Last Name = 1 char should be accepted
Email = a@a and the user is created.
User ID = 1 char
Password = 6 chars
Confirm pwd = 6 chars
7.3.9 Login as the new user… None User successfully logs
in.
7.3.10 Login as Admin and None User is deleted.
delete this user…
Scope: Test various field input on the Create User Form.
Scenario 3: Test maximum number of characters accepted for each field.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.3.11 Submit Create User First Name = max Create User form
form… chars should be
Last Name = max accepted and the
chars user is created.
Email = max chars incl
@
User ID = max chars
Password = max chars
Confirm pwd = max
chars
7.3.12 Login as the new user… None User successfully
logs in.
7.3.13 Login as Admin and None User is deleted.
delete this user…
Scope: Test various field input on the Create User Form.
Test Notes & Preconditions: Field input should limit the user to some maximum value. If not, an error
should be produced
Scenario 4: Test exceeding maximum field input lengths on the create user form.
S# Action Input Value Expected Actual P/F Autom
Results Results ated
7.3.1 Submit Create User First Name = max + 1 chars, Field input is limited
4 form… Other fields valid to max allowable
chars.
7.3.1 Submit Create User Last Name = max + 1 chars, Field input is limited
5 form… Other fields valid to max allowable
chars.
7.3.1 Submit Create User Email = max + 1 chars, Field input is limited
6 form… Other fields valid to max allowable
chars.
7.3.1 Submit Create User User ID = max + 1 chars, Field input is limited
7 form… Other fields valid to max allowable
chars.
7.3.1 Submit Create User Password = max + 1 chars, Field input is limited
8 form… Other fields valid to max allowable
chars.
7.3.1 Submit Create User Confirm Password = max + 1 chars Field input is limited
9 form… Other fields valid to max allowable
chars.

Scope: Test various field input on the Create User Form.

Scenario 5: Test special characters on create user form. This test is for all fields except Email and User
ID, which are addressed separately.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.3.2 Submit Create User Enter all special chars in Create User form
0 form… each field, i.e. `~!@#$ should be accepted
%^&*()-=_+[]{}\|;’:”,.<>/? and the user is
created.
Except for Email and User
ID, which should be some
valid entry for this test.
7.3.2 Submit Create User Enter pound char twice in Create User form Bug#4567
1 form… each field, i.e. `~!@##$ should be accepted
%^&*()-=_+[]{}\|;’:”,.<>/? and the user is
created.
Except for Email and User
ID, which should be some
valid entry for this test.
7.3.2 Login as the new None User successfully
2 user… logs in.
7.3.2 Login as Admin and None User is deleted.
3 delete this user…

Scope: Test various field input on the Create User Form.

Test Notes & Preconditions: Not certain at this time which of these tests will produce errors. The
mechanism for email validation hasn’t been specified or documented to my knowledge. Need to get more
info from the developer and may need to expand this test scenario. When the email address does not
actually exist, the server will write an error to the error_log since it can’t actually send a confirmation
email to that address.
Scenario 6: Test Email field input.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.3.24 Submit Create User Email = a Appropriate error
form… message should be
displayed.
7.3.25 Submit Create User Email = a.b Appropriate error
form… message should be
displayed.
7.3.26 Submit Create User Email = a@b Appropriate error
form… message should be
displayed
7.3.27 Submit Create User Email = [email protected] Address should be
form… accepted.
7.3.28 Submit Create User Email = [email protected] Appropriate error
form… message should be
displayed
7.3.29 Submit Create User Email = a @b.com Appropriate error
form… message should be
displayed. .
7.3.30 Submit Create User Email = [email protected] Appropriate error
form… message should be
displayed. .
7.3.31 Submit Create User Email = [email protected] Address should be
form… accepted.
7.3.32 Submit Create User Email = a [email protected] Appropriate error
form… message should be
displayed
7.3.33 Submit Create User Email = a b @c.com Appropriate error
form… message should be
displayed.
7.3.34 Submit Create User Email = a@[email protected] Appropriate error
form… message should be
displayed
7.3.35 Submit Create User Email = a`~!@#$%^&*()-=_+[] Appropriate error
form… {}\|;’:”,.<>/? message should be
displayed.
7.3.36 Submit Create User Email = a`~ !#$%^&*()-=_+[] Appropriate error
form… {}\| ;’ :”,.<>/ [email protected] message should be
displayed
7.3.37 Submit Create User Email = Address should be Bug#
form… wqe##[email protected] accepted. 789

Scope: Test various field input on the Create User Form.

Test Notes & Preconditions: The User ID can only contain numbers and letters.
Scenario 7: Test User ID field input.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.3.38 Submit Create User User ID = all letters Input should be
form… accepted.
7.3.39 Submit Create User User ID = all numbers Input should be
form… accepted.
7.3.40 Submit Create User User ID = alpha-numeric Input should be
form… mix accepted.
7.3.41 Submit Create User User ID = contains a Input should be
form… space char accepted (user id must
begin with an alpha-
S# Action Input Value Expected Actual P/F Automated
Results Results
numeric char)
7.3.42 Submit Create User User ID = contains a Input should be
form… period. accepted (user id must
begin with an alpha-
numeric char)
7.3.43 Submit Create User User ID = contains a dash Input should be
form… - accepted (user id must
begin with an alpha-
numeric char)
7.3.44 Submit Create User User ID = contains a plus Input should be
form… char + accepted (user id must
begin with an alpha-
numeric char)
7.3.45 Submit Create User User ID = contains a Input should be
form… slash char / accepted (user id must
begin with an alpha-
numeric char)
7.3.46 Submit Create User User ID = Duplicate of an Appropriate error
form… already registered ID message should be
displayed.
7.3.47 Submit Create User User ID = unique alpha- Input should be
form… numeric entry but all other accepted.
fields are duplicate of a
registered user.
7.3.48 1 .Login to secure shell
as admin
2. Add the following line There are x no of users
to registered on this
decuma.local.properties. server, out of a
license_source=@butler maximum of 0.
3. Add users
4. Comment out the line
from
decuma.local.properties
#license_source=@butler
(bug #11084)

7.4 Test Item: Edit User

Scope: Test various field input on the Edit User Form.

Action: Display Edit User form.
Test Notes and Preconditions: Open the user registration request form from users tab from the existing
user list.
Verification Steps: verify the user details have been updated with the given details.
Scenario 1: Test that User ID field is NOT editable on the edit user form.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.1 Display Edit User Attempt to edit User ID User ID field is NOT (userid field is plain
form… field. editable. text, not a text
input)

Scope: Test various field input on the Edit User Form.

Scenario 2: Test for empty password filed in the edit user form.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.2 Display Edit User Verify the password field The password field
form… value. should be empty.

Scope: Test various field input on the Edit User Form.

Scenario 3: Test leaving a required field blank on the edit user form.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.3 Submit Edit User First Name = blank, Error message should
form… Other fields valid be displayed for
invalid First Name.
7.4.4 Submit Edit User Last Name = blank, Error message should
form… Other fields valid be displayed for
invalid Last Name.
7.4.5 Submit Edit User Email = blank, Error message should
form… Other fields valid be displayed for
invalid Email.
7.4.6 Submit Edit User Password = blank, Error message should
form… Other fields valid be displayed for
invalid Password.
7.4.7 Submit Edit User Confirm Password = Error message should
form… blank be displayed for
Other fields valid invalid confirmation
password
7.4.8 Submit Edit User All fields blank Error message should
form… be displayed.

Scope: Test various field input on the Edit User Form.

Scenario 4: Test minimum number of characters accepted for each field.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.9 Submit Edit User First Name = 1 char Edit User form should
form… Last Name = 1 char be accepted and the
Email = a@a user information is
Password = 6 chars updated.
Confirm pwd = 6 chars
7.4.1 Login as the new None User successfully logs
0 user… in.

Scope: Test various field input on the Edit User Form.

Scenario 5: Test maximum number of characters accepted for each field.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.11 Submit Edit User First Name = max Edit User form should be
form… chars accepted and the user
Last Name = max info is updated.
chars
Email = max chars
incl @
Password = max
chars
S# Action Input Value Expected Actual P/F Automated
Results Results
Confirm pwd = max
chars
7.4.12 Login as the new None User successfully logs
user… in.

Scope: Test various field input on the Edit User Form.

Test Notes & Preconditions: Field input should limit the user to some maximum value. If not, an error
should be produced.
Scenario 6: Test exceeding maximum field input lengths on the Edit user form.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.13 Submit Edit User First Name = max + 1 chars, Field input is limited to
form… Other fields valid max allowable chars.
7.4.14 Submit Edit User Last Name = max + 1 chars, Field input is limited to
form… Other fields valid max allowable chars.
7.4.15 Submit Edit User Email = max + 1 chars, Field input is limited to
form… Other fields valid max allowable chars.
7.4.16 Submit Edit User Password = max + 1 chars, Field input is limited to
form… Other fields valid max allowable chars.
7.4.17 Submit Edit User Confirm Password = max + Field input is limited to
form… 1 chars max allowable chars.
Other fields valid

Scope: Test various field input on the Edit User Form.

Scenario 7: Test special characters on Edit user form. This test is for all fields except Email and User ID
which are addressed separately.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.18 Submit Edit User Enter all special chars in Edit User form should
form… each field, i.e. `~!@#$ be accepted and the
%^&*()-=_+[]{}\|;’:”,.<>/? user information is
Except for Email which updated.
should be some valid
entry for this test.
7.4.19 Login as the new None User successfully logs
user… in.
Scope: Test various field input on the Edit User Form.
Test Notes & Preconditions: Not certain at this time which of these tests will produce errors. The
mechanism for email validation hasn’t been specified or documented to my knowledge. Need to get more
info from the developer and may need to expand this test scenario.
Scenario 8: Test Email field input.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.20 Submit Edit User Email = a Appropriate error Allows it. Probably
form… message should be shouldn’t but is
displayed. innocuous
7.4.21 Submit Edit User Email = a.b Appropriate error
form… message should be
displayed.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.4.22 Submit Edit User Email = a@b Appropriate error
form… message should be
displayed.
7.4.23 Submit Edit User Email = [email protected] Address should be
form… accepted.
7.4.24 Submit Edit User Email = [email protected] Appropriate error
form… message should be
displayed saying the
email is invalid.
7.4.25 Submit Edit User Email = a @b.com Appropriate error
form… message should be
displayed saying the
email is invalid
7.4.26 Submit Edit User Email = [email protected] Appropriate error
form… message should be
displayed saying the
email is invalid.
7.4.27 Submit Edit User Email = [email protected] Address should be
form… accepted.
7.4.28 Submit Edit User Email = a [email protected] Appropriate error
form… message should be
displayed saying the
email is invalid
7.4.29 Submit Edit User Email = a b @c.com Appropriate error Says it appears to
form… message should be be invalid
displayed saying the
email is invalid
7.4.30 Submit Edit User Email = a@[email protected] Appropriate error Says it appears to
form… message should be be invalid
displayed saying the
email is invalid
7.4.31 Submit Edit User Email = a`~!@#$ Appropriate error
form… %^&*()-=_+[] message should be
{}\|;’:”,.<>/? displayed saying the
email is invalid.
7.4.32 Submit Edit User Email = a`~ !#$%^&*()- Appropriate error
form… =_+[]{}\| ;’ :”,.<>/ ? message should be
[email protected] displayed saying the
email is invalid
7.4.33 Submit Edit User Email = Address should be Bug#
form… a##[email protected] accepted. 9876

Scope: Test various field input on the Edit User Form.

Scenario 8: Password field tests are exercised in the TestCase_pass.doc test case document.

7.5 Test Item: Basic Delete and Disable

Scope: Test for login credentials of the Disabled user.

Action: Admin disables test user.
Test Notes & Preconditions: An active test user is available for this test and is not currently logged in.
Verification Steps: Verify the user has been disabled or not.
Scenario 1: Test that a disabled user cannot login to Company Access Mobilizer.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.5.1 Admin disables test None. User’s status is
user… changed from ‘Active’
to ‘Disabled’.
7.5.2 Disabled user Valid user id and A message should be Bug#
attempts to login… password displayed that the user 1234567
provided at login has been disabled and 89
is not logged in.

Scope: Test for login credentials of the Deleted user.

Test Notes & Preconditions: An active test user is available for this test and is not currently logged in.
Scenario 2: Test that a deleted user cannot login to Company Access Mobilzer.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.5.3 Admin deletes test None. User is deleted and
user… removed from the
registered list of users.
7,.5.4 Deleted user Original user id and A message should be
attempts to login… password provided displayed that the User
at login ID is invalid.

Scope: Test for login credentials of the Deleted disabled user.

 Test Notes & Preconditions: The user should be a member of a group and the ‘Disabled’ test user
is available for this test.
Setup: The user should be a member of a group for this deletion test
Scenario 3: Test deleting a disabled user.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.5.5 Admin deletes the None. User is deleted and
disabled test user… removed from the
registered list of
users.
7.5.6 Deleted user Original user id A message should be
attempts to login… and password displayed that the
provided at login User ID is invalid.

Scope: Test for login credentials of the Deleted and recreated the same user
Test Notes & Preconditions: The user under test has at least one of each of the following:
 Registered device(s)
 Registered Bookmark(s)
 Registered Email account(s)
 Registered Sent-Mail folder
 Registered Speed message(s)
 Registered Nickname(s)
 Registered PIM account(s)
Scenario 4: Test deleting and recreating a user that has personalized configuration info in the
Company database.
S# Action Input Expected Actual P/F Automated
Value Results Results
7.5.7 Admin deletes the None. User is deleted and
test user… removed from the
registered list of users.
7.5.8 Admin recreates a None. The user is created
user with the same successfully.
user information…
7.5.9 The user logs into None. The user is logged in.
Company… There are no
configuration remnants
left over from the
previously deleted user
with the same ID and
user info.

Scope: Test for login credentials of the Deleted user.

Test Notes & Preconditions: The user under test has just been created and has performed NO
personalized configuration.
Scenario 5: Test deleting and recreating a user that has NO personalized configuration info in
the Company database.
S# Action Input Expected Actual P/F Automated
Value Results Results
7.5.10 Admin deletes the test None. User is deleted and
user… removed from the
registered list of users.

7.6 Test Item: Test user

Scope: Test for test the user Account

Action: Admin test user.
Test Notes & Preconditions: Open the Test link from list all users tab
Verification Steps: Verify the user Configured server Account validation
Scenario 1: Test that a Test link for the particular user

S# Action Input Expected Actual P/F Automated

Value Results Results
7.6.1 Click on Test link for User has not Message should display
the particular user created any “User has no server
server Account account configured”
7.6.2 Click on Test link for User has Valid Message should
the particular user Server Account displays” Test
successful! “
7.6.3 Click on Test link for User has Appropiate error
the particular user invalid Server message should diplay
Account
7.7 Test Item: Admin creates user(s) and assign(s) to group(s) using batch scripts

Scope: administrator would use a script to do batch user(s) to group(s) assignments

Test Notes & Preconditions: A text file contains users and groups mapping data is existed for this test.
Action: Admin runs the batch user creation scripts
Verification Steps: Verify that the users are created and assigns to the groups as we specified.
Scenario 1: Admin creates user(s) and assign(s) to group(s) using batch scripts
S# Action Input Value Expected Actual Results P/F Auto
Results mated
7.7.1 Run the batch script and pass the File path=invalid Error message
file name as an argument… Others=valid data should be displayed
7.7.2 Run the batch script and pass the File format=wrong Error message
file name as an argument… Others=valid data should be displayed
7.7.3 Run the batch script and pass the File path=valid Error message
file name as an argument… User=already existed should be displayed
Others=valid data in log file for the user
7.7.4 Run the batch script and pass the File path=valid Error message
file name as an argument… User=valid should be displayed
Group=invalid in log file for the user
Others=valid data
7.7.5 Run the batch script and pass the File path=valid Users are created
file name as an argument… User=valid and assigned to the
Group=valid groups we specified
Others=valid data in the text file

7.8 Test Item: Delete and Disable users logged into Company.

Scope: Test for Admin disables use for Desktop Browser.

Action: Admin disables user account of desktop.
Test Notes & Preconditions: For each step below, the user state must be reset to ‘Active’ and the user
must be logged in and display the portion of the UI as indicated.
Verification Steps: Verify the user account has been disabled or not.
Scenario 1: Test the affects of disabling a user that is actively using Company with a desktop
browser.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.8.1 UI Location: Email Tab Click Home link Login page should be
Admin disables user… displayed since user
has been deactivated.
7. 8.2 UI Location: Email Tab Click Login page should be
Admin disables user… displayed since user
has been deactivated.

7.8.3 UI Location: Email Tab Click Help Tab Login page should be
Admin disables user… displayed since user
has been deactivated.
7. 8.4 UI Location: Email Tab Click Logout Login page should be
Admin disables user… displayed since user
has been deactivated.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.28.5 UI Location: Email Tab / Click Speed Login page should be
Access Account(s) Messages link displayed since user
Admin disables user… has been deactivated.
7.28.6 UI Location: Email Tab / Click Compose link Login page should be
Access Account(s) displayed since user
Admin disables user… has been deactivated.
7.28.7 UI Location: Email Tab / Click Notifications link Login page should be
Access Account(s) displayed since user
Admin disables user… has been deactivated.
7.28.8 UI Location: Email Tab / Click Configure link The ‘Configure” link
Access Account(s) should be removed
Admin disables user… since the user is
disabled
7.28.9 UI Location: Email Tab / Click an email Login page should be
Access Account(s) account link displayed since user
Admin disables user… has been deactivated.
7.28.10 UI Location: Email Tab / Click Access Login page should be
Access Account(s) Account(s) link displayed since user
Admin disables user… has been deactivated.
7.28.11 UI Location: Email Tab / Click Add Speed Login page should be
Speed Messages Message link displayed since user
Admin disables user… has been deactivated.
7.28.12 UI Location: Email Tab / Click edit speed Login page should be
Speed Messages message link displayed since user
Admin disables user… has been deactivated.
7.28.13 UI Location: Email Tab / Click delete speed Login page should be
Speed Messages message link displayed since user
Admin disables user… has been deactivated.
7.28.14 UI Location: Edit Speed Click Update button Login page should be
Message page displayed since user
displayed. Admin has been deleted.
deletes user…
7.28.15 UI Location: Email Tab / Click Send button Login page should be
Compose displayed since user
Admin disables user… has been deactivated.
7.28.16 UI Location: Email Tab / Click Update button Login page should be
Notifications displayed since user
Admin disables user… has been deactivated.
7.28.17 UI Location: Email Tab / Click an email Login page should be
Configure account link displayed since user
Admin disables user… has been deactivated.
7.28.18 UI Location: Configure Click Update button Login page should be
email account displayed since user
Admin disables user… has been deactivated.
7.28.19 UI Location: Email Click a message to Login page should be
Account opened open displayed since user
Admin disables user… has been deactivated.
7.28.20 UI Location: Email Click Reload Login page should be
Account opened displayed since user
Admin disables user… has been deactivated.
7.28.21 UI Location: Email Click Older messages Login page should be
Account opened displayed since user
Admin disables user… has been deactivated.
7.28.22 UI Location: Email Click Close Mailbox Login page should be
Account opened displayed since user
Admin disables user… has been deactivated.
7.28.23 UI Location: Email Click Connection Info Login page should be
Account opened displayed since user
Admin disables user… has been deactivated.
7.28.24 UI Location: Email Click Attachments Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
7.28.25 UI Location: Email Click Mailbox Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.28.26 UI Location: Email Click Full View Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
7.28.27 UI Location: Email Click Reply Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
7.28.28 UI Location: Email Click Reply to all Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
7.28.29 UI Location: Email Click Forward Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
7.28.30 UI Location: Email Click Delete Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
7.28.31 UI Location: Email Click Connection Info Login page should be
Message opened displayed since user
Admin disables user… has been deactivated.
7.28.32 UI Location: Email Click an attachment Login page should be
Attachment list opened displayed since user
Admin disables user… has been deactivated.
7.28.33 UI Location: Web Tab Click Email Tab Login page should be
Admin disables user… displayed since user
has been deactivated.
7.28.34 UI Location: Web Tab / Click Go button Login page should be
Browse displayed since user
Admin disables user… has been deactivated.
7.28.35 UI Location: Web Tab / Click Bookmarks link Login page should be
Browse displayed since user
Admin disables user… has been deactivated.
7.28.36 UI Location: Web Tab / Click History link Login page should be
Browse displayed since user
Admin disables user… has been deactivated.
7.28.37 UI Location: Web Tab / Click Settings link Login page should be
Browse displayed since user
Admin disables user… has been deactivated.
7.28.38 UI Location: Web Tab / Click Browse link Login page should be
Browse displayed since user
Admin disables user… has been deactivated.
7.28.39 UI Location: Web Tab / Click Add Bookmark Login page should be
Bookmarks link displayed since user
Admin disables user… has been deactivated.
7.28.40 UI Location: Web Tab / Click Clear Login page should be
Bookmarks Bookmarks link displayed since user
Admin disables user… has been deactivated.
7.28.41 UI Location: Web Tab / Click Original link Page should be
Bookmarks loaded
Admin disables user…
7.28.42 UI Location: Web Tab / Click via Company Login page should be
Bookmarks link displayed since user
Admin disables user… has been deactivated.
7.28.43 UI Location: Web Tab / Click Edit Bookmark Login page should be
Bookmarks link displayed since user
Admin disables user… has been deactivated.
7.28.44 UI Location: Web Tab / Click Delete Login page should be
Bookmarks Bookmark link displayed since user
Admin disables user… has been deactivated.
7.28.45 UI Location: Edit Click Update button Login page should be
Bookmark page displayed since user
displayed has been deactivated.
Admin disables user…
7.28.46 UI Location: Web Tab / Click Clear History Login page should be
History link displayed since user
Admin disables user… has been deactivated.
7.28.47 UI Location: Web Tab / Click Original link Page should be
S# Action Input Value Expected Actual P/F Automated
Results Results
History loaded
Admin disables user…
7.28.48 UI Location: Web Tab / Click via Company Login page should be
History link displayed since user
Admin disables user… has been deactivated.
7.28.49 UI Location: Web Tab / Click Clear Cookies Login page should be (Settings is now
Caches button displayed since user called ‘caches’)
Admin disables user… has been deactivated.
7.28.50 UI Location: Web Tab / Click View Cookies Login page should be (Settings is now
Caches button displayed since user called ‘caches’)
Admin disables user… has been deactivated.
7.28.51 UI Location: Web Tab / Click Clear Auto- Login page should be (Settings is now
Caches completions button displayed since user called ‘caches’)
Admin disables user… has been deactivated.
7.28.52 UI Location: Web Tab / Click View Auto- Login page should be (Settings is now
Caches completions button displayed since user called ‘caches’)
Admin disables user… has been deactivated.
7.28.53 UI Location: Web Page Click Next Part Login page should be
opened displayed since user
Admin disables user… has been deactivated.
7.28.54 UI Location: Web Page Click Previous Part Login page should be
opened displayed since user
Admin disables user… has been deactivated.
7.28.55 UI Location: Web Page Click Top Login page should be
opened displayed since user
Admin disables user… has been deactivated.
7.28.56 UI Location: Web Page Click Reload Login page should be
opened displayed since user
Admin disables user… has been deactivated.
7.28.57 UI Location: Web Page Click Full View Login page should be
opened displayed since user
Admin disables user… has been deactivated.
7.28.58 UI Location: Web Page Click Mark Login page should be
opened displayed since user
Admin disables user… has been deactivated.
7.28.59 UI Location: Web Page Click Connection Info Login page should be
opened displayed since user
Admin disables user… has been deactivated.
7.28.60 UI Location: My Click Devices link Login page should be
Accounts Tab displayed since user
Admin disables user… has been deactivated.
7.28.61 UI Location: My Click Password link Login page should be
Accounts Tab displayed since user
Admin disables user… has been deactivated.
7.28.62 UI Location: My Click Update button Login page should be
Accounts Tab / Devices displayed since user
Admin disables user… has been deactivated.
7.28.63 UI Location: My Click Show all link Login page should be
Accounts Tab / Devices displayed since user
Admin disables user… has been deactivated.
7.28.64 UI Location: My Click Delete device Login page should be
Accounts Tab / Devices link displayed since user
Admin disables user… has been deactivated.
7.28.65 UI Location: My Click Change Login page should be
Accounts Tab / Password button displayed since user
Password has been deactivated.
Admin disables user…
7.28.66 UI Location: Help Tab Click Troubleshooting Login page should be
Admin disables user… link displayed since user
has been deactivated.
7.28.67 UI Location: Help Tab Click About link Login page should be
Admin disables user… displayed since user
has been deactivated.
7.28.68 UI Location: Help Tab Click Introduction link Login page should be
Admin disables user… displayed since user
S# Action Input Value Expected Actual P/F Automated
Results Results
has been deactivated.

Scope: Test for Admin disables user in WAP browser.

Test Notes & Preconditions: For each step below, the user state must be reset to ‘Active’ and the user
must be logged in and display the portion of the UI as indicated.
Scenario 2: Test the affects of disabling a user that is actively using Company with a WAP browser.
S# Action Input Value Expected Actual Results P/F Automated
Results
7.28.69 UI Location: Company Click Email link Login page should
Home be displayed since
Admin disables user… user has been
deactivated.
7.28.70 UI Location: Company Click Bookmarks link Login page should
Home be displayed since
Admin disables user… user has been
deactivated.
7.28.71 UI Location: Company Click Go to web link Login page should
Home be displayed since
Admin disables user… user has been
deactivated.
7.28.72 UI Location: Company Click Preferences link Login page should
Home be displayed since
Admin disables user… user has been
deactivated.
7.28.73 UI Location: Company Click Info link Login page should
Home be displayed since
Admin disables user… user has been
deactivated.
7.28.74 UI Location: Company Click Log out link Login page should Bug
Home be displayed since #5579
Admin disables user… user has been
deactivated.
7.28.75 UI Location: Email Click Email account link Login page should
accounts list be displayed since
Admin disables user… user has been
deactivated.
7.28.76 UI Location: Email Click Reload button Login page should
accounts list be displayed since
Admin disables user… user has been
deactivated.
7.28.77 UI Location: Bookmarks list Click Bookmark link Login page should
Admin disables user… be displayed since
user has been
deactivated.
7.28.78 UI Location: Bookmarks list Click Home button Login page should
Admin disables user… be displayed since
user has been
deactivated.
7.28.79 UI Location: Go to Web Click Visit URL link Login page should
options be displayed since
Admin disables user… user has been
deactivated.
7.28.80 UI Location: Go to Web Click History link Login page should
options be displayed since
Admin disables user… user has been
deactivated.
7.28.81 UI Location: Preferences Click Update Login page should
page be displayed since
Admin disables user… user has been
deactivated.
S# Action Input Value Expected Actual Results P/F Automated
Results
7.28.82 UI Location: Info page Click Help Login page should
Admin disables user… be displayed since
user has been
deactivated.
7.28.83 UI Location: Info page Click Device Info Login page should
Admin disables user… be displayed since
user has been
deactivated.

Scope: Test for Admin deletes user.

Test Notes & Preconditions: For each step below, the user state must be reset to ‘Active’ and the user
must be logged in and display the portion of the UI as indicated.
Scenario 3: Test the affects of deleting a user that is actively using Company with a desktop browser.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.28.84 UI Location: Email Tab Click Web Tab Login page should be
Admin deletes user… displayed since user
has been deleted.
7.28.85 UI Location: Email Tab Click My Account Login page should be
Admin deletes user… Tab displayed since user
has been deleted.
7.28.86 UI Location: Email Tab Click Help Tab Login page should be
Admin deletes user… displayed since user
has been deleted.
7.28.87 UI Location: Email Tab Click Logout Login page should be
Admin deletes user… displayed since user
has been deleted.
7.28.88 UI Location: Email Tab / Click Speed Login page should be
Access Account(s) Messages link displayed since user
Admin deletes user… has been deleted.
7.28.89 UI Location: Email Tab / Click Compose Login page should be
Access Account(s) link displayed since user
Admin deletes user… has been deleted.
7. 28.90 UI Location: Email Tab / Click Notifications Login page should be
Access Account(s) link displayed since user
Admin deletes user… has been deleted.
7. 28.91 UI Location: Email Tab / Click Configure Login page should be
Access Account(s) link displayed since user
Admin deletes user… has been deleted.
7. 28.92 UI Location: Email Tab / Click an email Login page should be
Access Account(s) account link displayed since user
Admin deletes user… has been deleted.
7. 28.93 UI Location: Email Tab / Click Access Login page should be
Access Account(s) Account(s) link displayed since user
Admin deletes user… has been deleted.
7. 28.94 UI Location: Email Account Click a message Login page should be
opened to open displayed since user
Admin deletes user… has been deactivated.
7. 28.95 UI Location: Email Account Click Reload Login page should be
opened displayed since user
Admin deletes user… has been deactivated.
7. 28.96 UI Location: Email Account Click Older Login page should be
opened messages displayed since user
Admin deletes user… has been deactivated.
7. 28.97 UI Location: Email Account Click Close Login page should be
opened Mailbox displayed since user
Admin deletes user… has been deactivated.
7. 28.98 UI Location: Email Account Click Connection Login page should be
opened Info displayed since user
Admin deletes user… has been deactivated.
S# Action Input Value Expected Actual P/F Automated
Results Results
7. 28.99 UI Location: Email Click Attachments Login page should be
Message opened displayed since user
Admin deletes user… has been deactivated.
7. 28.100 UI Location: Email Click Mailbox Login page should be
Message opened displayed since user
Admin deletes user… has been deactivated.
7. 28.101 UI Location: Email Click Full View Login page should be
Message opened displayed since user
Admin deletes user… has been deactivated.
7. 28.102 UI Location: Email Click Reply Login page should be
Message opened displayed since user
Admin deletes user… has been deactivated.
7. 28.103 UI Location: Email Click Reply to all Login page should be
Message opened displayed since user
Admin deletes user… has been deactivated.
7. 28.104 UI Location: Email Click Forward Login page should be
Message opened displayed since user
Admin deletes user… has been deactivated.
7. 28.105 UI Location: Email Click Delete Login page should be
Message opened displayed since user
Admin deletes user… has been deactivated.
7. 28.106 UI Location: Email Click Connection Login page should be
Message opened Info displayed since user
Admin deletes user… has been deactivated.
7. 28.107 UI Location: Email Click an Login page should be
Attachment list opened attachment displayed since user
Admin deletes user… has been deactivated.
7. 28.108 UI Location: Email Tab / Click Add Speed Login page should be
Speed Messages Message link displayed since user
Admin deletes user… has been deleted.
7. 28.109 UI Location: Email Tab / Click edit speed Login page should be
Speed Messages message link displayed since user
Admin deletes user… has been deleted.
7. 28.110 UI Location: Email Tab / Click delete speed Login page should be
Speed Messages message link displayed since user
Admin deletes user… has been deleted.
7. 28.111 UI Location: Edit Speed Click Update Login page should be
Message page displayed. button displayed since user
Admin deletes user… has been deleted.
7. 28.112 UI Location: Email Tab / Click Send button Login page should be
Compose displayed since user
Admin deletes user… has been deleted.
7. 28.113 UI Location: Email Tab / Click Update Login page should be
Notifications button displayed since user
Admin deletes user… has been deleted.
7. 28.114 UI Location: Email Tab / Click an email Login page should be
Configure account link displayed since user
Admin deletes user… has been deleted.
7. 28.115 UI Location: Configure Click Update Login page should be
email account button displayed since user
Admin deletes user… has been deactivated.
7. 28.116 UI Location: Web Tab Click Email Tab Login page should be
Admin deletes user… displayed since user
has been deleted.
7. 28.117 UI Location: Web Tab / Click Go button Login page should be
Browse displayed since user
Admin deletes user… has been deleted.
7. 28.118 UI Location: Web Tab / Click Bookmarks Login page should be
Browse link displayed since user
Admin deletes user… has been deleted.
7. 28.119 UI Location: Web Tab / Click History link Login page should be
Browse displayed since user
Admin deletes user… has been deleted.
7. 28.120 UI Location: Web Tab / Click Settings link Login page should be
Browse displayed since user
S# Action Input Value Expected Actual P/F Automated
Results Results
Admin deletes user… has been deleted.
7. 28.121 UI Location: Web Tab / Click Browse link Login page should be
Browse displayed since user
Admin deletes user… has been deleted.
7. 28.122 UI Location: Web Tab / Click Add Login page should be
Bookmarks Bookmark link displayed since user
Admin deletes user… has been deleted.
7. 28.123 UI Location: Web Tab / Click Clear Login page should be
Bookmarks Bookmarks link displayed since user
Admin deletes user… has been deleted.
7. 28.124 UI Location: Web Tab / Click Original link Login page should be
Bookmarks displayed since user
Admin deletes user… has been deleted.
7. 28.125 UI Location: Web Tab / Click via Login page should be
Bookmarks Company link displayed since user
Admin deletes user… has been deleted.
7. 28.126 UI Location: Web Tab / Click Edit Login page should be
Bookmarks Bookmark link displayed since user
Admin deletes user… has been deleted.
7. 28.127 UI Location: Web Tab / Click Delete Login page should be
Bookmarks Bookmark link displayed since user
Admin deletes user… has been deleted.
7. 28.128 UI Location: Edit Bookmark Click Update Login page should be
page displayed button displayed since user
Admin disables user… has been deactivated.
7. 28.129 UI Location: Web Tab / Click Clear Login page should be
History History link displayed since user
Admin deletes user… has been deleted.
7. 28.130 UI Location: Web Tab / Click Original link Login page should be
History displayed since user
Admin deletes user… has been deleted.
7. 28.131 UI Location: Web Tab / Click via Login page should be
History Company link displayed since user
Admin deletes user… has been deleted.
7. 28.132 UI Location: Web Tab / Click Clear Login page should be
Settings Cookies button displayed since user
Admin deletes user… has been deleted.
7. 28.133 UI Location: Web Tab / Click Clear Auto- Login page should be
Settings completions displayed since user
Admin deletes user… button has been deleted.
7. 28.134 UI Location: Web Page Click Next Part Login page should be
opened displayed since user
Admin deletes user… has been deactivated.
7. 28.135 UI Location: Web Page Click Previous Login page should be
opened Part displayed since user
Admin deletes user… has been deactivated.
7. 28.136 UI Location: Web Page Click Top Login page should be
opened displayed since user
Admin deletes user… has been deactivated.
7. 28.137 UI Location: Web Page Click Reload Login page should be
opened displayed since user
Admin deletes user… has been deactivated.
7. 28.138 UI Location: Web Page Click Full View Login page should be
opened displayed since user
Admin deletes user… has been deactivated.
7. 28.139 UI Location: Web Page Click Mark Login page should be
opened displayed since user
Admin deletes user… has been deactivated.
7. 28.140 UI Location: Web Page Click Connection Login page should be
opened Info displayed since user
Admin deletes user… has been deactivated.
7. 28.141 UI Location: My Accounts Click Devices link Login page should be
Tab displayed since user
Admin deletes user… has been deleted.
7. 28.142 UI Location: My Accounts Click Password Login page should be
S# Action Input Value Expected Actual P/F Automated
Results Results
Tab link displayed since user
Admin deletes user… has been deleted.
7. 28.143 UI Location: My Accounts Click Update Login page should be
Tab / Devices button displayed since user
Admin deletes user… has been deleted.
7. 28.144 UI Location: My Accounts Click Show all link Login page should be
Tab / Devices displayed since user
Admin deletes user… has been deleted.
7. 28.145 UI Location: My Accounts Click Delete Login page should be
Tab / Devices device link displayed since user
Admin deletes user… has been deleted.
7. 28.146 UI Location: My Accounts Click Change Login page should be
Tab / Password Password button displayed since user
Admin deletes user… has been deleted.
7. 28.147 UI Location: Help Tab Click Login page should be
Admin deletes user… Troubleshooting displayed since user
link has been deleted.
7. 28.148 UI Location: Help Tab Click About link Login page should be
Admin deletes user… displayed since user
has been deleted.
7. 28.149 UI Location: Help Tab Click Introduction Login page should be
Admin deletes user… link displayed since user
has been deleted.

Scope: Test for Admin deletes user.

Test Notes & Preconditions: For each step below, the user state must be reset to ‘Active’ and the user
must be logged in and display the portion of the UI as indicated.
Scenario 4: Test the affects of deleting a user that is actively using Company with a WAP browser.
S# Action Input Value Expected Actual P/F Automated
Results Results
7. 28.150 UI Location: Company Click Home tab Login page should be
Home displayed since user
Admin deletes user… has been deleted.
7. 28.151 UI Location: Company Click Server tab Login page should be
Home displayed since user
Admin deletes user… has been deleted.
7. 28.152 UI Location: Company Click Phone tab Login page should be
Home displayed since user
Admin deletes user… has been deleted.
7. 28.153 UI Location: Company Click sync tab Login page should be
Home displayed since user
Admin deletes user… has been deleted.
7. 28.154 UI Location: Company Click password tab Login page should be
Home displayed since user
Admin deletes user… has been deleted.
7. 28.155 UI Location: Company Click Log out link Login page should be
Home displayed since user
Admin deletes user… has been deleted.

7.9 Test Item: Email to All Users

Scope: Test the functionality of admin email.

Action: Send email with input values mentioned below

Test Notes & Preconditions: Make sure admin has valid and existing email id. Click on Email All Users
button in List all users page, in order to compose a mail.
Verification Steps: Verify that the messages are successfully sent and opened correctly.

Scenario 1: Test with blank components of email

Scope: Test various input values for subject and body.

S# Action Input Value Expected Actual Results P/F

Results
7.29.1 Send a message with Subject = Blank Message is sent
specified input values. Message = Blank successfully.

7.29.2 Open the message Subject = Blank Message is opened

received from admin from Message = Blank successfully.
the active user account
7.29.3 Send a message with Subject = Non blank Message is sent
specified input values. Message = Blank successfully.
7.29.4 Open the message Subject = Non blank Message is opened
received from admin from Message = Blank successfully.
the active user account
7.29.5 Send a message with Subject = Blank Message is sent
specified input values. Message = Non Blank successfully.
7.29.6 Open the message Subject = Blank Message is opened
received from admin from Message = Non Blank successfully.
the active user account
7.29.7 Send a message with Subject = Non Blank Message is sent
specified input values. Message = Non Blank successfully.
7.29.8 Open the message Subject = Non Blank Message is opened
received from admin from Message = Non Blank successfully.
the active user account

Scenario 2: Some string length and special character tests

Scope: Test short and long strings and special characters in various email components.

S# Action Input Value Expected Actual Results P/F

Results

7.29.9 Send the message of Subject =1 char Message is sent

specified char length for Body = 1char successfully
subject and body.
7.29.1 Open the message Subject =1 char Message is opened
0 received from admin from Body = 1char successfully.
the active user account
7.29.1 Send the message of Subject = Maximum Message is sent
1 specified char length for allowed length or simply successfully.
subject and body. very long.
Body = Maximum allowed
length or simply very long.

7.29.1 Open the message Subject = Maximum Message is opened

2 received from admin from allowed length or simply successfully.
the active user account very long.
Body = Maximum allowed
length or simply very long.

7.29.1 Send the message of Subject =Contains all Message is sent

3 specified char length for special character. successfully.
subject and body. Body = Contains all special
characters.
7.29.1 Open the message Subject = Contains all Message is opened
S# Action Input Value Expected Actual Results P/F
Results

4 received from admin from special character successfully.

the active user account Body = Contains all special
characters
7.29.1 Send the message of Subject =Contains only Message is sent
5 specified char length for ”##”. successfully.
subject and body. Body = Contains only “##”.
7.29.1 Open the message Subject =Contains only Message is opened
6 received from admin from ”##”. successfully.
the active user account Body = Contains only “##”.

Scenario 5: Basic Send and Receive

Scope: Test sending mail to all users

Verification Steps: Verify that the message is sent only to active users.

S# Action Input Value Expected Actual P/F

Results Results
7.29.35 Admin sends an email No active user is present. Message is only sent to
to all users with valid admin, since admin is in
values in subject and Bcc by default.
body.
7.29.36 Check for new Messages are opened
messages and open successfully
those messages in
Admin’s ‘Reply to’ email
account.
7.29.37 Admin sends an email Active and Inactive users are Message is only sent to
to all users with valid present. admin and all the active
values in subject and users. Inactive users
body. should not receive this
message.
7.29.38 Login and check the No Messages were
inactive user’s primary received from admin,
email account for new since the user was
messages, after disabled.
enabling the inactive
user by admin.
7.29.39 Admin sends an email Some of the active users do Message is sent to active
to all users with valid not have primary email users email addresses
values in subject and accounts. that were used for SRC
body. account creation.
7.29.40 Check for new The active user does not Message is received
messages received have primary email account. from admin successfully.
from admin from users
email accounts that
were used for SRC
account creation.
7.29.41 Admin sends an email Active and Inactive users are Message is sent to
to all users with valid present. admin and all the active
values in subject and users. And the header of
body. the received message
should correctly display
the admin’s mail
address.
7.29.42 Admin composes and No connection between SRC The error page should be
sends a message with and SMTP server. displayed with the “Try
valid values in subject again” and “Cancel”
and body. buttons.
 S# Action Input Value Expected Actual P/F
Results Results
7.29.43 Admin clicks cancel The main “Users” page
button of the error page. should be displayed. No
mail is sent.

7.29.44 Check for new No mails from admin

messages in Admin’s were received since the
reply to email account. email sending was
cancelled.
7.29.45 Admin clicks on the “Try Connection between SRC Email will be sent to the
again” button of the and SMTP is fine. active users. The
error page. success screen should
be displayed with the
message “Mail sent to all
enabled users”.
7.29.46 Check for new Message are opened
messages and open successfully
those mails in Admin’s
reply to email account.

Scenario 6: Administrator changes “reply to” address

Scope: Test for changing administrator’s reply to address.

S# Action Input Value Expected Actual P/F

Results Results
7.29.47 Admin runs the reconfig Save changes and restart The new ‘Reply to’ email
script from command SRC address is used when
line and change the admin sends an email
reply to address. message to active users.
7.29.48 Admin sends an email Message is sent
to all users with valid successfully with new
input ‘Reply-to’ email address
7.29.49 Login to SRC as an The email address in the
active User. Open the ‘To’ header should be
email received from the new ‘Reply-to’ email
admin and click on address.
‘reply to’ link.
7.29.50 Admin runs the reconfig Abort the process before The old ‘Reply to’ email
script from command saving. address is used when
line and change the admin sends an email
reply to address. message to active users.
7.29.51 Admin sends an email Message is sent
to all users with valid successfully with the old
input ‘Reply-to’ email address
7.29.52 Login to SRC as an The email address in the
active User. Open the ‘To’ header should be
email received from the old ‘Reply-to’ email
admin and click on address.
‘reply to’ link.

7.10 Test Item: Logout

Scope: Test that no operations can be performed after Logout.

Action: Admin Logs out, chooses the browser’s <Back> option, clicks any command function.
Test Notes & Preconditions: Admin user is logged into the administration page and has performed some
admin functions.
Verification Steps: Verify the Admin is accessing the options of Company even if Admin selects logout
option.
Scenario 1: Test using the browser’s <Back> option after logout.
S# Action Input Expected Actual P/F Automated
Value Results Results
7.30.1 Admin Logs out, chooses the Message should be
browser’s <Back> option, displayed that session
clicks any command function… is invalid or expired
and provides a link to
log back in.
7. 30.2 Click login link and log back Admin is successfully
in… logged back in.

7.11 Test Item: Multiple browser window usage

Scope: Test simultaneous and conflicting operations from multiple browser windows.
Action: Test simultaneous and conflicting operations from multiple browser windows.
Test Notes & Preconditions: Admin is logged in from two separate browser windows.
Verification Steps: Verify the status of the 2 users depends on the operations performed on them.
Scenario 1: Test simultaneous and conflicting operations from multiple browser windows.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.31.1 Enable 2 different registered Both users are
users at the same time. enabled successfully.
7.31.2 Enable the same registered The user is enabled.
user in both browser windows at No error results from
the same time. the conflict.
7.31.3 Disable 2 different users at the Both users are
same time. disabled successfully.
7. 31.4 Disable the same user in both The user is disabled.
browser windows at the same No error results from
time. the conflict.
7. 31.5 Create 2 different users at the Both users are
same time. created successfully.
7. 31.6 Create the same user in both The create request
browser windows at the same that is submitted first
time. creates the user. The
second request will
give an error that the
user already exists.
7. 31.7 Edit and update 2 different Info for both users is
users at the same time. updated successfully.
7. 31.8 Edit and update the same user The user info is
in both browser windows at the updated. No error
same time. results from the
conflict.
7. 31.9 Delete 2 different users at the Both users are
same time. deleted successfully.
7. 31.10 Delete the same user in both The delete request
browser windows at the same that is submitted first
time. deletes the user. The
second request will
give an error that the
user does not exist.
7. 31.11 Delete a user in one window, A message should be F – bug
attempt to edit the user in the displayed that the #5652
S# Action Input Value Expected Actual P/F Automated
Results Results
other window… user does not exist.
7. 31.12 Delete a user in one window, A message should be F – bug
attempt to disable the user in displayed that the #5653
the other window… user does not exist.
7.12 Test Item: Change Admin password

Scope: Test the ability to change the Admin’s password.

Action: User submits Change Password form from the password tab.
Test Notes & Preconditions: Admin is logged into the system.
Verification Steps: Verify the Admin password to enter in to the admin page with the new password.
Scenario 1: Test changing the Admin’s password.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.32.1 User submits Old Password = Blank Error message should
Change Password New Password = Blank be displayed because
form… Confirm Password = original password is
Blank invalid.
7. 32.2 User submits Old Password = Invalid Error message should
Change Password New Password = any be displayed because
form… Confirm Password = any original password is
invalid.
7. 32.3 User submits Old Password = Valid Error message should
Change Password New Password = Blank be displayed because
form… Confirm Password = password cannot be
Blank blank.
7. 32.4 User submits Old Password = Valid Error message should
Change Password New Password = any be displayed because
form… Confirm Password = confirmation password
Does NOT match must match the newly
types password.
7. 32.5 User submits Old Password = Valid Message should be
Change Password New Password = Any displayed stating that
form… Confirm Password = the password has been
Matches changed.
7. 32.6 Logout and attempt Password = OLD Admin cannot login
to login with OLD password with old password.
password Appropriate error
message should be
displayed saying that
password is invalid.
7. 32.7 Attempt to login Password = valid new Admin is logged in
with new password. password successfully.
7. 32.8 User submits Old Password = Valid Message should be
Change Password New Password = All displayed stating that
form… special chars the password has been
Confirm Password = changed.
Matches
7. 32.9 Logout and attempt Password = OLD User cannot login with
to login with OLD password old password.
password Appropriate error
message should be
displayed saying that
password is invalid.
7. 32.10 Attempt to login Password = valid new User is logged in
with new password. password successfully.
7. 32.11 User submits Old Password = all Message should be
Change Password special chars displayed stating that
form… New Password = the password has been
S# Action Input Value Expected Actual P/F Automated
Results Results
Maximum characters that changed.
input field permits
Confirm Password =
Maximum characters that
input field permits
7. 32.12 Logout and attempt Password = OLD User cannot login with
to login with OLD password old password.
password Appropriate error
message should be
displayed saying that
password is invalid.
7. 32.13 Attempt to login Password = valid new User is logged in
with new password. password successfully.

7.13 Test Item: Sending log files to Company Support.

Scope: Test sending log files to Company support or to specified email address
Action: Send log files to Company support or other Email ID with specified size, logs of specified date
range and with given comments.
Test Notes: This option available only in desktop browsers and only in administrator site. This ID can be
modified by the admin through desktop. The duration of the error logs in the log file, the maximum size of
the log files, selection of log files can also be configured before sending logs.
Verification Steps: The default values are always be set automatically when the page is revisited.
Verification Steps: Verify sending system logs as per the configuration set up by the admin. Specified
interval, specified log files registers the new start time and roll time.
Scenario 1: Test sending logs for different configuration.

S# Action Input Value Expected Result Actual P/F Autom

Result ated
7.43.1 Click on ‘System logs’ tab N1 should display the System logs
page, which has a link of ‘Sending
logs’ at the top of the page.
7.43.2 Click on ‘Sending logs’ N1 should display the ‘sending logs’
link page with log file names, email input
field, maximum size of logs/email,
comments input filed and date fields.
7.43.3 Verify the default By default this should be 2MB only.
maximum no of bytes
7.43.4 Verify the default email By default it should be
address in the recipient [email protected]
email address
7.43.5 Click on ‘Submit’ button Log files= one or all N1 should send the selected files as
Other fields= default per the default values given.
7.43.6 Modify the maximum Log file= any of the N1 should display an error of “Max
number of bytes per available or all log files size per email is not entered. Please
email, and click on Input = NULL enter a size” and should have a link
‘Submit’ button to abort the current process
7.43.7 Modify the maximum Log file= any of the N1 should display an error of “Max
number of bytes per available or all log files size per email should have a valid
email, and click on Input = Zero data” and should have a link to abort
‘Submit’ button the current process
7.43.8 Modify the maximum Log file= any of the N1 should display an error of “Max
number of bytes per available or all log files size per email should have a valid
email, and click on Input = negative value data” and should have a link to abort
‘Submit’ button the current process
7.43.9 Modify the maximum Log file= any of the N1 should allow the max size given
S# Action Input Value Expected Result Actual P/F Autom
Result ated
number of bytes per available or all log files and send the log files
email, and click on Input = positive decimal
‘Submit’ button value
7.43.10 Modify the maximum Log file= any of the N1 should allow the max size given
number of bytes per available or all log files and send the log files
email, and click on Input = any positive
‘Submit’ button value.
7.43.11 Modify the email address Log file = any N1 Should display an error saying
and click on ‘Submit’ Email Address= Empty that “Please enter a valid email
button. address” and should have a link to
abort the current process
7.43.12 Modify the email address Log file = any N1 Should display an error saying
and click on ‘Submit’ Email Address= that “Please enter a valid email
button. syntactically Invalid address” and should have a link to
abort the current process
7.43.13 Modify the email address Log file = any N1 should accept the email id given
and click on ‘Submit’ Email Address= Invalid and should send the logs to the
button. (But Syntactically Valid) same. Later the admin should get an
undelivered mail.
7.43.14 Modify the email address Log file = any N1 should accept the email id given
and click on ‘Submit’ Email Address= Valid and should send the logs to the
button. (But Syntactically Valid) same.
7.43.15 Click on the submit button Comments = Empty N1 should send the selected log files
All other field=Valid to the email address specified.
7.43.16 Click on ‘Submit’ button Log file = None N1 should display an error saying
All other fields = Valid “No log file is selected. Please select
one or more log files to send” and
should have a link to abort the
current process
7.43.17 Click on ‘Submit’ button Log file = One N1 should send the selected log file
All other fields = Valid only to the email specified.
7.43.18 Click on ‘Submit’ button Log file = More than N1 should send the selected log files
One only to the email specified.
All other fields = Valid
7.43.19 Mark the ‘Select all logs’ All other fields = valid N1 should send the selected log files
check box then click on only to the email specified.
‘Submit’ button
7.43.20 Unmark the ‘Date range’ All other fields = Valid The date range fields should be
check box and click on disabled and N1 should send the full
‘Submit’ button log files selected without any date
range filtering.
7.43.21 Mark the ‘Date range’ All other Fields = Valid N1 should send the log files for the
check box and click on selected date range only to the
‘Submit button specified date range.
7.43.22 Select the date range and From= current day N1 should send the log files for the
click on ‘Submit’ button Through= current day current day only to the specified date
All other fields = Valid range.
7.43.23 Select the date range and From and Through date N1 should send the log files for the
click on ‘Submit’ button = same day specified only to the specified
All other fields = Valid date range.
7.43.24 Select the date range and From= later than N1 should display an appropriate
click on ‘Submit’ button through date error stating that the date range
Through= current selected is invalid.
All other fields = Valid
7.43.25 Select the date range and From and Through= N1 should correct the date to the
click on ‘Submit’ button invalid nearest or previous date ranges and
Mm=45, proceed to send the log files.
dd=55,yyyy=2004
All other fields = Valid
7.43.26 Select the date range and From= Valid N1 should send the selected log files
click on ‘Submit’ button Through= Valid later for the specified date range to the
than the ‘From’ date email specified.
All other fields = Valid
7.43.27 Click on ‘Submit’ button All fields = Valid data N1 should start the process of
sending logs by displaying a
S# Action Input Value Expected Result Actual P/F Autom
Result ated
message contains the options to
abort and continue waiting. And it
should auto refresh every 10 sec.
7.43.28 Select ‘continue waiting’ N1 should refresh the screen and
option while N1 continue sending logs.
processing the sending
logs
7.43.29 Select ‘abort’ option while N1 should abort the sending logs
N1 processing the process and should show the
sending logs process completion screen.
7.43.30 Select ‘abort’ option in the N1 should abort sending logs, but it
middle of the process or a might have sent some log files.
bit later
7.43.31 In system logs page click All fields = Valid data N1 should start sending log files to
on ‘Submit button’ the specified email ID.
7.43.32 When the sending logs is N1 should show the progress screen
in progress go to other again and sending logs process still
screens (web, email or be continued.
any other tab) and re-
visits the ‘System
logs’>’Sending logs’
screen
7.43.33 Click on ‘Submit’ button… Max bytes/email = 1MB N1 should show an appropriate error
or other stating that log files selected is more
Selected log file > above than the specified byte size and give
max value set the following options:
1. Abort sending all files
2. Abort sending only the files
that are too large
3. Send files anyway
7.43.34 Select ‘Abort sending all N1 should abort sending log files and
files’ option and click on should display process completion
‘Submit’ button… screen.
7.43.35 Select ‘Abort sending N1 should abort sending the larger
only the files that are too files as specified and send the other
large’ option and click on log files selected if any and should
‘Submit’ button… display process completion screen.
7.43.36 Select ‘ Send all files N1 sends all the selected log files
anyway and click on and display the process completion
‘Submit’ button… screen.
7.43.37 Verify the process It should display the list of files if any,
completion screen which are successfully sent to the
specified email and list of log files if
any, which are failed to send.
7.43.38 If any errors occurs while N1 should show the progress page
sending logs… with the list of log files, which are
failed to send.

7.14 Test Item: Refresh after submits

Scope: Test clicking refresh in the desktop browser after submitting a form. The reason for this is at one
point in time, the system would resubmit the same form and cause an error. Refresh should not do this.
Action: Enable a new user registration request. Choose Refresh.
Test Notes & Preconditions: Login to Admin page.
Verification Steps: Verify the display results are not changing even after selecting the refresh option from
the browser’s window.
Scenario 1: Test browser refresh after submitting forms.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.44.1 Enable a new user The page is simply
registration request. Choose redisplayed.
Refresh.
7.44.2 Create a new user. Refresh. The page is simply
redisplayed.
7.44.4 Delete a user. Refresh. The page is simply
redisplayed.

7.15 Test Item: User/Admin Level Privileges

Scope: Test the ability to check admin level privileges

Action: Open ‘List all users’ link from the Users tab.
Test Notes & Preconditions: Admin is logged into the system and click on the Users Tab and click on list
all users.
Verification Steps: Verify that the Admin level privilege options are displayed as mentioned below.
Scenario 1: Test user / admin level privileges.

S# Action Input Value Expected Actual P/F Automated

Results Results
7.45.1 Display configure option Admin should be able to
see the configure
hyperlink in Action Items
for every user.
7.45.2 Display user pages to Click on configure It should take admin to
Admin option hyper link particular user’s
from action items account, just as if the
for particular user. user would have logged
in (Admin will have full
functionality except that
he unable to access the
user’s mail system like
view messages or
compose messages)

7.16 Test Item: Session validation

Scope: Test the admin session validation.

Action: Test the admin session validation for new user creation.
Test Notes & Preconditions: Admin is logged into the system and click on the Users Tab.
Verification Steps: Verify that the session is expired after some time.
Scenario 1: Test the admin session validation.
S# Action Input Value Expected Actual P/F Automated
Results Results
7.46.1 Admin session After creating an Online request, It should display the
validation Login into Admin UI screen select following message
“Enable/Delete” button under “Session invalid or
“Request-Registration Request” expired. Click here to
S# Action Input Value Expected Actual P/F Automated
Results Results
after the session expires. login”
7.46.2 Admin session Do an “upgrade request” from It should display the
validation Mobile Device. following message
Login into Admin UI screen select “Session invalid or
“Enable/Delete” button under expired. Click here to
“Request-Upgrade Request” after login”
the session expires.
7.46.3 Admin session Let the system sit idle until the It should display the
validation user session had expired and following message
then click on "List all Users" link. “Session invalid or
expired. Click here to
login”
7.46.4 Admin session Admin displays create user form, User should not be
validation fill out the form but does not hit added to the List of
“Submit” button until session Users.
timed out. Admin then hits
“submit” button on the form. Error
is displayed that session has
timed out. Admin logs back in.
7.46.5 Admin session Admin displays “Search” user It should display the
validation screen, enter valid data in the following message
search field but does not hit “Session invalid or
“Search” button until session expired. Click here to
timed out. Admin then hits login”
“search” button on the screen.
7.46.6 Admin session Let the system sit idle until the It should display the
validation user session had expired and following message
then click on “List all “Session invalid or
Administrators” expired. Click here to
login”
7.46.7 Admin session Admin opens Edit/Configure/ Selected user should
validation Delete/Test user form, fill out the not be
form but does not hit “Delete” Edited/Configured/del
button until session timed out. eted/tested from the
Admin then hits “Delete” button list of users.
on the form. Error is displayed
that session has timed out.
Admin logs back in.
7.46.8 Admin session Let the system sit idle until the It should display the
validation admin user session had expired following message
and then click on "Clear Cache" “Session invalid or
button under Provision. expired. Click here to
login”
7.46.9 Admin session Admin selects “Client Admin” tab It should display the
validation under which following message
“Status/Sessions/Users/Usage/A “Session invalid or
ccount Admin” should be expired. Click here to
selected after the session had login”
expired.
7.46.10 Admin session Admin selects “Licensing” tab let It should display the
validation the system sit idle after which following message
select “List Users”. “Session invalid or
expired. Click here to
login”
7.46.11 Admin session Admin selects “Logs” tab let the It should display the
validation system sit idle after which select following message
“Submit” button after entering all “Session invalid or
the details. expired. Click here to
login”
7.46.12 Admin session Admin displays Email form, fill out The message should
validation the form but does not hit “Send” not be sent to all the
button until session timed out. active users.
Admin then hits “Send” button on
the form. Error is displayed that
session has timed out. Admin log
S# Action Input Value Expected Actual P/F Automated
Results Results
back in.
7.46.13 Admin session Let the system sit idle until the It should display the
validation admin user session had expired following message
and then click on "Logout" . “Session invalid or
expired. Click here to
login”

Scope: Login failures

Action: Click on Client admin tab and click on users link and click on cient settings

Test Notes & Preconditions: Admin is logged into the system.

Scenario 1: Admin can configure the number of failed login attempts before the client data is
wiped.
S# Action Input Expected Actual P/F Automated
Value Results Results
7.19.13 Admin sets “Login Login failure User is locked out
before data
failures before data wipe” and client and
wipe=4 or10, or
20 Attempts client data are
wiped from the
device.
7.19.13 Admin sets “Login Login failure Client data should
before data
failures before data wipe” never wiped during
wipe=No= limit
invalid login
attempts.