Test Case Example From Net

7/31/2019 Test Case Example From Net

http://slidepdf.com/reader/full/test-case-example-from-net 1/40

Davath.com

TEST CASE ExampleAdministration

Owner:Scope: To validate known functions of the Administration features.

Originator:Status: ActiveDocumentID:

TestCase_Administration.doc

Location:

Change History

Issue Date Handled by CommentsCreated. dd-mmm-yyyy

Davath.com Davath.com



Davath.com

Approved by TypeDateHere TypeNameHere




Davath.com

Table of Contents1. Introduction..................................................................................................................................42. Scope...........................................................................................................................................43. Requirements...............................................................................................................................44. Related Documents.....................................................................................................................45. Traceability Matrix........................................................................................................................4

6. Notes............................................................................................................................................57. Test Cases - Administration........................................................................................................5

7.1 Test Item: Registration Request Form.................................................................................57.2 Test Item: Admin Login........................................................................................................107.3 Test Item: Create User........................................................................................................107.4 Test Item: Edit User ............................................................................................................147.5 Test Item: Basic Delete and Disable...................................................................................177.6 Test Item: Test user.............................................................................................................197.7 Test Item: Admin creates user(s) and assign(s) to group(s) using batch scripts...............207.8 Test Item: Delete and Disable users logged into Company...............................................207.9 Test Item: Email to All Users...............................................................................................297.10 Test Item: Logout...............................................................................................................32

7.11 Test Item: Multiple browser window usage.......................................................................327.12 Test Item: Change Admin password ................................................................................337.13 Test Item: Sending log files to Company Support............................................................347.14 Test Item: Refresh after submits.......................................................................................377.15 Test Item: User/Admin Level Privileges............................................................................377.16 Test Item: Session validation............................................................................................38




Davath.com

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 arenecessary for completion prior to the execution of the test cases listed in thisdocument.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 SoftwareMaintenance Groups.

4. RELATED DOCUMENTS

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

5. TRACEABILITY MATRIX

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

Requirement Validated by:

# Req-1

# Req-2

# Req-3

# Req-4

Test Item xxx

# PRV-1 Test Item xxx

Bug #1234 Test xxx.xxx




# REQ5 Test Items from




Davath.com

# REQ6

# REQ7

# REQ8

# REQ9

# REQ10

xx.xx to xx.xx

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 tothe left according to the results. Note bugzilla number if/when a bug is submittedresulting from a failed test

TestRun #

Tester Name Date Browser &Version

Execution Time Did all the Tests Pass

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 userstab.

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 ActualResults

P/F Autated

7.1.1 Submit Registration request… First Name = blank,Other fields valid

Error message should bedisplayed for invalid First Name.

7.1.2 Submit Registration request… Last Name = blank,Other fields valid

Error message should bedisplayed for invalid Last Name.

7.1.3 Submit Registration request… Email = blank,Other fields valid

Error message should bedisplayed for invalid Email.

7.1.4 Submit Registration request… Phone number = blank,Other fields valid

Error message should bedisplayed for invalid Phone




Davath.com


P/F Autated

number.7.1.5 Submit Registration request… Company = blank,

Other fields validError message should bedisplayed for invalid Last Name.

7.1.7 Submit Registration request… User ID = blank,Other fields valid

Error message should bedisplayed for invalid User ID.

7.1.8 Submit Registration request… Password = blank,Other fields valid

Error message should bedisplayed for invalid Password.

7.1.9 Submit Registration request… Confirm Password = blankOther fields valid

Error message should bedisplayed for invalid confirmationpassword

7.1.10 Submit Registration request… All fields blank Error message should bedisplayed.


Scenario 2: Test minimum number of characters accepted for each field.


P/F Autated

7.1.11 Submit Registrationrequest…

First Name = max charsLast Name = max charsEmail = max chars incl @Phone # = max charsCompany = max charsReason = max charsUser ID = max charsPassword = max charsConfirm pwd = max chars

Registration requestshould be accepted.


(Bug#10224)

First Name = max charsLast Name = max charsEmail = max chars incl @Phone # = max charsCompany = max chars

Additional information for the

admin =Max CharsUser ID = max charsPassword = max charsConfirm pwd = max chars


7.1.12 Login as Admin andenable this user…

None User is enabled.

7.1.13 Login as the newuser…

None User successfully logs in.

7.1.14 Login as Admin anddelete this user…

None User is deleted.


Scenario 3: Test maximum number of characters accepted for each field.


P/F Automed

7.1.15 Submit Registration request… First Name = 1 char Last Name = 1 char Email = [email protected] # = 1 char Company = 1 char Additional information





Davath.com


P/F Automed

for the admin = 1 char User ID = 1 char Password = 6 charsConfirm pwd = 6 chars

7.1.16 Login as Admin and enable this

user…


7.1.17 Login as the new user… None User successfully logs in.7.1.18 Login as Admin and delete this

user…None User is deleted.


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 registrationform.

S# Action Input Value Expected Results Actual

Results

P/F Autom

d


First Name = max + 1chars,Other fields valid

Field input is limited to maxallowable chars.


Last Name = max + 1chars,Other fields valid



Email = max + 1chars,Other fields valid



Phone number = max+ 1 chars,Other fields valid



Company = max + 1chars,

Other fields valid



Additional informationfor the admin = max +1 chars,Other fields valid



User ID = max + 1chars,Other fields valid



Password = max + 1chars,Other fields valid



Confirm Password =max + 1 charsOther 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 ExpectedResults

ActualResults

P/F Automad


Enter all special chars ineach field, i.e. `~! @#$%^&*()-=_+[]{}\|;’”<>/?





Davath.com


ActualResults

P/F Automad

Except for Email and User ID, which should be somevalid entry for this test.


Enter pound char in eachfield, i.e.

Asd##ads32%^&*(Except for Email and User ID, which should be somevalid entry for this test.


Bug#123456

7

7.1.30 Login as Admin and enablethis user…


7.1.31 Login as the new user… None User successfully logs in.7.1.32 Login as Admin and delete

this user…None User is deleted.


Scenario 6: Test Email field input.


ActualResults

P/F Automated


Email = a Appropriate error should be displayedsaying the email isinvalid.


Email = a.b Appropriate error should be displayedsaying the email isinvalid.


Email = a@b Appropriate error should be displayedsaying the email isinvalid.


Email = [email protected] Email address shouldbe accepted.


Email = [email protected] Appropriate error should be displayedsaying the email isinvalid.


Email = a @b.com Email address shouldbe accepted.






Email = a [email protected] Email address shouldbe accepted.

7.1.42 Submit Registrationrequest… Email = a b @c.com Email address shouldbe accepted.7.1.43 Submit Registration

request…Email = a@[email protected] Appropriate error

should be displayedsaying the email isinvalid.


Email = a`~!@#$%^&*()-=_+[]{}\|;’:”,.<>/?

Appropriate error should be displayedsaying the email isinvalid.

7.1.45 Submit Registrationrequest… (Bug #6855)

Email = a`##~!$%^&*()-=_+[]

Appropriate error should be displayed


mailto:a@b

mailto:[email protected]






mailto:a@[email protected]

mailto:a@b









Davath.com


ActualResults

P/F Automated

{}\|;’:”,.<>/[email protected] saying the email isinvalid.


Email = a`~!#$%^&*()-=_+[]{}\|;’:”,.<>/[email protected]

Appropriate error should be displayedsaying the email is

invalid.


Test Notes & Preconditions: The User ID can only contain numbers and letters.

Scenario 7: Test User ID field input.


ActualResults

P/F Automat


User ID = all letters Input should beaccepted.


User ID = all numbers Input should beaccepted.


User ID = alpha-numeric mix Input should beaccepted.


User ID = contains a spacechar

Input should beaccepted.


User ID = contains a period. Input should beaccepted (user idmust be begin with analpha-numeric char).


User ID = contains a dash - Input should beaccepted (user idmust be begin with analpha


User ID = contains a pluschar +

Input should beaccepted (user idmust be begin with analpha


User ID = contains a slashchar /

Input should beaccepted (user idmust be begin with analpha


User ID = contains a poundchar twice i.e. ##



User ID = Duplicate of analready registered ID

Appropriate error message should bedisplayed.


User ID = uniquealphanumeric entry but allother fields are duplicate of aregistered user.


7.1.58 Submit Registrationrequest… (Bug 10224)

Additional information for theadmin = Less than 256character

Registration requestshould be accepted.The requested user

will get an alert mailfrom N1bs Admin

7.1.59 Submit Registrationrequest… (Bug 10224)


admin: 256 character

Registration requestshould be accepted.The requested user will get an alert mailfrom N1bs Admin

7.1.60 Submit Registrationrequest…(Bug 10224)


admin: = More than 256character





Davath.com


ActualResults

P/F Automat

7.1.61 Submit Registrationrequest…(Bug 10224)

Additional information for theadmin: = Maximumcharacters


Scenario 8: Password field tests are exercised in the TestCase_TPAS.doc test casedocument.

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 giventhe correct details.



ActualResults

P/F Automated

7.2.1 Admin User submitsLogin form(Bug#10455)

User Name=Invalid

Password=Invalid

It should display anerror message saying“The User ID or Password you enteredis invalid. Please tryagain”

7.2.2 Click on ‘try again’hyper link (Bug #10455)

SRC admin login pageshould be displayed


User Name=valid

Password=Invalid





User Name=InvalidPassword=valid




7.2.7 Admin User submitsLogin forrm

Password = ValidUser Name=valid

Admin user should belogged in successfullyin the admin page

7.3 Test Item: Create User.

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




Davath.com

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 ExpectedResults ActualResults P/F Automated

7.3.1 Submit Create User form…

First Name = blank,Other fields valid

Error message should bedisplayed for invalid FirstName.


Last Name = blank,Other fields valid

Error message should bedisplayed for invalid LastName.


Email = blank,Other fields valid

Error message should bedisplayed for invalidEmail.


User ID = blank,Other fields valid

Error message should bedisplayed for invalid User ID.


Password = blank,Other fields valid

Error message should bedisplayed for invalidPassword.


Confirm Password =blankOther fields valid

Error message should bedisplayed for invalidconfirmation password


All fields blank Error message should bedisplayed.

Submit Create User form…

Client Version =Standard Client

User successfullyCeated.


Client Version =Professional client

User successfullycreated.

7.3.8(Bug8147and10475)

Creating new user account

First Name = validLast Name = validEmail = validUser ID = validPassword = valid

Confirm pwd = validchars

User successfullycreated.




ActualResults

P/F Automated


First Name = 1 char Last Name = 1 char Email = a@aUser ID = 1 char Password = 6 charsConfirm pwd = 6 chars

Create User formshould be accepted andthe user is created.

7.3.9 Login as the new user… None User successfully logs

in.7.3.10 Login as Admin anddelete this user…





ActualResults

P/F Automated

7.3.11 Submit Create User First Name = max chars Create User form


mailto:a@a

mailto:a@a



Davath.com


ActualResults

P/F Automated

form… Last Name = max charsEmail = max chars incl@User ID = max charsPassword = max chars

Confirm pwd = maxchars

should beaccepted and theuser is created.

7.3.12 Login as the new user… None User successfullylogs in.

7.3.13 Login as Admin anddelete this user…



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.


7.3.14


First Name = max + 1 chars,Other fields valid

Field input is limitedto max allowablechars.

7.3.15


Last Name = max + 1 chars,Other fields valid


7.3.16


Email = max + 1 chars,Other fields valid


7.3.17


User ID = max + 1 chars,Other fields valid


7.3.18


Password = max + 1 chars,Other fields valid


7.3.19


Confirm Password = max + 1 charsOther fields valid



Scenario 5: Test special characters on create user form. This test is for all fieldsexcept Email and User ID, which are addressed separately.


ActualResults

P/F Automated

7.3.2

0

Submit Create User

form…

Enter all special chars in

each field, i.e. `~!@#$%^&*()-=_+[]{}\|;’:”,.<>/?

Except for Email and User ID, which should be somevalid entry for this test.

Create User form

should be acceptedand the user iscreated.

7.3.21


Enter pound char twice ineach field, i.e. `~!@##$%^&*()-=_+[]{}\|;’:”,.<>/?

Except for Email and User ID, which should be some

Create User formshould be acceptedand the user iscreated.

Bug#4567




Davath.com


ActualResults

P/F Automated

valid entry for this test.7.3.22

Login as the newuser…

None User successfullylogs in.

7.3.23

Login as Admin anddelete this user…



Test Notes & Preconditions: Not certain at this time which of these tests will produceerrors. The mechanism for email validation hasn’t been specified or documented tomy knowledge. Need to get more info from the developer and may need to expandthis test scenario. When the email address does not actually exist, the server willwrite an error to the error_log since it can’t actually send a confirmation email to that address.



ActualResults

P/F Automated


Email = a Appropriate error message should bedisplayed.


Email = a.b Appropriate error message should bedisplayed.


Email = a@b Appropriate error message should bedisplayed


Email = [email protected] Address should beaccepted.


Email = [email protected] Appropriate error message should bedisplayed


Email = a @b.com Appropriate error message should bedisplayed. .


Email = [email protected] Appropriate error message should bedisplayed. .




Email = a [email protected] Appropriate error message should bedisplayed


Email = a b @c.com Appropriate error message should bedisplayed.


Email = a@[email protected] Appropriate error message should be

displayed7.3.35 Submit Create User form…

Email = a`~!@#$%^&*()-=_+[]{}\|;’:”,.<>/?



Email = a`~ !#$%^&*()-=_+[]{}\| ;’ :”,.<>/ [email protected]

Appropriate error message should bedisplayed


Email =wqe##[email protected]

Address should beaccepted.

Bug#789


mailto:a@b

mailto:a@b













mailto:wqe#%[email protected]

mailto:a@b







mailto:wqe#%[email protected]



Davath.com


Test Notes & Preconditions: The User ID can only contain numbers and letters.


S# Action Input Value Expected

Results

Actual

Results

P/F Automated


User ID = all letters Input should beaccepted.


User ID = all numbers Input should beaccepted.


User ID = alpha-numericmix



User ID = contains aspace char

Input should beaccepted (user id mustbegin with an alpha-numeric char)


User ID = contains aperiod.


7.3.43 Submit Create User

form…

User ID = contains a dash

-

Input should be

accepted (user id mustbegin with an alpha-numeric char)


User ID = contains a pluschar +



User ID = contains a slashchar /



User ID = Duplicate of analready registered ID



User ID = unique alpha-numeric entry but all other

fields are duplicate of aregistered user.


7.3.48 1 .Login to secure shell asadmin2. Add the following line todecuma.local.properties.license_source=@butler 3. Add users4. Comment out the linefromdecuma.local.properties#license_source=@butler (bug #11084)

There are x no of usersregistered on thisserver, out of amaximum of 0.

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 tabfrom the existing user list.

Verification Steps: verify the user details have been updated with the given details.




Davath.com

Scenario 1: Test that User ID field is NOT editable on the edit user form.


ActualResults

P/F Automated

7.4.1 Display Edit User form…

Attempt to edit User IDfield.

User ID field is NOTeditable.

(userid field is plaintext, not a textinput)


Scenario 2: Test for empty password filed in the edit user form.


ActualResults

P/F Automated

7.4.2 Display Edit User form…

Verify the password fieldvalue.

The password fieldshould be empty.


Scenario 3: Test leaving a required field blank on the edit user form.S# Action Input Value Expected

ResultsActualResults

P/F Automated

7.4.3 Submit Edit User form…

First Name = blank,Other fields valid

Error message shouldbe displayed for invalid First Name.


Last Name = blank,Other fields valid

Error message shouldbe displayed for invalid Last Name.


Email = blank,Other fields valid

Error message shouldbe displayed for invalid Email.


Password = blank,Other fields valid

Error message shouldbe displayed for

invalid Password.7.4.7 Submit Edit User form…

Confirm Password =blankOther fields valid

Error message shouldbe displayed for invalid confirmationpassword


All fields blank Error message shouldbe displayed.




ActualResults

P/F Automated

7.4.9 Submit Edit User form… First Name = 1 char Last Name = 1 char Email = a@aPassword = 6 charsConfirm pwd = 6 chars

Edit User form shouldbe accepted and theuser information isupdated.

7.4.10

Login as the newuser…

None User successfully logsin.



mailto:a@a

mailto:a@a

mailto:a@a



Davath.com



ActualResults

P/F Automated


First Name = maxcharsLast Name = max

charsEmail = max chars incl@Password = maxcharsConfirm pwd = maxchars

Edit User form should beaccepted and the user info is updated.


None User successfully logs in.


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.


ActualResults

P/F Automated


First Name = max + 1 chars,Other fields valid

Field input is limited tomax allowable chars.


Last Name = max + 1 chars,Other fields valid



Email = max + 1 chars,Other fields valid



Password = max + 1 chars,Other fields valid



Confirm Password = max + 1charsOther fields valid



Scenario 7: Test special characters on Edit user form. This test is for all fields except Email and User ID which are addressed separately.


ActualResults

P/F Automated


Enter all special chars ineach field, i.e. `~!@#$%^&*()-=_+[]{}\|;’:”,.<>/?Except for Email whichshould be some valid

entry for this test.

Edit User form shouldbe accepted and theuser information isupdated.


None User successfully logsin.


Test Notes & Preconditions: Not certain at this time which of these tests will produceerrors. The mechanism for email validation hasn’t been specified or documented tomy knowledge. Need to get more info from the developer and may need to expandthis test scenario.




Davath.com



ActualResults

P/F Automated


Email = a Appropriate error message should bedisplayed.

Allows it. Probablyshouldn’t but isinnocuous


Email = a.b Appropriate error message should bedisplayed.


Email = a@b Appropriate error message should bedisplayed.




Email = [email protected] Appropriate error message should bedisplayed saying theemail is invalid.


Email = a @b.com Appropriate error message should bedisplayed saying theemail is invalid


Email = [email protected] Appropriate error message should bedisplayed saying theemail is invalid.




Email = a [email protected] Appropriate error message should bedisplayed saying theemail is invalid


Email = a b @c.com Appropriate error message should bedisplayed saying theemail is invalid

Says it appears tobe invalid


Email = a@[email protected] Appropriate error message should be

displayed saying theemail is invalid

Says it appears tobe invalid


Email = a`~!@#$%^&*()-=_+[]{}\|;’:”,.<>/?

Appropriate error message should bedisplayed saying theemail is invalid.


Email = a`~ !#$%^&*()-=_+[]{}\| ;’ :”,.<>/ [email protected]

Appropriate error message should bedisplayed saying theemail is invalid


Email =a##[email protected]

Address should beaccepted.

Bug#9876


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

7.5 Test Item: Basic Delete and Disable

Scope: Test for login credentials of the Disabled user.

Action: Admin disables test user.


mailto:a@b

mailto:a@b















mailto:a#%[email protected]

mailto:a@b









mailto:a#%[email protected]



Davath.com

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.


7.5.1 Admin disables testuser…

None. User’s status ischanged from ‘Active’to ‘Disabled’.

7.5.2 Disabled user attemptsto login…

Valid user id andpasswordprovided at login

A message should bedisplayed that the user has been disabled andis not logged in.

Bug#123456789

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.


ActualResults

P/F Automated

7.5.3 Admin deletes testuser…

None. User is deleted andremoved from theregistered list of users.

7,.5.4 Deleted user attempts to login…

Original user id andpassword providedat login

A message should bedisplayed that the User 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.


ActualResults

P/F Automated

7.5.5 Admin deletes thedisabled test user…


7.5.6 Deleted user attempts to login…

Original user idand passwordprovided at login

A message should bedisplayed that theUser 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 thefollowing:

• Registered device(s)

• Registered Bookmark(s)




Davath.com

• 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 configurationinfo in the Company database.

S# Action InputValue

ExpectedResults

ActualResults

P/F Automated

7.5.7 Admin deletes thetest user…


7.5.8 Admin recreates auser with the sameuser information…

None. The user is createdsuccessfully.

7.5.9 The user logs into

Company…

None. The user is logged in.

There are noconfiguration remnantsleft over from thepreviously deleted user with the same ID anduser 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 personalizedconfiguration info in the Company database.


ExpectedResults

ActualResults

P/F Automated

7.5.10 Admin deletes the testuser…


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


ExpectedResults

ActualResults

P/F Automated

7.6.1 Click on Test link for theparticular user

User has notcreated any

Message should display“User has no server




Davath.com


ExpectedResults

ActualResults

P/F Automated

server Account account configured” 7.6.2 Click on Test link for the

particular user User has ValidServer Account

Message shoulddisplays” Test successful!

“7.6.3 Click on Test link for the

particular user User has invalidServer Account

Appropiate error message should diplay

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 isexisted 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 wespecified.

Scenario 1: Admin creates user(s) and assign(s) to group(s) using batch scripts


Actual Results P/F Autmat

7.7.1 Run the batch script and pass thefile name as an argument…

File path=invalidOthers=valid data

Error messageshould be displayed


File format=wrongOthers=valid data

Error messageshould be displayed


File path=validUser=already existedOthers=valid data

Error messageshould be displayedin log file for the user

7.7.4 Run the batch script and pass thefile name as an argument… File path=validUser=validGroup=invalidOthers=valid data

Error messageshould be displayedin log file for the user


File path=validUser=validGroup=validOthers=valid data

Users are createdand assigned to thegroups we specifiedin 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 adesktop browser.




Davath.com


ActualResults

P/F Automated

7.8.1 UI Location: Email Tab Admin disables user…

Click Home link Login page should bedisplayed since user has been deactivated.

7. 8.2 UI Location: Email Tab

Admin disables user…

Click Login page should be

displayed since user has been deactivated.

7.8.3 UI Location: Email Tab Admin disables user…

Click Help Tab Login page should bedisplayed since user has been deactivated.

7. 8.4 UI Location: Email Tab Admin disables user…

Click Logout Login page should bedisplayed since user has been deactivated.

7.28.5 UI Location: Email Tab / Access Account(s) Admin disables user…

Click SpeedMessages link

Login page should bedisplayed since user has been deactivated.


Click Compose link Login page should bedisplayed since user has been deactivated.

7.28.7 UI Location: Email Tab /

Access Account(s) Admin disables user…

Click Notifications link Login page should be

displayed since user has been deactivated.7.28.8 UI Location: Email Tab /

Access Account(s) Admin disables user…

Click Configure link The ‘Configure” linkshould be removedsince the user isdisabled


Click an email accountlink



Click Access Account(s) link


7.28.11 UI Location: Email Tab /Speed Messages Admin disables user…

Click Add SpeedMessage link


7.28.12 UI Location: Email Tab /Speed Messages


Click edit speedmessage link

Login page should bedisplayed since user

has been deactivated.7.28.13 UI Location: Email Tab /

Speed Messages Admin disables user…

Click delete speedmessage link


7.28.14 UI Location: Edit SpeedMessage pagedisplayed. Admin deletesuser…

Click Update button Login page should bedisplayed since user has been deleted.

7.28.15 UI Location: Email Tab /Compose Admin disables user…

Click Send button Login page should bedisplayed since user has been deactivated.

7.28.16 UI Location: Email Tab /Notifications Admin disables user…

Click Update button Login page should bedisplayed since user has been deactivated.

7.28.17 UI Location: Email Tab /Configure


Click an email accountlink


has been deactivated.7.28.18 UI Location: Configure

email account Admin disables user…


7.28.19 UI Location: Email Account opened Admin disables user…

Click a message toopen



Click Reload Login page should bedisplayed since user has been deactivated.

7.28.21 UI Location: Email Account opened

Click Older messages Login page should bedisplayed since user




Davath.com


ActualResults

P/F Automated

Admin disables user… has been deactivated.7.28.22 UI Location: Email

Account opened Admin disables user…

Click Close Mailbox Login page should bedisplayed since user has been deactivated.


Click Connection Info Login page should bedisplayed since user has been deactivated.

7.28.24 UI Location: EmailMessage opened Admin disables user…

Click Attachments Login page should bedisplayed since user has been deactivated.


Click Mailbox Login page should bedisplayed since user has been deactivated.


Click Full View Login page should bedisplayed since user has been deactivated.


Click Reply Login page should bedisplayed since user has been deactivated.

7.28.28 UI Location: EmailMessage opened


Click Reply to all Login page should bedisplayed since user

has been deactivated.7.28.29 UI Location: Email

Message opened Admin disables user…

Click Forward Login page should bedisplayed since user has been deactivated.


Click Delete Login page should bedisplayed since user has been deactivated.



7.28.32 UI Location: Email Attachment list opened Admin disables user…

Click an attachment Login page should bedisplayed since user has been deactivated.

7.28.33 UI Location: Web Tab Admin disables user…

Click Email Tab Login page should bedisplayed since user has been deactivated.

7.28.34 UI Location: Web Tab /Browse Admin disables user…

Click Go button Login page should bedisplayed since user has been deactivated.


Click Bookmarks link Login page should bedisplayed since user has been deactivated.


Click History link Login page should bedisplayed since user has been deactivated.


Click Settings link Login page should bedisplayed since user has been deactivated.


Click Browse link Login page should bedisplayed since user has been deactivated.

7.28.39 UI Location: Web Tab /Bookmarks Admin disables user…

Click Add Bookmarklink



Click Clear Bookmarks link



Click Original link Page should beloaded


Click via Company link Login page should bedisplayed since user has been deactivated.

7.28.43 UI Location: Web Tab / Click Edit Bookmark Login page should be




Davath.com


ActualResults

P/F Automated

Bookmarks Admin disables user…

link displayed since user has been deactivated.


Click DeleteBookmark link


7.28.45 UI Location: EditBookmark pagedisplayed Admin disables user…


7.28.46 UI Location: Web Tab /History Admin disables user…

Click Clear History link Login page should bedisplayed since user has been deactivated.


Click Original link Page should beloaded


Click via Company link Login page should bedisplayed since user has been deactivated.

7.28.49 UI Location: Web Tab /Caches Admin disables user…

Click Clear Cookiesbutton


(Settings is nowcalled ‘caches’)


Click View Cookiesbutton




Click Clear Auto-completions button




Click View Auto-completions button



7.28.53 UI Location: Web Pageopened Admin disables user…

Click Next Part Login page should bedisplayed since user has been deactivated.


Click Previous Part Login page should bedisplayed since user has been deactivated.

7.28.55 UI Location: Web Page

opened Admin disables user…

Click Top Login page should be

displayed since user has been deactivated.7.28.56 UI Location: Web Page

opened Admin disables user…





Click Mark Login page should bedisplayed since user has been deactivated.



7.28.60 UI Location: My Accounts Tab Admin disables user…

Click Devices link Login page should bedisplayed since user has been deactivated.

7.28.61 UI Location: My Accounts Tab Admin disables user…

Click Password link Login page should bedisplayed since user has been deactivated.

7.28.62 UI Location: My Accounts Tab / Devices Admin disables user…


7.28.63 UI Location: My Accounts Tab / Devices Admin disables user…

Click Show all link Login page should bedisplayed since user has been deactivated.

7.28.64 UI Location: My Accounts Tab / Devices

Click Delete devicelink





Davath.com


ActualResults

P/F Automated

Admin disables user… has been deactivated.7.28.65 UI Location: My

Accounts Tab /Password Admin disables user…

Click ChangePassword button


7.28.66 UI Location: Help Tab Admin disables user…

Click Troubleshootinglink



Click About link Login page should bedisplayed since user has been deactivated.


Click Introduction link Login page should bedisplayed since user has been deactivated.

Scope: Test for Admin disables user in WAP browser.


Scenario 2: Test the affects of disabling a user that is actively using Company with aWAP browser.


Actual Results P/F Autom

7.28.69 UI Location: CompanyHome Admin disables user…

Click Email link Login page shouldbe displayed sinceuser has beendeactivated.


Click Bookmarks l ink Login page shouldbe displayed sinceuser has beendeactivated.

7.28.71 UI Location: CompanyHome


Click Go to web link Login page shouldbe displayed since

user has beendeactivated.


Click Preferences link Login page shouldbe displayed sinceuser has beendeactivated.


Click Info link Login page shouldbe displayed sinceuser has beendeactivated.


Click Log out link Login page shouldbe displayed sinceuser has beendeactivated.

Bug#5579

7.28.75 UI Location: Email accountslist


Click Email account link Login page shouldbe displayed since

user has beendeactivated.7.28.76 UI Location: Email accounts

list Admin disables user…

Click Reload button Login page shouldbe displayed sinceuser has beendeactivated.

7.28.77 UI Location: Bookmarks list Admin disables user…

Click Bookmark link Login page shouldbe displayed sinceuser has beendeactivated.

7.28.78 UI Location: Bookmarks list Admin disables user…

Click Home button Login page shouldbe displayed since




Davath.com


Actual Results P/F Autom

user has beendeactivated.

7.28.79 UI Location: Go to Weboptions Admin disables user…

Click Visit URL link Login page shouldbe displayed sinceuser has been

deactivated.7.28.80 UI Location: Go to Web

options Admin disables user…

Click History link Login page shouldbe displayed sinceuser has beendeactivated.

7.28.81 UI Location: Preferencespage Admin disables user…

Click Update Login page shouldbe displayed sinceuser has beendeactivated.

7.28.82 UI Location: Info page Admin disables user…

Click Help Login page shouldbe displayed sinceuser has beendeactivated.

7.28.83 UI Location: Info page Admin disables user…

Click Device Info Login page shouldbe displayed sinceuser has been

deactivated.

Scope: Test for Admin deletes user.


Scenario 3: Test the affects of deleting a user that is actively using Company with adesktop browser.


ActualResults

P/F Automated

7.28.84 UI Location: Email Tab

Admin deletes user…

Click Web Tab Login page should be

displayed since user has been deleted.7.28.85 UI Location: Email Tab

Admin deletes user…Click My AccountTab

Login page should bedisplayed since user has been deleted.

7.28.86 UI Location: Email Tab Admin deletes user…

Click Help Tab Login page should bedisplayed since user has been deleted.

7.28.87 UI Location: Email Tab Admin deletes user…

Click Logout Login page should bedisplayed since user has been deleted.

7.28.88 UI Location: Email Tab / Access Account(s) Admin deletes user…

Click SpeedMessages link


7.28.89 UI Location: Email Tab / Access Account(s) Admin deletes user…

Click Composelink


7. 28.90 UI Location: Email Tab / Access Account(s) Admin deletes user…

Click Notificationslink



Click Configurelink



Click an emailaccount link


7. 28.93 UI Location: Email Tab / Access Account(s)

Click Access Account(s) link





Davath.com


ActualResults

P/F Automated

Admin deletes user… has been deleted.7. 28.94 UI Location: Email Account

opened Admin deletes user…

Click a messageto open


7. 28.95 UI Location: Email Accountopened Admin deletes user…



Click Older messages



Click CloseMailbox



Click ConnectionInfo


7. 28.99 UI Location: EmailMessage opened Admin deletes user…

Click Attachments Login page should bedisplayed since user has been deactivated.

7. 28.100 UI Location: EmailMessage opened


Click Mailbox Login page should bedisplayed since user

has been deactivated.7. 28.101 UI Location: Email

Message opened Admin deletes user…



Click Reply Login page should bedisplayed since user has been deactivated.


Click Reply to all Login page should bedisplayed since user has been deactivated.


Click Forward Login page should bedisplayed since user has been deactivated.


Click Delete Login page should bedisplayed since user has been deactivated.


Click ConnectionInfo Login page should bedisplayed since user has been deactivated.

7. 28.107 UI Location: Email Attachment list opened Admin deletes user…

Click anattachment


7. 28.108 UI Location: Email Tab /Speed Messages Admin deletes user…

Click Add SpeedMessage link



Click edit speedmessage link



Click delete speedmessage link


7. 28.111 UI Location: Edit SpeedMessage page displayed. Admin deletes user…

Click Updatebutton


7. 28.112 UI Location: Email Tab /Compose Admin deletes user…

Click Send button Login page should bedisplayed since user has been deleted.

7. 28.113 UI Location: Email Tab /Notifications Admin deletes user…

Click Updatebutton


7. 28.114 UI Location: Email Tab /Configure Admin deletes user…

Click an emailaccount link


7. 28.115 UI Location: Configure Click Update Login page should be




Davath.com


ActualResults

P/F Automated

email account Admin deletes user…

button displayed since user has been deactivated.

7. 28.116 UI Location: Web Tab Admin deletes user…

Click Email Tab Login page should bedisplayed since user has been deleted.

7. 28.117 UI Location: Web Tab /Browse Admin deletes user…

Click Go button Login page should bedisplayed since user has been deleted.


Click Bookmarkslink



Click History link Login page should bedisplayed since user has been deleted.


Click Settings link Login page should bedisplayed since user has been deleted.


Click Browse link Login page should bedisplayed since user has been deleted.

7. 28.122 UI Location: Web Tab /

Bookmarks Admin deletes user…

Click Add

Bookmark link

Login page should be

displayed since user has been deleted.

7. 28.123 UI Location: Web Tab /Bookmarks Admin deletes user…

Click Clear Bookmarks link



Click Original link Login page should bedisplayed since user has been deleted.


Click via Companylink



Click EditBookmark link


7. 28.127 UI Location: Web Tab /Bookmarks


Click DeleteBookmark link


has been deleted.7. 28.128 UI Location: Edit Bookmarkpage displayed Admin disables user…

Click Updatebutton


7. 28.129 UI Location: Web Tab /History Admin deletes user…

Click Clear Historylink



Click Original link Login page should bedisplayed since user has been deleted.


Click via Companylink


7. 28.132 UI Location: Web Tab /Settings Admin deletes user…

Click Clear Cookies button


7. 28.133 UI Location: Web Tab /Settings Admin deletes user…

Click Clear Auto-completionsbutton


7. 28.134 UI Location: Web Pageopened Admin deletes user…

Click Next Part Login page should bedisplayed since user has been deactivated.


Click PreviousPart



Click Top Login page should bedisplayed since user has been deactivated.




Davath.com


ActualResults

P/F Automated



7. 28.138 UI Location: Web Pageopened


Click Full View Login page should bedisplayed since user

has been deactivated.7. 28.139 UI Location: Web Page

opened Admin deletes user…

Click Mark Login page should bedisplayed since user has been deactivated.


Click ConnectionInfo


7. 28.141 UI Location: My AccountsTab Admin deletes user…

Click Devices link Login page should bedisplayed since user has been deleted.

7. 28.142 UI Location: My AccountsTab Admin deletes user…

Click Passwordlink


7. 28.143 UI Location: My AccountsTab / Devices Admin deletes user…

Click Updatebutton



Click Show all link Login page should bedisplayed since user has been deleted.


Click Deletedevice link


7. 28.146 UI Location: My AccountsTab / Password Admin deletes user…

Click ChangePassword button


7. 28.147 UI Location: Help Tab Admin deletes user…

ClickTroubleshootinglink


7. 28.148 UI Location: Help Tab Admin deletes user…

Click About link Login page should bedisplayed since user has been deleted.

7. 28.149 UI Location: Help Tab


Click Introduction

link

Login page should be

displayed since user has been deleted.

Scope: Test for Admin deletes user.


Scenario 4: Test the affects of deleting a user that is actively using Company with aWAP browser.


ActualResults

P/F Automated

7. 28.150 UI Location: CompanyHome Admin deletes user…

Click Home tab Login page should bedisplayed since user has been deleted.


Click Server tab Login page should bedisplayed since user has been deleted.


Click Phone tab Login page should bedisplayed since user has been deleted.


Click sync tab Login page should bedisplayed since user has been deleted.




Davath.com


ActualResults

P/F Automated


Click password tab Login page should bedisplayed since user has been deleted.

7. 28.155 UI Location: CompanyHome


Click Log out link Login page should bedisplayed since 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 onEmail 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.


Actual Results P/F

7.29.1 Send a message withspecified input values.

Subject = BlankMessage = Blank

Message is sentsuccessfully.

7.29.2 Open the messagereceived from admin from

the active user account

Subject = BlankMessage = Blank

Message is openedsuccessfully.


Subject = Non blankMessage = Blank


7.29.4 Open the messagereceived from admin fromthe active user account

Subject = Non blankMessage = Blank



Subject = BlankMessage = Non Blank



Subject = BlankMessage = Non Blank



Subject = Non BlankMessage = Non Blank



Subject = Non BlankMessage = Non Blank


Scenario 2: Some string length and special character tests

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




Davath.com


Actual Results P/F

7.29.9 Send the message of specified char length for subject and body.

Subject =1 char Body = 1char

Message is sentsuccessfully

7.29.10 Open the message received

from admin from the activeuser account

Subject =1 char

Body = 1char

Message is opened

successfully.


Subject = Maximum allowedlength or simply very long.Body = Maximum allowedlength or simply very long.


7.29.12 Open the message receivedfrom admin from the activeuser account

Subject = Maximum allowedlength or simply very long.Body = Maximum allowedlength or simply very long.



Subject =Contains all specialcharacter.Body = Contains all specialcharacters.



Subject = Contains allspecial character Body = Contains all specialcharacters



Subject =Contains only ”##”.Body = Contains only “##”.



Subject =Contains only ”##”.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.


P/F

7.29.35 Admin sends an email toall users with valid valuesin subject and body.

No active user is present. Message is only sent toadmin, since admin is inBcc by default.

7.29.36 Check for new messagesand open thosemessages in Admin’s‘Reply to’ email account.

Messages are openedsuccessfully


Active and Inactive users arepresent.

Message is only sent toadmin and all the activeusers. Inactive usersshould not receive thismessage.

7.29.38 Login and check theinactive user’s primaryemail account for newmessages, after enablingthe inactive user byadmin.

No Messages werereceived from admin,since the user wasdisabled.




Davath.com


P/F


Some of the active users donot have primary emailaccounts.

Message is sent to activeusers email addressesthat were used for SRCaccount creation.

7.29.40 Check for new messages

received from admin fromusers email accounts thatwere used for SRCaccount creation.

The active user does not have

primary email account.

Message is received from

admin successfully.


Active and Inactive users arepresent.

Message is sent to adminand all the active users. And the header of thereceived message shouldcorrectly display theadmin’s mail address.

7.29.42 Admin composes andsends a message withvalid values in subjectand body.

No connection between SRCand SMTP server.

The error page should bedisplayed with the “Tryagain” and “Cancel”buttons.

7.29.43 Admin clicks cancelbutton of the error page.

The main “Users” pageshould be displayed. No

mail is sent.

7.29.44 Check for new messagesin Admin’s reply to emailaccount.

No mails from admin werereceived since the emailsending was cancelled.

7.29.45 Admin clicks on the “Tryagain” button of the error page.

Connection between SRC andSMTP is fine.

Email will be sent to theactive users. The successscreen should bedisplayed with themessage “Mail sent to allenabled users”.

7.29.46 Check for new messagesand open those mails in Admin’s reply to emailaccount.

Message are openedsuccessfully

Scenario 6: Administrator changes “reply to” address

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


P/F

7.29.47 Admin runs the reconfigscript from command lineand change the reply toaddress.

Save changes and restart SRC The new ‘Reply to’ emailaddress is used whenadmin sends an emailmessage to active users.

7.29.48 Admin sends an email toall users with valid input

Message is sentsuccessfully with new

‘Reply-to’ email address7.29.49 Login to SRC as an

active User. Open theemail received fromadmin and click on ‘replyto’ link.

The email address in the‘To’ header should be thenew ‘Reply-to’ emailaddress.

7.29.50 Admin runs the reconfigscript from command lineand change the reply toaddress.

Abort the process beforesaving.

The old ‘Reply to’ emailaddress is used whenadmin sends an emailmessage to active users.

7.29.51 Admin sends an email toall users with valid input

Message is sentsuccessfully with the old




Davath.com


P/F

‘Reply-to’ email address

7.29.52 Login to SRC as anactive User. Open theemail received from

admin and click on ‘replyto’ link.

The email address in the‘To’ header should be theold ‘Reply-to’ email

address.

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 commandfunction.

Test Notes & Preconditions: Admin user is logged into the administration page andhas 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.


ExpectedResults

ActualResults

P/F Automated

7.30.1 Admin Logs out, chooses thebrowser’s <Back> option, clicksany command function…

Message should bedisplayed that sessionis invalid or expiredand provides a link tolog back in.

7. 30.2 Click login link and log backin…

Admin is successfullylogged 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.


ActualResults

P/F Automated

7.31.1 Enable 2 different registeredusers at the same time.

Both users areenabled successfully.

7.31.2 Enable the same registered user in both browser windows at thesame time.

The user is enabled.No error results fromthe conflict.

7.31.3 Disable 2 different users at the Both users are




Davath.com


ActualResults

P/F Automated

same time. disabled successfully.7. 31.4 Disable the same user in both

browser windows at the sametime.

The user is disabled.No error results fromthe conflict.

7. 31.5 Create 2 different users at thesame time.

Both users are createdsuccessfully.

7. 31.6 Create the same user in bothbrowser windows at the sametime.

The create requestthat is submitted firstcreates the user. Thesecond request willgive an error that theuser already exists.

7. 31.7 Edit and update 2 different usersat the same time.

Info for both users isupdated successfully.

7. 31.8 Edit and update the same user inboth browser windows at thesame time.

The user info isupdated. No error results from theconflict.

7. 31.9 Delete 2 different users at thesame time.

Both users are deletedsuccessfully.

7. 31.10 Delete the same user in both

browser windows at the sametime.

The delete request

that is submitted firstdeletes the user. Thesecond request willgive an error that theuser does not exist.

7. 31.11 Delete a user in one window,attempt to edit the user in theother window…

A message should bedisplayed that the user does not exist.

F – bug#5652

7. 31.12 Delete a user in one window,attempt to disable the user in theother window…

A message should bedisplayed that the user does not exist.

F – bug#5653

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 thenew password.

Scenario 1: Test changing the Admin’s password.


ActualResults

P/F Automated

7.32.1 User submitsChange Passwordform…

Old Password = BlankNew Password = BlankConfirm Password =Blank

Error message shouldbe displayed becauseoriginal password isinvalid.

7. 32.2 User submitsChange Passwordform…

Old Password = InvalidNew Password = anyConfirm Password = any

Error message shouldbe displayed becauseoriginal password isinvalid.


Old Password = ValidNew Password = BlankConfirm Password =Blank

Error message shouldbe displayed becausepassword cannot beblank.


Old Password = ValidNew Password = anyConfirm Password =Does NOT match

Error message shouldbe displayed becauseconfirmation passwordmust match the newly




Davath.com


ActualResults

P/F Automated

types password.7. 32.5 User submits

Change Passwordform…

Old Password = ValidNew Password = AnyConfirm Password =Matches

Message should bedisplayed stating thatthe password has beenchanged.

7. 32.6 Logout and attemptto login with OLDpassword

Password = OLDpassword

Admin cannot login withold password. Appropriate error message should bedisplayed saying thatpassword is invalid.

7. 32.7 Attempt to login withnew password.

Password = valid newpassword

Admin is logged insuccessfully.


Old Password = ValidNew Password = Allspecial charsConfirm Password =Matches




User cannot login withold password. Appropriate error

message should bedisplayed saying thatpassword is invalid.



User is logged insuccessfully.


Old Password = allspecial charsNew Password =Maximum characters thatinput field permitsConfirm Password =Maximum characters thatinput field permits




User cannot login withold password. Appropriate error message should bedisplayed saying thatpassword is invalid.



User is logged insuccessfully.

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, logsof 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 beconfigured before sending logs.

Verification Steps: The default values are always be set automatically when the pageis revisited.

Verification Steps: Verify sending system logs as per the configuration set up by theadmin. Specified interval, specified log files registers the new start time and roll time.




Davath.com

Scenario 1: Test sending logs for different configuration.

S# Action Input Value Expected Result ActualResult

P/F Autated

7.43.1 Click on ‘System logs’ tab N1 should display the System logspage, which has a link of ‘Sendinglogs’ at the top of the page.

7.43.2 Click on ‘Sending logs’link

N1 should display the ‘sending logs’page with log file names, email inputfield, maximum size of logs/email,comments input filed and date fields.

7.43.3 Verify the defaul tmaximum no of bytes

By default this should be 2MB only.

7.43.4 Verify the default emailaddress in the recipientemail address

By default it should [email protected]

7.43.5 Click on ‘Submit’ button Log files= one or al lOther fields= default

N1 should send the selected files asper the default values given.

7.43.6 Modify the maximumnumber of bytes per email, and click on‘Submit’ button

Log file= any of theavailable or all log filesInput = NULL

N1 should display an error of “Maxsize per email is not entered. Pleaseenter a size” and should have a link toabort the current process

7.43.7 Modify the maximum

number of bytes per email, and click on‘Submit’ button

Log file= any of the

available or all log filesInput = Zero

N1 should display an error of “Max

size per email should have a validdata” and should have a link to abortthe current process


Log file= any of theavailable or all log filesInput = negative value

N1 should display an error of “Maxsize per email should have a validdata” and should have a link to abortthe current process


Log file= any of theavailable or all log filesInput = positive decimalvalue

N1 should allow the max size givenand send the log files


Log file= any of theavailable or all log filesInput = any positivevalue.

N1 should allow the max size givenand send the log files

7.43.11 Modify the email address

and click on ‘Submit’button.

Log file = any

Email Address= Empty

N1 Should display an error saying that

“Please enter a valid email address”and should have a link to abort thecurrent process

7.43.12 Modify the email addressand click on ‘Submit’button.

Log file = anyEmail Address=syntactically Invalid

N1 Should display an error saying that“Please enter a valid email address”and should have a link to abort thecurrent process


Log file = anyEmail Address= Invalid(But Syntactically Valid)

N1 should accept the email id givenand should send the logs to the same.Later the admin should get anundelivered mail.


Log file = anyEmail Address= Valid(But Syntactically Valid)

N1 should accept the email id givenand should send the logs to the same.

7.43.15 Click on the submit button Comments = Empty All other field=Valid

N1 should send the selected log filesto the email address specified.

7.43.16 Click on ‘Submit’ button Log file = None

All other fields = Valid

N1 should display an error saying “No

log file is selected. Please select oneor more log files to send” and shouldhave a link to abort the currentprocess

7.43.17 Click on ‘Submit’ button Log file = One All other fields = Valid

N1 should send the selected log fileonly to the email specified.

7.43.18 Click on ‘Submit’ button Log file = More than One All other fields = Valid

N1 should send the selected log filesonly to the email specified.

7.43.19 Mark the ‘Select all logs’check box then click on‘Submit’ button

All other fields = valid N1 should send the selected log filesonly to the email specified.






Davath.com


P/F Autated

7.43.20 Unmark the ‘Date range’check box and click on‘Submit’ button

All other fields = Valid The date range fields should bedisabled and N1 should send the fulllog files selected without any daterange filtering.

7.43.21 Mark the ‘Date range’

check box and click on‘Submit button

All other Fields = Valid N1 should send the log files for the

selected date range only to thespecified date range.

7.43.22 Select the date range andclick on ‘Submit’ button

From= current dayThrough= current day All other fields = Valid

N1 should send the log files for thecurrent day only to the specified daterange.


From and Through date= same All other fields = Valid

N1 should send the log files for theday specified only to the specifieddate range.


From= later than throughdateThrough= current All other fields = Valid

N1 should display an appropriateerror stating that the date rangeselected is invalid.


From and Through=invalidMm=45,dd=55,yyyy=2004

All other fields = Valid

N1 should correct the date to thenearest or previous date ranges andproceed to send the log files.


From= ValidThrough= Valid later than the ‘From’ date All other fields = Valid

N1 should send the selected log filesfor the specified date range to theemail specified.

7.43.27 Click on ‘Submit’ button All fields = Valid data N1 should start the process of sending logs by displaying a messagecontains the options to abort andcontinue waiting. And it should autorefresh every 10 sec.

7.43.28 Select ‘continue waiting’option while N1processing the sendinglogs

N1 should refresh the screen andcontinue sending logs.

7.43.29 Select ‘abort’ option whileN1 processing thesending logs

N1 should abort the sending logsprocess and should show the processcompletion screen.

7.43.30 Select ‘abort’ option in themiddle of the process or abit later

N1 should abort sending logs, but itmight have sent some log files.

7.43.31 In system logs page clickon ‘Submit button’

All fields = Valid data N1 should start sending log files to thespecified email ID.

7.43.32 When the sending logs isin progress go to other screens (web, email or any other tab) and re-visits the ‘Systemlogs’>’Sending logs’screen

N1 should show the progress screenagain and sending logs process stillbe continued.

7.43.33 Click on ‘Submit’ button… Max bytes/email = 1MBor other Selected log file > abovemax value set

N1 should show an appropriate error stating that log files selected is morethan the specified byte size and givethe following options:

1. Abort sending all files2. Abort sending only the files

that are too large3. Send files anyway

7.43.34 Select ‘Abort sending allfiles’ option and click on‘Submit’ button…

N1 should abort sending log files andshould display process completionscreen.

7.43.35 Select ‘Abort sendingonly the files that are toolarge’ option and click on‘Submit’ button…

N1 should abort sending the larger files as specified and send the other log files selected if any and shoulddisplay process completion screen.

7.43.36 Select ‘ Send all files N1 sends all the selected log files and




Davath.com


P/F Autated

anyway and click on‘Submit’ button…

display the process completionscreen.

7.43.37 Verify the processcompletion screen

It should display the list of files if any,which are successfully sent to thespecified email and list of log files if

any, which are failed to send.7.43.38 If any errors occurs while

sending logs…N1 should show the progress pagewith the list of log files, which arefailed to send.

7.14 Test Item: Refresh after submits

Scope: Test clicking refresh in the desktop browser after submitting a form. Thereason for this is at one point in time, the system would resubmit the same form andcause 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 therefresh option from the browser’s window.

Scenario 1: Test browser refresh after submitting forms.


ActualResults

P/F Automated

7.44.1 Enable a new user registration request. ChooseRefresh.

The page is simplyredisplayed.

7.44.2 Create a new user. Refresh. The page is simplyredisplayed.

7.44.4 Delete a user. Refresh. The page is simplyredisplayed.

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 UsersTab and click on list all users.

Verification Steps: Verify that the Admin level privilege options are displayed asmentioned below.

Scenario 1: Test user / admin level privileges.


ActualResults

P/F Automated

7.45.1 Display configure option Admin should be able tosee the configurehyperlink in Action Itemsfor every user.

7.45.2 Display user pages to Admin

Click on configureoption hyper link

It should take admin toparticular user’s account,




Davath.com


ActualResults

P/F Automated

from action itemsfor particular user.

just as if the user wouldhave logged in (Adminwill have full functionalityexcept that he unable toaccess the user’s mail

system like viewmessages or composemessages)

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.


ActualResults

P/F Automated

7.46.1 Admin sessionvalidation

After creating an Online request,Login into Admin UI screen select“Enable/Delete” button under “Request-Registration Request”after the session expires.

It should display thefollowing message“Session invalid or expired. Click here tologin”


Do an “upgrade request” fromMobile Device.Login into Admin UI screen select“Enable/Delete” button under “Request-Upgrade Request” after the session expires.



Let the system sit idle until theuser session had expired andthen click on "List all Users" link.



Admin displays create user form,fill out the form but does not hit“Submit” button until sessiontimed out. Admin then hits“submit” button on the form. Error is displayed that session has

timed out. Admin logs back in.

User should not beadded to the List of Users.


Admin displays “Search” user screen, enter valid data in thesearch field but does not hit“Search” button until sessiontimed out. Admin then hits“search” button on the screen.



Let the system sit idle until theuser session had expired andthen click on “List all Administrators”





Davath.com


ActualResults

P/F Automated


Admin opens Edit/Configure/Delete/Test user form, fill out theform but does not hit “Delete”button until session timed out. Admin then hits “Delete” button on

the form. Error is displayed thatsession has timed out. Admin logsback in.

Selected user shouldnot beEdited/Configured/deleted/tested from thelist of users.


Let the system sit idle until theadmin user session had expiredand then click on "Clear Cache"button under Provision.



Admin selects “Client Admin” tabunder which“Status/Sessions/Users/Usage/Account Admin” should be selectedafter the session had expired.



Admin selects “Licensing” tab letthe system sit idle after whichselect “List Users”.

It should display thefollowing message“Session invalid or

expired. Click here tologin”7.46.11 Admin session

validation Admin selects “Logs” tab let thesystem sit idle after which select“Submit” button after entering allthe details.

It should display thefollowing message

“Session invalid or expired. Click here tologin”


Admin displays Email form, fill outthe form but does not hit “Send”button until session timed out. Admin then hits “Send” button onthe form. Error is displayed thatsession has timed out. Admin logback in.

The message shouldnot be sent to all theactive users.


Let the system sit idle until theadmin user session had expired

and then click on "Logout" .

It should display thefollowing message

“Session invalid or expired. Click here tologin”

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 iswiped.


ExpectedResults

ActualResults

P/F Automated

7.19.13 Admin sets “Loginfailures before datawipe”

Login failurebefore datawipe=4 or10, or 20 Attempts

User is lockedout and clientand client dataare wiped fromthe device.




Davath.com


ExpectedResults

ActualResults

P/F Automated

7.19.13 Admin sets “Loginfailures before datawipe”

Login failurebefore datawipe=No= limit

Client datashould neverwiped duringinvalid loginattempts.

Test Case Example From Net

Documents

Transcript of Test Case Example From Net