TEST CASE ExampleAdministration Owner: Scope: Originator: Status: Document ID: Location: Change History Issue Created. Date Handled by dd-mmm-yyyy Comments To validate known functions of the Administration features. Active TestCase_Administration.doc Approved by TypeDateHere TypeNameHere 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...............20 7.8 Test Item: Delete and Disable users logged into Company...............................................20 7.9 Test Item: Email to All Users...............................................................................................29 7.10 Test Item: Logout...............................................................................................................32 7.11 Test Item: Multiple browser window usage.......................................................................32 7.12 Test Item: Change Admin password ................................................................................33 7.13 Test Item: Sending log files to Company Support............................................................34 7.14 Test Item: Refresh after submits.......................................................................................37 7.15 Test Item: User/Admin Level Privileges............................................................................37 7.16 Test Item: Session validation............................................................................................38 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 # Req-1 # Req-2 # Req-3 # Req-4 # PRV-1 Bug #1234 Bug #1235 Bug #1236 Bug #1237 # REQ5 Test Item xxx Test xxx.xxx Test xxx.xxx Test xxx.xxx Test xxx.xxx Test Items from Validated by: Test Item xxx xx to xx.1 Test Item: Registration Request Form. Other fields valid Last Name = blank. Error message should be displayed for invalid Last Name. Note bugzilla number if/when a bug is submitted resulting from a failed test Test Run # Tester Name Date Browser & Version Execution Time Did all the Tests Pass? 7. NOTES Add any generally relevant notes here. Verification Steps: Verify the user has been registered with the given details.1 7. Scenario 1: Test leaving a required field blank on the new user registration S# 7.# REQ6 # REQ7 # REQ8 # REQ9 # REQ10 xx. Check the Pass work Fail box to the left according to the results. Test Notes and Preconditions: Open the user registration request form from the users tab.1. Include the following checklist. Other fields valid Email = blank.1.3 7. TEST CASES .1. Scope: Test various field input on the Registration Request Form.4 Action Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Input Value First Name = blank.Administration This section should provide the set of test cases that are used in the process of testing specific features and functions. Other fields valid Phone number = blank.xx 6.1.2 7. Error message should be displayed for invalid Email. Other fields valid Expected Results Error message should be displayed for invalid First Name. Action: Submit Registration request. Follow the checklist in order and perform each test. Error message should be displayed for invalid Phone Actual Results P/F Autom ated . 7. 12 Submit Registration request… (Bug#10224) Registration request should be accepted.5 7. Error message should be displayed for invalid User ID. Error message should be displayed for invalid Last Name. Scenario 2: Test minimum number of characters accepted for each field. Error message should be displayed for invalid confirmation password Error message should be displayed. 7.13 7. Actual Results P/F Autom ated 7. Scenario 3: Test maximum number of characters accepted for each field.1. Error message should be displayed for invalid Password.7 7.14 Login as Admin and enable this user… Login as the new user… Login as Admin and delete this user… None None None User is enabled.S# Action Input Value Expected Results number.10 Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Company = blank.8 7.1. Scope: Test various field input on the Registration Request Form.1. User is deleted.1. User successfully logs in.1. Other fields valid Confirm Password = blank Other fields valid All fields blank Scope: Test various field input on the Registration Request Form. Other fields valid Password = blank.1.11 Action Submit Registration request… Input Value First Name = max chars Last Name = max chars Email = max chars incl @ Phone # = max chars Company = max chars Reason = max chars User ID = max chars Password = max chars Confirm pwd = max chars First Name = max chars Last Name = max chars Email = max chars incl @ Phone # = max chars Company = max chars Additional information for the admin =Max Chars User ID = max chars Password = max chars Confirm pwd = max chars Expected Results Registration request should be accepted.15 Action Submit Registration request… Input Value First Name = 1 char Last Name = 1 char Email = a@a. Other fields valid User ID = blank. S# 7.12 7. S# 7.1.1.1.1. Actual Results P/F Automat ed . Actual Results P/F Autom ated 7.9 7.com Phone # = 1 char Company = 1 char Additional information Expected Results Registration request should be accepted.1. 1. S# 7.26 7.1. This test is for all fields except Email and User ID.1.24 Action Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Input Value First Name = max + 1 chars.28 Action Submit Registration request… Input Value Enter all special chars in each field. Actual Results P/F Automate d . S# 7. `~! @#$ %^&*()-=_+[]{}\|. Other fields valid Password = max + 1 chars. Field input is limited to max allowable chars. i. Field input is limited to max allowable chars. Scope: Test various field input on the Registration Request Form.1. Other fields valid Company = max + 1 chars. Other fields valid Email = max + 1 chars. an error should be produced.17 7.1. Field input is limited to max allowable chars. User successfully logs in.19 7.1.S# Action Input Value for the admin = 1 char User ID = 1 char Password = 6 chars Confirm pwd = 6 chars None None None Expected Results Actual Results P/F Automat ed 7. Other fields valid User ID = max + 1 chars.25 7.21 7. Other fields valid Last Name = max + 1 chars. Field input is limited to max allowable chars.e.1. Field input is limited to max allowable chars.22 7.’”<>/? Expected Results Registration request should be accepted. Field input is limited to max allowable chars. Other fields valid Additional information for the admin = max + 1 chars. Scenario 5: Test special characters on the new user registration form.16 7. Test Notes & Preconditions: Field input should limit the user to some maximum value. Scenario 4: Test exceeding maximum field input lengths on the new user registration form.1.1. Field input is limited to max allowable chars. Other fields valid Phone number = max + 1 chars.27 Scope: Test various field input on the Registration Request Form.18 Login as Admin and enable this user… Login as the new user… Login as Admin and delete this user… User is enabled.1.23 7. Other fields valid Confirm Password = max + 1 chars Other fields valid Expected Results Field input is limited to max allowable chars.1.1.1. which are addressed separately. User is deleted. Actual Results P/F Automate d 7.20 7. If not. Field input is limited to max allowable chars. Email address should be accepted.1.1. Appropriate error should be displayed saying the email is invalid.1.34 Email = a. Asd##ads32%^&*( Except for Email and User ID.com 7. Enter pound char in each field. Email address should be accepted.36 7.1.43 Email = a
[email protected] 7.1. Appropriate error should be displayed saying the email is invalid.com 7. Appropriate error should be displayed saying the email is invalid.1.35 Email = a@b 7. Scenario 6: Test Email field input. Appropriate error should be displayed saying the email is invalid.1. Bug #123456 7 7.1.39 Email = a @b.29 Submit Registration request… Registration request should be accepted.42 7.com Email =
[email protected]. Email address should be accepted.1.44 Email = a`~!@#$ %^&*()-=_+[] {}\|.1.30 7.38 7.40 Email = a_b@c. which should be some valid entry for this test.33 Action Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… (Bug #6855) Input Value Email = a Expected Results Appropriate error should be displayed saying the email is invalid.45 . None None None Expected Results Actual Results P/F Automate d 7.37 Email = a@b. Scope: Test various field input on the Registration Request Form. which should be some valid entry for this test.com 7.e.c Email = a@b. Appropriate error should be displayed saying the email is invalid.com 7.com Email = a b @c. Appropriate error should be displayed Actual Results P/F Automated 7. Appropriate error should be displayed saying the email is invalid. i.1.S# Action Input Value Except for Email and User ID.1. User successfully logs in. User is deleted.. S# 7. Email address should be accepted.1.com Email = a@b@c.’:”.1.<>/? Email = a`##~!$ %^&*()-=_+[] 7.31 7.1. Appropriate error should be displayed saying the email is invalid.1.41 7.32 Login as Admin and enable this user… Login as the new user… Login as Admin and delete this user… User is enabled. Scenario 7: Test User ID field input.com Expected Results saying the email is invalid.56 7. Input should be accepted.53 User ID = contains a plus char + User ID = contains a slash char / User ID = contains a pound char twice i.1.’:”.1.1.60 Submit Registration request…(Bug 10224) Additional information for the admin: = More than 256 character .1.1. Input should be accepted.S# Action Input Value {}\|.1. Appropriate error message should be displayed.54 7.1.59 Submit Registration request… (Bug 10224) 7. Registration request should be accepted.’:”.48 7.51 Action Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… Submit Registration request… (Bug 10224) Input Value User ID = all letters User ID = all numbers User ID = alpha-numeric mix User ID = contains a space char User ID = contains a period..<>/
[email protected] Submit Registration request… Email = a`~!#$ %^&*()-=_+[] {}\|. S# 7.<>/
[email protected] Scope: Test various field input on the Registration Request Form.1.1. The requested user will get an alert mail from N1bs Admin Registration request should be accepted. ## User ID = Duplicate of an already registered ID User ID = unique alphanumeric entry but all other fields are duplicate of a registered user.55 7. The requested user will get an alert mail from N1bs Admin Registration request should be accepted. Expected Results Input should be accepted. Test Notes & Preconditions: The User ID can only contain numbers and letters. Input should be accepted (user id must be begin with an alpha-numeric char). Appropriate error should be displayed saying the email is invalid.57 7.1.58 7.1. Input should be accepted..47 7.52 User ID = contains a dash - 7.e. The requested user will get an alert mail from N1bs Admin Actual Results P/F Automated 7.1.49 7. Input should be accepted (user id must be begin with an alpha Input should be accepted (user id must be begin with an alpha Input should be accepted (user id must be begin with an alpha Input should be accepted.1.1. Actual Results P/F Automated 7.50 7. Additional information for the admin = Less than 256 character Additional information for the admin: 256 character 7.1. Input should be accepted. 61 Action Submit Registration request…(Bug 10224) Input Value Additional information for the admin: = Maximum characters Expected Results Registration request should be accepted. S# 7.2 Test Item: Admin Login Scope: Test valid and invalid login attempts to the Administration page.doc test case document.S# 7.2.1 Action Admin User submits Login form (Bug#10455) Input Value User Name=Invalid Password=Invalid Expected Results It should display an error message saying “The User ID or Password you entered is invalid. Scenario 1: Test User ID field input.2.2. Please try again” SRC admin login page should be displayed It should display an error message saying “The User ID or Password you entered is invalid. Action: User submits Login form.2. 7.2.6 7. Scope: Test various field input on the Create User Form. Verification Steps: Verify the user has been entered in to the admin page after given the correct details. Please try again” SRC admin login page should be displayed Admin user should be logged in successfully in the admin page Actual Results P/F Automated 7.5 Click on ‘try again’ hyper link (Bug # 10455) Admin User submits Login form (Bug#10455) User Name=Invalid Password=valid 7.7 Click on ‘try again’ hyper link (Bug # 10455) Admin User submits Login forrm Password = Valid User Name=valid 7.4 7. Test Notes and Preconditions: Open the admin login page.2.3 Click on ‘try again’ hyper link (Bug # 10455) Admin User submits Login form (Bug#10455) User Name=valid Password=Invalid 7.2. The requested user will get an alert mail from N1bs Admin Actual Results P/F Automated Scenario 8: Password field tests are exercised in the TestCase_TPAS.1. Please try again” SRC admin login page should be displayed It should display an error message saying “The User ID or Password you entered is invalid.2 7.3 Test Item: Create User. . 5 7. S# 7.6 7. Error message should be displayed for invalid User ID.3.3.4 7.3 7. Verification Steps: Verify the user has been registered with the given details.2 7. Scenario 1: Test various field input on the Create User Form S# Action Input Value Expected Actual Results Results 7. Error message should be displayed for invalid Email. Scenario 3: Test maximum number of characters accepted for each field. S# 7. Actual Results P/F Automated 7.3.3.3.11 Action Submit Create User Input Value First Name = max chars Expected Results Create User form Actual Results P/F Automated . Test Notes and Preconditions: Open the User registration form from the users tab. Other fields valid Password = blank. Error message should be displayed for invalid Password.3. User successfully created.8 Action Submit Create User form… Input Value First Name = 1 char Last Name = 1 char Email = a@a User ID = 1 char Password = 6 chars Confirm pwd = 6 chars None None Expected Results Create User form should be accepted and the user is created.3. Other fields valid Email = blank. User successfully created.3. Error message should be displayed for invalid Last Name.10 Login as the new user… Login as Admin and delete this user… User successfully logs in.3. Other fields valid User ID = blank. Scope: Test various field input on the Create User Form. Other fields valid Last Name = blank. P/F Automated 7.1 7. User is deleted.Action: Submit Create User form.3. Other fields valid Confirm Password = blank Other fields valid All fields blank Client Version = Standard Client Client Version = Professional client First Name = valid Last Name = valid Email = valid User ID = valid Password = valid Confirm pwd = valid chars Error message should be displayed for invalid First Name.9 7.8 (Bug 8147 and 10475) Scope: Test various field input on the Create User Form. User successfully Ceated.3.7 Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Creating new user account First Name = blank.3. Error message should be displayed for invalid confirmation password Error message should be displayed. Scenario 2: Test minimum number of characters accepted for each field. S# 7. Field input is limited to max allowable chars.e. which should be some Expected Results Create User form should be accepted and the user is created. Field input is limited to max allowable chars. i.1 4 7. Other fields valid Confirm Password = max + 1 chars Other fields valid Expected Results Field input is limited to max allowable chars. Bug#4567 . Scope: Test various field input on the Create User Form.3.3.2 0 Action Submit Create User form… Input Value Enter all special chars in each field. which should be some valid entry for this test.. Actual Results P/F Automated 7. S# 7.’:”. If not. Actual Results P/F Autom ated Scope: Test various field input on the Create User Form. Other fields valid User ID = max + 1 chars.2 1 Submit Create User form… Create User form should be accepted and the user is created.3.1 7 7.e.13 Login as the new user… Login as Admin and delete this user… User successfully logs in. Other fields valid Email = max + 1 chars. Actual Results P/F Automated 7.1 6 7. Scenario 5: Test special characters on create user form. Field input is limited to max allowable chars.1 5 7. an error should be produced Scenario 4: Test exceeding maximum field input lengths on the create user form. This test is for all fields except Email and User ID.3.3. User is deleted. `~!@#$ %^&*()-=_+[]{}\|. which are addressed separately.3. Other fields valid Last Name = max + 1 chars.. Enter pound char twice in each field.12 7.1 9 Action Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Input Value First Name = max + 1 chars.<>/? Except for Email and User ID.3.3.<>/? Except for Email and User ID.3. Other fields valid Password = max + 1 chars. Field input is limited to max allowable chars.’:”.3.S# Action form… Input Value Last Name = max chars Email = max chars incl @ User ID = max chars Password = max chars Confirm pwd = max chars None None Expected Results should be accepted and the user is created. Test Notes & Preconditions: Field input should limit the user to some maximum value. Field input is limited to max allowable chars. `~!@##$ %^&*()-=_+[]{}\|.1 8 7. i. com Email = a`~!@#$%^&*()-=_+[] {}\|.3. .com Email = a_b@c. Appropriate error message should be displayed Appropriate error message should be displayed. the server will write an error to the error_log since it can’t actually send a confirmation email to that address.com Email = a b @c.36 7.3.c Email = a@b. The mechanism for email validation hasn’t been specified or documented to my knowledge.3.com Email =
[email protected] 7.29 7.25 7.com Email = a @b.3.com Email = wqe##
[email protected]. Appropriate error message should be displayed. Appropriate error message should be displayed.31 7. . Address should be accepted. Appropriate error message should be displayed Address should be accepted.3.3.3.33 7.’ :”. When the email address does not actually exist. Actual Results P/F Automated Bug# 789 .2 3 Login as the new user… Login as Admin and delete this user… Scope: Test various field input on the Create User Form. Appropriate error message should be displayed Address should be accepted.24 7.28 7.b Email = a@b Email =
[email protected]. Actual Results P/F Automated 7. User is deleted.3.3.com Expected Results Appropriate error message should be displayed.com Email = a@b@c.’:”.3.26 7.32 7.<>/? Email = a`~ !#$%^&*()-=_+[] {}\| .27 7. Appropriate error message should be displayed Appropriate error message should be displayed..37 Action Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Input Value Email = a Email = a.com Email = a
[email protected]# Action Input Value valid entry for this test.30 7. Scenario 6: Test Email field input. Need to get more info from the developer and may need to expand this test scenario. None None Expected Results User successfully logs in.3. Appropriate error message should be displayed Appropriate error message should be displayed. S# 7.34 7..2 2 7. Test Notes & Preconditions: Not certain at this time which of these tests will produce errors.<>/
[email protected]. Test Notes & Preconditions: The User ID can only contain numbers and letters.properties #license_source=@butler (bug #11084) Input Value User ID = all letters User ID = all numbers User ID = alpha-numeric mix User ID = contains a space char User ID = contains a period. license_source=@butler 3. Input should be accepted.46 7. Add the following line to decuma.3.Scope: Test various field input on the Create User Form. Action: Display Edit User form. Input should be accepted. 7. Input should be accepted (user id must begin with an alphanumeric char) Input should be accepted (user id must begin with an alphanumeric char) Input should be accepted (user id must begin with an alphanumeric char) Input should be accepted (user id must begin with an alphanumeric char) Input should be accepted (user id must begin with an alphanumeric char) Appropriate error message should be displayed.3.47 7.local.40 7.3.Login to secure shell as admin 2. S# 7.4 Test Item: Edit User Scope: Test various field input on the Edit User Form.41 Action Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… Submit Create User form… 1 .44 7.local.43 7. Verification Steps: verify the user details have been updated with the given details.38 7.3. Add users 4.3. Scenario 7: Test User ID field input.42 7.3.3.3. . Test Notes and Preconditions: Open the user registration request form from users tab from the existing user list.39 7.3.3. User ID = contains a dash User ID = contains a plus char + User ID = contains a slash char / User ID = Duplicate of an already registered ID User ID = unique alphanumeric entry but all other fields are duplicate of a registered user. Input should be accepted.48 There are x no of users registered on this server. Actual Results P/F Automated 7.45 7.3. Comment out the line from decuma. out of a maximum of 0. Expected Results Input should be accepted.properties. S# 7. Actual Results P/F Automated 7.1 Action Display Edit User form… Input Value Attempt to edit User ID field.6 7.4.8 Scope: Test various field input on the Edit User Form. Actual Results P/F Automated 7. User successfully logs in. Error message should be displayed for invalid confirmation password Error message should be displayed. S# 7.Scenario 1: Test that User ID field is NOT editable on the edit user form. Scenario 3: Test leaving a required field blank on the edit user form. Expected Results The password field should be empty. Error message should be displayed for invalid Password. Other fields valid Password = blank.3 7.4 7. Error message should be displayed for invalid Last Name. Other fields valid Email = blank. Actual Results (userid field is plain text. Actual Results P/F Automated Scope: Test various field input on the Edit User Form.2 Action Display Edit User form… Input Value Verify the password field value.9 Action Submit Edit User form… Input Value First Name = 1 char Last Name = 1 char Email = a@a Password = 6 chars Confirm pwd = 6 chars None Expected Results Edit User form should be accepted and the user information is updated.5 7.4. Other fields valid Last Name = blank.4. S# 7.4.4. Scenario 4: Test minimum number of characters accepted for each field.4. Scenario 2: Test for empty password filed in the edit user form.4. not a text input) P/F Automated Scope: Test various field input on the Edit User Form.7 Action Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Input Value First Name = blank. S# 7. . Expected Results User ID field is NOT editable.1 0 Login as the new user… Scope: Test various field input on the Edit User Form. Other fields valid Confirm Password = blank Other fields valid All fields blank Expected Results Error message should be displayed for invalid First Name. Error message should be displayed for invalid Email.4.4.4. `~!@#$ %^&*()-=_+[]{}\|.4.13 7.19 Login as the new user… Scope: Test various field input on the Edit User Form. Actual Results P/F Automated Scope: Test various field input on the Edit User Form.15 7. Other fields valid Confirm Password = max + 1 chars Other fields valid Expected Results Field input is limited to max allowable chars. an error should be produced.e. i.4.11 Action Submit Edit User form… Input Value First Name = max chars Last Name = max chars Email = max chars incl @ Password = max chars Confirm pwd = max chars None Expected Results Edit User form should be accepted and the user info is updated. Scope: Test various field input on the Edit User Form. Scenario 6: Test exceeding maximum field input lengths on the Edit user form.4.16 7.4. S# 7. Field input is limited to max allowable chars. Scenario 7: Test special characters on Edit user form. Other fields valid Password = max + 1 chars.4. Test Notes & Preconditions: Field input should limit the user to some maximum value. Actual Results P/F Automated 7. User successfully logs in.17 Action Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Input Value First Name = max + 1 chars.4. This test is for all fields except Email and User ID which are addressed separately. If not. S# 7.’:”.<>/? Except for Email which should be some valid entry for this test. Need to get more info from the developer and may need to expand this test scenario. S# 7. Other fields valid Email = max + 1 chars. None Expected Results Edit User form should be accepted and the user information is updated. Field input is limited to max allowable chars.12 Login as the new user… User successfully logs in. Field input is limited to max allowable chars. Actual Results P/F Automated 7. The mechanism for email validation hasn’t been specified or documented to my knowledge.4.4. Other fields valid Last Name = max + 1 chars.Scenario 5: Test maximum number of characters accepted for each field.4. ..14 7.18 Action Submit Edit User form… Input Value Enter all special chars in each field. Field input is limited to max allowable chars. Test Notes & Preconditions: Not certain at this time which of these tests will produce errors. .4.b Email = a@b Email = a@b.’ :”.32 7.29 Email = a b @c.26 Email = a@. Appropriate error message should be displayed saying the email is invalid Appropriate error message should be displayed saying the email is invalid.4. 7. .22 7.25 Email = a @b.com Email = a##
[email protected] 8: Test Email field input.com Expected Results Appropriate error message should be displayed. Appropriate error message should be displayed saying the email is invalid Address should be accepted. Appropriate error message should be displayed. Appropriate error message should be displayed saying the email is invalid Appropriate error message should be displayed saying the email is invalid Appropriate error message should be displayed saying the email is invalid Appropriate error message should be displayed saying the email is invalid.4.com 7.4.doc test case document. Actual Results Allows it.5 Test Item: Basic Delete and Disable Scope: Test for login credentials of the Disabled user.c Email =
[email protected] 7.4.4.21 7.<>/? Email = a`~ !#$%^&*()=_+[]{}\| . Scenario 8: Password field tests are exercised in the TestCase_pass.com 7..4.24 Action Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Submit Edit User form… Input Value Email = a Email = a.20 7. Action: Admin disables test user.4. S# 7.’:”.31 Email = a`~!@#$ %^&*()-=_+[]{}\|.4. Address should be accepted.28 Email =
[email protected] 7.4.4. Probably shouldn’t but is innocuous P/F Automated 7.33 Bug# 9876 Scope: Test various field input on the Edit User Form. Appropriate error message should be displayed.4.com 7. Address should be accepted.4.com Says it appears to be invalid Says it appears to be invalid 7.com Email = a
[email protected] Email = a@b@c. Appropriate error message should be displayed saying the email is invalid.23 7.27 7.<>/ ?
[email protected]. . S# 7. Scenario 1: Test that a disabled user cannot login to Company Access Mobilizer.4 Action Admin deletes test user… Deleted user attempts to login… Input Value None.5. S# 7. Test Notes & Preconditions: An active test user is available for this test and is not currently logged in.3 7.5. Setup: The user should be a member of a group for this deletion test Scenario 3: Test deleting a disabled user. Actual Results P/F Automated Scope: Test for login credentials of the Deleted disabled user.1 7. Verification Steps: Verify the user has been disabled or not. Actual Results P/F Automated Bug# 1234567 89 Scope: Test for login credentials of the Deleted user. Valid user id and password provided at login Expected Results User’s status is changed from ‘Active’ to ‘Disabled’.Test Notes & Preconditions: An active test user is available for this test and is not currently logged in. A message should be displayed that the User ID is invalid. Original user id and password provided at login Expected Results User is deleted and removed from the registered list of users.2 Action Admin disables test user… Disabled user attempts to login… Input Value None.5.6 Action Admin deletes the disabled test user… Deleted user attempts to login… Input Value None.5. Actual Results P/F Automated 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) . A message should be displayed that the user has been disabled and is not logged in. Scenario 2: Test that a deleted user cannot login to Company Access Mobilzer. Original user id and password provided at login Expected Results User is deleted and removed from the registered list of users. A message should be displayed that the User ID is invalid. S# 7. Test Notes & Preconditions: The user should be a member of a group and the ‘Disabled’ test user is available for this test.5.5.5 7. There are no configuration remnants left over from the previously deleted user with the same ID and user info.6. S# 7. None.10 Action Admin deletes the test user… Input Value None.9 Action Admin deletes the test user… Admin recreates a user with the same user information… The user logs into Company… Input Value None. Expected Results User is deleted and removed from the registered list of users. None.6 Test Item: Test user Scope: Test for test the user Account Action: Admin test user. Actual Results P/F Automated 7.5. S# 7. Test Notes & Preconditions: The user under test has just been created and has performed NO personalized configuration.5. Actual Results P/F Automated Scope: Test for login credentials of the Deleted user. The user is created successfully. Scenario 5: Test deleting and recreating a user that has NO personalized configuration info in the Company database.8 7. The user is logged in.7 7.5.5.1 Action Click on Test link for the particular user Input Value User has not created any Expected Results Message should display “User has no server Actual Results P/F Automated . 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# 7.• • • • • 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. Expected Results User is deleted and removed from the registered list of users. Scope: Test for Admin disables use for Desktop Browser.8 Test Item: Delete and Disable users logged into Company. Action: Admin runs the batch user creation scripts Verification Steps: Verify that the users are created and assigns to the groups as we specified. Action: Admin disables user account of desktop. the user state must be reset to ‘Active’ and the user must be logged in and display the portion of the UI as indicated.S# Action Input Value server Account User has Valid Server Account User has invalid Server Account Expected Results account configured” Message should displays” Test successful! “ Appropiate error message should diplay Actual Results P/F Automated 7.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.6. Test Notes & Preconditions: For each step below.2 Click on Test link for the particular user Click on Test link for the particular user 7.3 7.7.1 7.7.6. .3 7.5 7.4 Action Run the batch script and pass the file name as an argument… Run the batch script and pass the file name as an argument… Run the batch script and pass the file name as an argument… Run the batch script and pass the file name as an argument… Run the batch script and pass the file name as an argument… Input Value File path=invalid Others=valid data File format=wrong Others=valid data File path=valid User=already existed Others=valid data File path=valid User=valid Group=invalid Others=valid data File path=valid User=valid Group=valid Others=valid data Expected Results Error message should be displayed Error message should be displayed Error message should be displayed in log file for the user Error message should be displayed in log file for the user Users are created and assigned to the groups we specified in the text file Actual Results P/F Auto mated 7.7.2 7. 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. Scenario 1: Admin creates user(s) and assign(s) to group(s) using batch scripts S# 7.7. 28.28.12 7.28.28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.28. Login page should be displayed since user has been deactivated. 8.9 7.28.15 7.S# 7.4 7.19 7. Login page should be displayed since user has been deactivated.7 7.28. Login page should be displayed since user has been deleted.28. Login page should be displayed since user has been deactivated.2 Click 7.16 7.28.28. Login page should be displayed since user has been deactivated.28.14 Click an email account link Click Access Account(s) link Click Add Speed Message link Click edit speed message link Click delete speed message link Click Update button 7.28. The ‘Configure” link should be removed since the user is disabled Login page should be displayed since user has been deactivated.8.18 7.17 7. Login page should be displayed since user has been deactivated.21 Click Send button Click Update button Click an email account link Click Update button Click a message to open Click Reload Click Older messages .13 7.28. Login page should be displayed since user has been deactivated.20 7. Login page should be displayed since user has been deactivated.8 UI Location: Email Tab Admin disables user… UI Location: Email Tab Admin disables user… UI Location: Email Tab / Access Account(s) Admin disables user… UI Location: Email Tab / Access Account(s) Admin disables user… UI Location: Email Tab / Access Account(s) Admin disables user… UI Location: Email Tab / Access Account(s) Admin disables user… UI Location: Email Tab / Access Account(s) Admin disables user… UI Location: Email Tab / Access Account(s) Admin disables user… UI Location: Email Tab / Speed Messages Admin disables user… UI Location: Email Tab / Speed Messages Admin disables user… UI Location: Email Tab / Speed Messages Admin disables user… UI Location: Edit Speed Message page displayed. Login page should be displayed since user has been deactivated.28. Login page should be displayed since user has been deactivated.5 7.11 7.1 Action UI Location: Email Tab Admin disables user… UI Location: Email Tab Admin disables user… Input Value Click Home link Expected Results Login page should be displayed since user has been deactivated.10 7.28.8. Login page should be displayed since user has been deactivated.3 7. Login page should be displayed since user Actual Results P/F Automated 7. 8. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.28.6 7. Login page should be displayed since user has been deactivated.28. Admin deletes user… UI Location: Email Tab / Compose Admin disables user… UI Location: Email Tab / Notifications Admin disables user… UI Location: Email Tab / Configure Admin disables user… UI Location: Configure email account Admin disables user… UI Location: Email Account opened Admin disables user… UI Location: Email Account opened Admin disables user… UI Location: Email Account opened Click Help Tab Click Logout Click Speed Messages link Click Compose link Click Notifications link Click Configure link 7. 31 7.S# Action Admin disables user… UI Location: Email Account opened Admin disables user… UI Location: Email Account opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Message opened Admin disables user… UI Location: Email Attachment list opened Admin disables user… UI Location: Web Tab Admin disables user… UI Location: Web Tab / Browse Admin disables user… UI Location: Web Tab / Browse Admin disables user… UI Location: Web Tab / Browse Admin disables user… UI Location: Web Tab / Browse Admin disables user… UI Location: Web Tab / Browse Admin disables user… UI Location: Web Tab / Bookmarks Admin disables user… UI Location: Web Tab / Bookmarks Admin disables user… UI Location: Web Tab / Bookmarks Admin disables user… UI Location: Web Tab / Bookmarks Admin disables user… UI Location: Web Tab / Input Value Expected Results has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.37 7. Page should be loaded Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.28.28.28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.28. Login page should be Actual Results P/F Automated 7.28.36 7.28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.24 7. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.39 7.28.28.28.32 7. Login page should be displayed since user has been deactivated.28.28.28.34 7. Login page should be displayed since user has been deactivated.43 Click Close Mailbox Click Connection Info Click Attachments Click Mailbox Click Full View Click Reply Click Reply to all Click Forward Click Delete Click Connection Info Click an attachment Click Email Tab Click Go button Click Bookmarks link Click History link Click Settings link Click Browse link Click Add Bookmark link Click Clear Bookmarks link Click Original link Click via Company link Click Edit Bookmark .26 7. Login page should be displayed since user has been deactivated.27 7.28.25 7.23 7.28.29 7.22 7.42 7. Login page should be displayed since user has been deactivated.28.28.28.35 7.38 7.41 7.30 7. Login page should be displayed since user has been deactivated.33 7.28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.40 7.28 7.28.28.28.28. 52 7.28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.58 7.28.28.47 7. Login page should be displayed since user has been deactivated.28.55 7.50 7.62 7.63 7.28.53 7. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.57 7. Login page should be displayed since user Actual Results P/F Automated 7.44 7. Login page should be displayed since user has been deactivated.28. Login page should be displayed since user has been deactivated.61 7.28. Login page should be displayed since user has been deactivated.28.64 Click Clear History link Click Original link Click via Company link Click Clear Cookies button Click View Cookies button Click Clear Autocompletions button Click View Autocompletions button Click Next Part Click Previous Part Click Top Click Reload Click Full View Click Mark Click Connection Info Click Devices link Click Password link Click Update button Click Show all link Click Delete device link (Settings is now called ‘caches’) (Settings is now called ‘caches’) (Settings is now called ‘caches’) (Settings is now called ‘caches’) .28.28.28. Login page should be displayed since user has been deactivated.28. Login page should be displayed since user has been deactivated.56 7.28.28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.49 7.45 7.59 7.54 7.48 7. Login page should be displayed since user has been deactivated.S# Action Bookmarks Admin disables user… UI Location: Web Tab / Bookmarks Admin disables user… UI Location: Edit Bookmark page displayed Admin disables user… UI Location: Web Tab / History Admin disables user… UI Location: Web Tab / History Admin disables user… UI Location: Web Tab / History Admin disables user… UI Location: Web Tab / Caches Admin disables user… UI Location: Web Tab / Caches Admin disables user… UI Location: Web Tab / Caches Admin disables user… UI Location: Web Tab / Caches Admin disables user… UI Location: Web Page opened Admin disables user… UI Location: Web Page opened Admin disables user… UI Location: Web Page opened Admin disables user… UI Location: Web Page opened Admin disables user… UI Location: Web Page opened Admin disables user… UI Location: Web Page opened Admin disables user… UI Location: Web Page opened Admin disables user… UI Location: My Accounts Tab Admin disables user… UI Location: My Accounts Tab Admin disables user… UI Location: My Accounts Tab / Devices Admin disables user… UI Location: My Accounts Tab / Devices Admin disables user… UI Location: My Accounts Tab / Devices Input Value link Click Delete Bookmark link Click Update button Expected Results displayed since user has been deactivated.28.28. Page should be loaded Login page should be displayed since user has been deactivated.28.51 7. Login page should be displayed since user has been deactivated.46 7.28.60 7.28.28.28. 73 Click Info link 7.28.67 7. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.66 7.28.78 Click Home button .28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.28. Test Notes & Preconditions: For each step below.28.28. Actual Results P/F Automated 7. Login page should be displayed since Actual Results P/F Automated 7.28.76 Click Reload button 7.28.28. Login page should be displayed since user has been deactivated.68 Scope: Test for Admin disables user in WAP browser.S# Action Admin disables user… UI Location: My Accounts Tab / Password Admin disables user… UI Location: Help Tab Admin disables user… UI Location: Help Tab Admin disables user… UI Location: Help Tab Admin disables user… Input Value Expected Results has been deactivated. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deactivated.65 Click Change Password button Click Troubleshooting link Click About link Click Introduction link 7.28. the user state must be reset to ‘Active’ and the user must be logged in and display the portion of the UI as indicated.28.28.70 Click Bookmarks link 7. Login page should be displayed since user has been deactivated.69 Action UI Location: Company Home Admin disables user… UI Location: Company Home Admin disables user… UI Location: Company Home Admin disables user… UI Location: Company Home Admin disables user… UI Location: Company Home Admin disables user… UI Location: Company Home Admin disables user… UI Location: Email accounts list Admin disables user… UI Location: Email accounts list Admin disables user… UI Location: Bookmarks list Admin disables user… UI Location: Bookmarks list Admin disables user… Input Value Click Email link Expected Results Login page should be displayed since user has been deactivated. Scenario 2: Test the affects of disabling a user that is actively using Company with a WAP browser. Login page should be displayed since user has been deactivated.77 Click Bookmark link 7.75 Click Email account link 7.72 Click Preferences link 7. Login page should be displayed since user has been deactivated.74 Click Log out link Bug #5579 7. Login page should be displayed since user has been deactivated. S# 7.71 Click Go to web link 7.28.28. the user state must be reset to ‘Active’ and the user must be logged in and display the portion of the UI as indicated. 28.80 Click History link 7.28.84 7. Login page should be displayed since user has been deleted.83 Click Device Info Scope: Test for Admin deletes user. Login page should be displayed since user has been deactivated.93 Action UI Location: Email Tab Admin deletes user… UI Location: Email Tab Admin deletes user… UI Location: Email Tab Admin deletes user… UI Location: Email Tab Admin deletes user… UI Location: Email Tab / Access Account(s) Admin deletes user… UI Location: Email Tab / Access Account(s) Admin deletes user… UI Location: Email Tab / Access Account(s) Admin deletes user… UI Location: Email Tab / Access Account(s) Admin deletes user… UI Location: Email Tab / Access Account(s) Admin deletes user… UI Location: Email Tab / Access Account(s) Input Value Click Web Tab Click My Account Tab Click Help Tab Click Logout Click Speed Messages link Click Compose link Click Notifications link Click Configure link Click an email account link Click Access Account(s) link Expected Results Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted.79 UI Location: Go to Web options Admin disables user… UI Location: Go to Web options Admin disables user… UI Location: Preferences page Admin disables user… UI Location: Info page Admin disables user… UI Location: Info page Admin disables user… Click Visit URL link 7. Test Notes & Preconditions: For each step below. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deactivated.88 7.82 Click Help 7.91 7.89 7. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deactivated. S# 7.92 7.90 7. Login page should be displayed since user has been deactivated.28.28. Login page should be displayed since user has been deleted.28. Login page should be displayed since user has been deleted. Actual Results P/F Automated 7.85 7.S# Action Input Value Expected Results user has been deactivated. Login page should be displayed since user has been deactivated.86 7.81 Click Update 7. 28. 28.28. Scenario 3: Test the affects of deleting a user that is actively using Company with a desktop browser.28.28.28.28.28. Login page should be displayed since user Actual Results P/F Automated . 28. Login page should be displayed since user has been deleted.28.87 7. Login page should be displayed since user has been deleted. 28. Login page should be Actual Results P/F Automated 7.97 7. Login page should be displayed since user has been deactivated. 28.110 7. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deleted.109 7. Login page should be displayed since user has been deactivated.106 7.103 7. Login page should be displayed since user has been deleted. 28. 28. 28.99 7.S# Action Admin deletes user… UI Location: Email Account opened Admin deletes user… UI Location: Email Account opened Admin deletes user… UI Location: Email Account opened Admin deletes user… UI Location: Email Account opened Admin deletes user… UI Location: Email Account opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Message opened Admin deletes user… UI Location: Email Attachment list opened Admin deletes user… UI Location: Email Tab / Speed Messages Admin deletes user… UI Location: Email Tab / Speed Messages Admin deletes user… UI Location: Email Tab / Speed Messages Admin deletes user… UI Location: Edit Speed Message page displayed. 28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deleted.115 Click a message to open Click Reload Click Older messages Click Close Mailbox Click Connection Info Click Attachments Click Mailbox Click Full View Click Reply Click Reply to all Click Forward Click Delete Click Connection Info Click an attachment Click Add Speed Message link Click edit speed message link Click delete speed message link Click Update button Click Send button Click Update button Click an email account link Click Update .94 7. 28. 28.108 7.107 7. Login page should be displayed since user has been deactivated.112 7. 28.95 7. 28. 28.114 7. Login page should be displayed since user has been deactivated. 28.100 7.96 7. Login page should be displayed since user has been deactivated. 28. Admin deletes user… UI Location: Email Tab / Compose Admin deletes user… UI Location: Email Tab / Notifications Admin deletes user… UI Location: Email Tab / Configure Admin deletes user… UI Location: Configure Input Value Expected Results has been deleted.111 7. Login page should be displayed since user has been deleted.113 7. Login page should be displayed since user has been deactivated. 28. 28. 28. 28. 28.102 7. Login page should be displayed since user has been deactivated.101 7. Login page should be displayed since user has been deleted.104 7.98 7. Login page should be displayed since user has been deactivated. 28. Login page should be displayed since user has been deactivated.105 7. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deactivated. 28. Login page should be displayed since user has been deactivated. 28. 28. 133 7.124 7.117 7. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted.131 7.136 . Login page should be displayed since user has been deactivated.116 7.129 7. Login page should be displayed since user has been deactivated.126 7. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. 28. Login page should be displayed since user has been deactivated. Login page should be displayed since user has been deleted.119 7.128 7. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. 28.132 7. 28. 28. 28. 28. 28. 28. Actual Results P/F Automated 7. 28. 28. 28. 28. 28. Login page should be displayed since user has been deleted. 28.118 7. Login page should be displayed since user has been deactivated.120 7. Login page should be displayed since user has been deleted.121 7.122 7.127 7.125 7.S# Action email account Admin deletes user… UI Location: Web Tab Admin deletes user… UI Location: Web Tab / Browse Admin deletes user… UI Location: Web Tab / Browse Admin deletes user… UI Location: Web Tab / Browse Admin deletes user… UI Location: Web Tab / Browse Admin deletes user… UI Location: Web Tab / Browse Admin deletes user… UI Location: Web Tab / Bookmarks Admin deletes user… UI Location: Web Tab / Bookmarks Admin deletes user… UI Location: Web Tab / Bookmarks Admin deletes user… UI Location: Web Tab / Bookmarks Admin deletes user… UI Location: Web Tab / Bookmarks Admin deletes user… UI Location: Web Tab / Bookmarks Admin deletes user… UI Location: Edit Bookmark page displayed Admin disables user… UI Location: Web Tab / History Admin deletes user… UI Location: Web Tab / History Admin deletes user… UI Location: Web Tab / History Admin deletes user… UI Location: Web Tab / Settings Admin deletes user… UI Location: Web Tab / Settings Admin deletes user… UI Location: Web Page opened Admin deletes user… UI Location: Web Page opened Admin deletes user… UI Location: Web Page opened Admin deletes user… Input Value button Click Email Tab Click Go button Click Bookmarks link Click History link Click Settings link Click Browse link Click Add Bookmark link Click Clear Bookmarks link Click Original link Click via Company link Click Edit Bookmark link Click Delete Bookmark link Click Update button Click Clear History link Click Original link Click via Company link Click Clear Cookies button Click Clear Autocompletions button Click Next Part Click Previous Part Click Top Expected Results displayed since user has been deactivated. Login page should be displayed since user has been deleted. 28. 28.135 7.123 7. 28. Login page should be displayed since user has been deleted. 28. Login page should be displayed since user has been deleted. 28. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted.134 7. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. 28. 28.130 7. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. 28. 28. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deactivated.144 7.145 7. Actual Results P/F Automated . the user state must be reset to ‘Active’ and the user must be logged in and display the portion of the UI as indicated.143 7. Login page should be displayed since user has been deleted. 28. 28.137 7.140 7. Login page should be displayed since user has been deleted.147 7. 28.152 7. 28.153 Action UI Location: Company Home Admin deletes user… UI Location: Company Home Admin deletes user… UI Location: Company Home Admin deletes user… UI Location: Company Home Admin deletes user… Input Value Click Home tab Click Server tab Click Phone tab Click sync tab Expected Results Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted.146 7. S# 7. Scenario 4: Test the affects of deleting a user that is actively using Company with a WAP browser. Actual Results P/F Automated Scope: Test for Admin deletes user. 28. 28. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. 28.142 7.149 Action UI Location: Web Page opened Admin deletes user… UI Location: Web Page opened Admin deletes user… UI Location: Web Page opened Admin deletes user… UI Location: Web Page opened Admin deletes user… UI Location: My Accounts Tab Admin deletes user… UI Location: My Accounts Tab Admin deletes user… UI Location: My Accounts Tab / Devices Admin deletes user… UI Location: My Accounts Tab / Devices Admin deletes user… UI Location: My Accounts Tab / Devices Admin deletes user… UI Location: My Accounts Tab / Password Admin deletes user… UI Location: Help Tab Admin deletes user… UI Location: Help Tab Admin deletes user… UI Location: Help Tab Admin deletes user… Input Value Click Reload Click Full View Click Mark Click Connection Info Click Devices link Click Password link Click Update button Click Show all link Click Delete device link Click Change Password button Click Troubleshooting link Click About link Click Introduction link Expected Results Login page should be displayed since user has been deactivated.S# 7.150 7. 28. Login page should be displayed since user has been deactivated. Test Notes & Preconditions: For each step below. Login page should be displayed since user has been deleted.138 7. 28. Login page should be displayed since user has been deactivated. 28.148 7. 28. 28.151 7. 28. 28. Login page should be displayed since user has been deleted.141 7. 28.139 7. Login page should be displayed since user has been deleted. Login page should be displayed since user has been deleted. 29.29.29.6 7.8 Scenario 2: Some string length and special character tests Scope: Test short and long strings and special characters in various email components. Verification Steps: Verify that the messages are successfully sent and opened correctly.1 Action Send a message with specified input values. Message is sent successfully. Message is sent successfully. Message is opened successfully.155 Action UI Location: Company Home Admin deletes user… UI Location: Company Home Admin deletes user… Input Value Click password tab Click Log out link Expected Results Login page should be displayed since user has been deleted. in order to compose a mail.29.9 Test Item: Email to All Users Scope: Test the functionality of admin email. Message is opened successfully.29.154 7. 28. Message is sent successfully. Message is opened successfully.4 7.7 7. Open the message received from admin from the active user account Send a message with specified input values. Open the message received from admin from the active user account Send a message with specified input values. Message is opened successfully. . Action: Send email with input values mentioned below Test Notes & Preconditions: Make sure admin has valid and existing email id. Scenario 1: Test with blank components of email Scope: Test various input values for subject and body.2 7.5 7. Click on Email All Users button in List all users page. Open the message received from admin from the active user account Send a message with specified input values. Actual Results P/F Automated 7.29. Actual Results P/F 7. Open the message received from admin from the active user account Input Value Subject = Blank Message = Blank Subject = Blank Message = Blank Subject = Non blank Message = Blank Subject = Non blank Message = Blank Subject = Blank Message = Non Blank Subject = Blank Message = Non Blank Subject = Non Blank Message = Non Blank Subject = Non Blank Message = Non Blank Expected Results Message is sent successfully.29. 28.3 7.S# 7. S# 7. Login page should be displayed since user has been deleted.29. Body = Contains all special characters. Expected Results Message is sent successfully Message is opened successfully. Body = Contains only “##”. Login and check the inactive user’s primary email account for new messages.29.29.13 Message is sent successfully. since the user was disabled.29. Subject =Contains all special character. Message is sent successfully.38 Message is only sent to admin and all the active users. Message is opened successfully. Messages are opened successfully Actual Results P/F 7.15 7.29. S# 7.36 7.29. Subject = Maximum allowed length or simply very long. Expected Results Message is only sent to admin.29. Message is opened successfully. Body = Maximum allowed length or simply very long.11 Action Send the message of specified char length for subject and body.29. Actual Results P/F 7. Input Value No active user is present.29.35 Action Admin sends an email to all users with valid values in subject and body.29.29. Check for new messages and open those messages in Admin’s ‘Reply to’ email account.37 Active and Inactive users are present. 7. Inactive users should not receive this message. Subject = Contains all special character Body = Contains all special characters Subject =Contains only ”##”.14 7. No Messages were received from admin. since admin is in Bcc by default.12 Message is opened successfully.29. 7. Message is sent successfully.9 7. . Body = Contains only “##”. Body = Maximum allowed length or simply very long.29. 7. Admin sends an email to all users with valid values in subject and body. after enabling the inactive user by admin. Open the message received from admin from the active user account Send the message of specified char length for subject and body. Open the message received from admin from the active user account Input Value Subject =1 char Body = 1char Subject =1 char Body = 1char Subject = Maximum allowed length or simply very long. Open the message received from admin from the active user account Send the message of specified char length for subject and body. Open the message received from admin from the active user account Send the message of specified char length for subject and body. Subject =Contains only ”##”.10 7.S# 7.16 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. 7. No connection between SRC and SMTP server.41 Active and Inactive users are present.29.49 7.51 .29.45 Connection between SRC and SMTP is fine.29. Check for new messages received from admin from users email accounts that were used for SRC account creation. Admin clicks on the “Try again” button of the error page. The old ‘Reply to’ email address is used when admin sends an email message to active users. Admin runs the reconfig script from command line and change the reply to address.43 Admin composes and sends a message with valid values in subject and body. Message is sent successfully with the old Actual Results P/F 7. No mail is sent.42 7.39 Action Admin sends an email to all users with valid values in subject and body. And the header of the received message should correctly display the admin’s mail address. Message are opened successfully Scenario 6: Administrator changes “reply to” address Scope: Test for changing administrator’s reply to address.S# 7.29. Open the email received from admin and click on ‘reply to’ link. 7. Admin sends an email to all users with valid input Login to SRC as an active User. Admin sends an email to all users with valid input Input Value Save changes and restart SRC Expected Results The new ‘Reply to’ email address is used when admin sends an email message to active users. Admin clicks cancel button of the error page.40 7.50 Abort the process before saving. Input Value Some of the active users do not have primary email accounts.48 7. Message is sent successfully with new ‘Reply-to’ email address The email address in the ‘To’ header should be the new ‘Reply-to’ email address.29.29.29. Expected Results Message is sent to active users email addresses that were used for SRC account creation.47 Action Admin runs the reconfig script from command line and change the reply to address. 7. S# 7.44 7. 7.29. Message is received from admin successfully. The active user does not have primary email account. Email will be sent to the active users. No mails from admin were received since the email sending was cancelled.29.29. Actual Results P/F 7.46 Check for new messages and open those mails in Admin’s reply to email account. Check for new messages in Admin’s reply to email account. The success screen should be displayed with the message “Mail sent to all enabled users”. The main “Users” page should be displayed.29.29.29. The error page should be displayed with the “Try again” and “Cancel” buttons. Admin sends an email to all users with valid values in subject and body. Message is sent to admin and all the active users. 10 Test Item: Logout Scope: Test that no operations can be performed after Logout. Verification Steps: Verify the status of the 2 users depends on the operations performed on them. The user is enabled. 30.1 7. S# 7.29.11 Test Item: Multiple browser window usage Scope: Test simultaneous and conflicting operations from multiple browser windows.2 7. Both users are Actual Results P/F Automated . Action: Admin Logs out. chooses the browser’s <Back> option. Test Notes & Preconditions: Admin is logged in from two separate browser windows. Enable the same registered user in both browser windows at the same time.31.31.31.S# Action Input Value Expected Results ‘Reply-to’ email address Actual Results P/F 7.2 7. Admin is successfully logged back in. Verification Steps: Verify the Admin is accessing the options of Company even if Admin selects logout option. No error results from the conflict. chooses the browser’s <Back> option. clicks any command function… Click login link and log back in… Input Value Expected Results Message should be displayed that session is invalid or expired and provides a link to log back in.52 Login to SRC as an active User. Test Notes & Preconditions: Admin user is logged into the administration page and has performed some admin functions. Scenario 1: Test simultaneous and conflicting operations from multiple browser windows. 7. clicks any command function.30. Open the email received from admin and click on ‘reply to’ link. Actual Results P/F Automated 7. The email address in the ‘To’ header should be the old ‘Reply-to’ email address. Scenario 1: Test using the browser’s <Back> option after logout. Disable 2 different users at the Input Value Expected Results Both users are enabled successfully. Action: Test simultaneous and conflicting operations from multiple browser windows.3 Action Enable 2 different registered users at the same time.1 Action Admin Logs out. S# 7. 5 7. Verification Steps: Verify the Admin password to enter in to the admin page with the new password. Input Value Expected Results disabled successfully. Error message should be displayed because password cannot be blank. Delete 2 different users at the same time. Disable the same user in both browser windows at the same time.7 7. 31.12 Test Item: Change Admin password Scope: Test the ability to change the Admin’s password. Error message should be displayed because confirmation password must match the newly Actual Results P/F Automated 7.32. The second request will give an error that the user already exists. 31. Actual Results P/F Automated 7.12 Delete a user in one window. 31. A message should be displayed that the user does not exist. The create request that is submitted first creates the user.4 7. 31.8 Edit and update 2 different users at the same time. 7. 31. 32. Edit and update the same user in both browser windows at the same time. Both users are deleted successfully.11 7. attempt to disable the user in the other window… F – bug #5652 F – bug #5653 7. The user info is updated. 31. A message should be displayed that the user does not exist. Delete the same user in both browser windows at the same time. The user is disabled. S# 7.3 7. 31. 32.10 7. The second request will give an error that the user does not exist. attempt to edit the user in the other window… Delete a user in one window. Create 2 different users at the same time. Create the same user in both browser windows at the same time.S# Action same time. No error results from the conflict. 32. 31. Scenario 1: Test changing the Admin’s password. The delete request that is submitted first deletes the user.4 .9 7.6 7. Both users are created successfully. Test Notes & Preconditions: Admin is logged into the system. 31. No error results from the conflict. Action: User submits Change Password form from the password tab. Info for both users is updated successfully.2 7.1 Action User submits Change Password form… User submits Change Password form… User submits Change Password form… User submits Change Password form… Input Value Old Password = Blank New Password = Blank Confirm Password = Blank Old Password = Invalid New Password = any Confirm Password = any Old Password = Valid New Password = Blank Confirm Password = Blank Old Password = Valid New Password = any Confirm Password = Does NOT match Expected Results Error message should be displayed because original password is invalid. Error message should be displayed because original password is invalid. 12 Logout and attempt to login with OLD password Password = valid new password Old Password = all special chars New Password = Maximum characters that input field permits Confirm Password = Maximum characters that input field permits Password = OLD password 7. . User submits Change Password form… Logout and attempt to login with OLD password 7. Actual Results P/F Automated 7. Verification Steps: The default values are always be set automatically when the page is revisited.10 7. selection of log files can also be configured before sending logs. 32. Admin is logged in successfully. 32.8 Attempt to login with new password. 32. 7.7 7. User submits Change Password form… 7. Test Notes: This option available only in desktop browsers and only in administrator site. 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. the maximum size of the log files. Message should be displayed stating that the password has been changed. The duration of the error logs in the log file.6 Old Password = Valid New Password = Any Confirm Password = Matches Password = OLD password 7. 32.13 Attempt to login with new password. Appropriate error message should be displayed saying that password is invalid. Admin cannot login with old password. Password = valid new password User cannot login with old password. Appropriate error message should be displayed saying that password is invalid.9 Password = valid new password Old Password = Valid New Password = All special chars Confirm Password = Matches Password = OLD password 7. This ID can be modified by the admin through desktop.13 Test Item: Sending log files to Company Support. specified log files registers the new start time and roll time. 32. Message should be displayed stating that the password has been changed. 32. logs of specified date range and with given comments. Verification Steps: Verify sending system logs as per the configuration set up by the admin.11 Attempt to login with new password.5 User submits Change Password form… Logout and attempt to login with OLD password 7. 32. 32.S# Action Input Value Expected Results types password. Message should be displayed stating that the password has been changed. Appropriate error message should be displayed saying that password is invalid. Specified interval. User cannot login with old password. User is logged in successfully. User is logged in successfully. 32. 43.Scenario 1: Test sending logs for different configuration.43.4 7. N1 should send the selected log files only to the email specified.13 7.14 7.com Actual Result P/F Autom ated 7. Click on the submit button Click on ‘Submit’ button Input Value Expected Result N1 should display the System logs page.43.1 7.12 7. and click on ‘Submit’ button Modify the maximum number of bytes per email.11 7.3 7. 7. email input field.7 7.8 7. S# 7.15 7. and click on ‘Submit’ button Modify the maximum number of bytes per email.6 Log files= one or all Other fields= default Log file= any of the available or all log files Input = NULL Log file= any of the available or all log files Input = Zero Log file= any of the available or all log files Input = negative value Log file= any of the available or all log files Input = positive decimal value Log file= any of the available or all log files Input = any positive value. N1 should send the selected log files to the email address specified.43.18 7.43. which has a link of ‘Sending logs’ at the top of the page. N1 should send the selected log files only to the email specified. and click on ‘Submit’ button Modify the maximum number of bytes per email.43. Later the admin should get an undelivered
[email protected] N1 should send the selected files as per the default values given. comments input filed and date fields. N1 should display the ‘sending logs’ page with log file names. Please enter a size” and should have a link to abort the current process N1 should display an error of “Max size per email should have a valid data” and should have a link to abort the current process N1 should display an error of “Max size per email should have a valid data” and should have a link to abort the current process N1 should allow the max size given and send the log files N1 should allow the max size given and send the log files N1 Should display an error saying that “Please enter a valid email address” and should have a link to abort the current process N1 Should display an error saying that “Please enter a valid email address” and should have a link to abort the current process N1 should accept the email id given and should send the logs to the same. and click on ‘Submit’ button Modify the email address and click on ‘Submit’ button. By default it should be def. N1 should accept the email id given and should send the logs to the same.16 7.10 7. N1 should display an error saying “No log file is selected.43. and click on ‘Submit’ button Modify the maximum number of bytes per email.5 7.43.43.17 7. maximum size of logs/email.43.43.43. Please select one or more log files to send” and should have a link to abort the current process N1 should send the selected log file only to the email specified.43.43.2 Action Click on ‘System logs’ tab Click on ‘Sending logs’ link Verify the default maximum no of bytes Verify the default email address in the recipient email address Click on ‘Submit’ button Modify the maximum number of bytes per email.43.43. Log file = any Email Address= Empty Log file = any Email Address= syntactically Invalid Log file = any Email Address= Invalid (But Syntactically Valid) Log file = any Email Address= Valid (But Syntactically Valid) Comments = Empty All other field=Valid Log file = None All other fields = Valid 7.19 Click on ‘Submit’ button Click on ‘Submit’ button Mark the ‘Select all logs’ check box then click on ‘Submit’ button Log file = One All other fields = Valid Log file = More than One All other fields = Valid All other fields = valid . Modify the email address and click on ‘Submit’ button. N1 should display an error of “Max size per email is not entered. By default this should be 2MB only. Modify the email address and click on ‘Submit’ button. Modify the email address and click on ‘Submit’ button.43.43.43. 30 7. N1 should correct the date to the nearest or previous date ranges and proceed to send the log files.36 Select ‘Abort sending all files’ option and click on ‘Submit’ button… Select ‘Abort sending only the files that are too large’ option and click on ‘Submit’ button… Select ‘ Send all files N1 should show an appropriate error stating that log files selected is more than the specified byte size and give the following options: 1.43. Max bytes/email = 1MB or other Selected log file > above max value set 7.29 7.43.22 7. N1 should refresh the screen and continue sending logs. N1 should show the progress screen again and sending logs process still be continued.43.20 Action Unmark the ‘Date range’ check box and click on ‘Submit’ button Mark the ‘Date range’ check box and click on ‘Submit button Select the date range and click on ‘Submit’ button Select the date range and click on ‘Submit’ button Select the date range and click on ‘Submit’ button Select the date range and click on ‘Submit’ button Input Value All other fields = Valid Expected Result The date range fields should be disabled and N1 should send the full log files selected without any date range filtering. N1 sends all the selected log files and .43. N1 should send the log files for the day specified only to the specified date range.31 7. And it should auto refresh every 10 sec. email or any other tab) and revisits the ‘System logs’>’Sending logs’ screen Click on ‘Submit’ button… All fields = Valid data N1 should start sending log files to the specified email ID.43. Actual Result P/F Autom ated 7.S# 7. N1 should send the selected log files for the specified date range to the email specified.yyyy=2004 All other fields = Valid From= Valid Through= Valid later than the ‘From’ date All other fields = Valid All fields = Valid data 7.43.35 7.23 7.24 All other Fields = Valid From= current day Through= current day All other fields = Valid From and Through date = same All other fields = Valid From= later than through date Through= current All other fields = Valid From and Through= invalid Mm=45.43.43.43. N1 should display an appropriate error stating that the date range selected is invalid. N1 should send the log files for the current day only to the specified date range.28 7.43.43.43. N1 should abort the sending logs process and should show the process completion screen.33 Select ‘continue waiting’ option while N1 processing the sending logs Select ‘abort’ option while N1 processing the sending logs Select ‘abort’ option in the middle of the process or a bit later In system logs page click on ‘Submit button’ When the sending logs is in progress go to other screens (web. Abort sending all files 2. dd=55. but it might have sent some log files.43.27 7. Send files anyway N1 should abort sending log files and should display process completion screen.32 7.43. N1 should abort sending the larger files as specified and send the other log files selected if any and should display process completion screen.34 7.21 7.43.26 Select the date range and click on ‘Submit’ button Click on ‘Submit’ button 7.43. N1 should start the process of sending logs by displaying a message contains the options to abort and continue waiting. Abort sending only the files that are too large 3.43.25 7. N1 should send the log files for the selected date range only to the specified date range. N1 should abort sending logs. Actual Results P/F Automated 7. Actual Results P/F Automated 7.44. which are failed to send. Actual Result P/F Autom ated 7. Refresh. It should take admin to particular user’s account.1 7. Choose Refresh. Create a new user. The page is simply redisplayed. The reason for this is at one point in time. Refresh should not do this. The page is simply redisplayed. Refresh. which are failed to send. which are successfully sent to the specified email and list of log files if any. S# 7. Action: Enable a new user registration request. Delete a user.45. N1 should show the progress page with the list of log files.38 7. S# 7. It should display the list of files if any. the system would resubmit the same form and cause an error. Test Notes & Preconditions: Admin is logged into the system and click on the Users Tab and click on list all users.43.2 7.44. Scenario 1: Test browser refresh after submitting forms.45.4 Action Enable a new user registration request.37 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.2 Display user pages to Admin Click on configure option hyper link .1 Action Display configure option Input Value Expected Results Admin should be able to see the configure hyperlink in Action Items for every user. Test Notes & Preconditions: Login to Admin page.14 Test Item: Refresh after submits Scope: Test clicking refresh in the desktop browser after submitting a form. Choose Refresh.S# Action anyway and click on ‘Submit’ button… Verify the process completion screen If any errors occurs while sending logs… Input Value Expected Result display the process completion screen. Scenario 1: Test user / admin level privileges. Verification Steps: Verify the display results are not changing even after selecting the refresh option from the browser’s window.43. Verification Steps: Verify that the Admin level privilege options are displayed as mentioned below.44. Input Value Expected Results The page is simply redisplayed. enter valid data in the search field but does not hit “Search” button until session timed out.46.46.3 Admin session validation 7.S# Action Input Value from action items for particular user. S# 7. Admin displays create user form. Click here to login” 7. Error is displayed that session has timed out. Login into Admin UI screen select “Enable/Delete” button under “Request-Registration Request” after the session expires. Click here to login” It should display the following message “Session invalid or expired.2 Admin session validation 7. Click here to login” It should display the following message “Session invalid or expired. Click here to login” User should not be added to the List of Users. Admin then hits “submit” button on the form.46. Login into Admin UI screen select “Enable/Delete” button under “Request-Upgrade Request” after the session expires. Let the system sit idle until the user session had expired and then click on “List all Administrators” Expected Results It should display the following message “Session invalid or expired. Admin displays “Search” user screen. Let the system sit idle until the user session had expired and then click on "List all Users" link.46.1 Action Admin session validation Input Value After creating an Online request.46. Click here to login” It should display the following message “Session invalid or expired.46.4 Admin session validation 7. Admin then hits “search” button on the screen. Expected Results just as if the 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) Actual Results P/F Automated 7. Action: Test the admin session validation for new user creation. Actual Results P/F Automated 7. Scenario 1: Test the admin session validation.16 Test Item: Session validation Scope: Test the admin session validation.6 Admin session validation . Test Notes & Preconditions: Admin is logged into the system and click on the Users Tab. fill out the form but does not hit “Submit” button until session timed out.5 Admin session validation It should display the following message “Session invalid or expired. Admin logs back in. Verification Steps: Verify that the session is expired after some time. Do an “upgrade request” from Mobile Device. Admin log back in.46.46. Admin then hits “Delete” button on the form. Error is displayed that session has timed out. or 20 Attempts Expected Results User is locked out and client and client data are wiped from the device. Expected Results Selected user should not be Edited/Configured/del eted/tested from the list of users. Actual Results P/F Automated . Let the system sit idle until the admin user session had expired and then click on "Clear Cache" button under Provision.46. S# 7.46. fill out the form but does not hit “Delete” button until session timed out.9 Admin session validation 7.46.13 Admin session validation It should display the following message “Session invalid or expired. Admin displays Email form. Admin then hits “Send” button on the form. Error is displayed that session has timed out. Admin selects “Client Admin” tab under which “Status/Sessions/Users/Usage/Ac count Admin” should be selected after the session had expired. Let the system sit idle until the admin user session had expired and then click on "Logout" . Click here to login” It should display the following message “Session invalid or expired. Admin selects “Licensing” tab let the system sit idle after which select “List Users”.13 Action Admin sets “Login failures before data wipe” Input Value Login failure before data wipe=4 or10. Actual Results P/F Automated 7.7 Action Admin session validation Input Value Admin opens Edit/Configure/ Delete/Test user form.S# 7. Scenario 1: Admin can configure the number of failed login attempts before the client data is wiped. Click here to login” It should display the following message “Session invalid or expired. 7.19.11 Admin session validation 7. Click here to login” The message should not be sent to all the active users.46.12 Admin session validation It should display the following message “Session invalid or expired.10 Admin session validation 7.46. Click here to login” It should display the following message “Session invalid or expired.8 Admin session validation 7. Admin logs back in. fill out the form but does not hit “Send” button until session timed out. Admin selects “Logs” tab let the system sit idle after which select “Submit” button after entering all the details. 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. 19. Actual Results P/F Automated .13 Action Admin sets “Login failures before data wipe” Input Value Login failure before data wipe=No= limit Expected Results Client data should never wiped during invalid login attempts.S# 7.