You are on page 1of 12

Component

Test Cases Name


Prepared for
[Customer Name]
[Date]
Version 1 Final

Prepared by
[Author Name]
[Author Title]
[Author Email]

Contributors
[Type Contributors Here]

Instructions: Update and add to the table in the Test Cases tab of this workbook to prepare for delivery to
the customer. The document should be delivered prior to the start of testing for review and sign-off and
updated with the results of testing. The workbook will be used to track any issues that are identified during
testing and should be made available to the customer after each major iteration.

Testing Status
Data is refreshed upon opening the file or by clicking anywhere in
the table and pressing Alt+F5
Result CategorCount - Result
Pending
Open ma 1
Open fo 1
Create 1
Send ne 1
Receive 1
Reply to 1
Open an 1
Create 1
Receive 1
Read exi 1
Create 1
Reply to 1
Pending Result 12
Total Result 12
book to prepare for delivery to
g for review and sign-off and
issues that are identified during
ation.
Test Cases
The test cases documented in the following table will be executed to verify that the
solution is functioning as designed. Any issues that are identified during testing will be
logged in the Issues tab of this workbook and referenced in the corresponding test case.

Result Definition
Pass The test showed the expected result with no
issues
Partial Fail The test showed the expected result, but issues
were identified
Fail The test did not show the expected result

Update and add to the test cases for the component in this table. Make sure to assign a
result of Pending for all new tasks so the tasks show up properly in the dashboard. As
you complete testing, document the results, log any issues in the Issues tab, and take
notes as necessary. Any failures or partial failures associated with blocking issues should
be remediated and retested.

ID Category Test
T1 Open mailbox User can succesfully open their migrated mailbox

T2 Open folders User can successfully open folders within their


migrated mailbox and view the contents

T3 Create new folders User can create a new folder in their migrated
mailbox
T4 Send new email User can send a mail from their migrated
mailbox
T5 Receive new Email User can receive mail to their new mailbox

T6 Reply to an existing email User can successfully reply to existing migrated


mail
T7 Reply to an existing calendar User can successfully reply to an existing
invite migrated calendar invite
T8 Open an existing Calender User can successfully open a migrated calendar
meeting meeting
T9 Create a new meeting User can successfully create a new meeting

T10 Receive replies for new User successfully receives meeting replies
meetings
T11 Read existing Contacts User can successfully view migrated contacts
T12 Create new Contact User can create and save a new contact
Method Expected Results
Open via a new profile in the Outlook client User can successfully open their migrated
aswell as via OWA. mailbox using either method
Open folders in the Outlook client aswell as via All folders can successfully be opened
OWA

Create a new folder in the Outlook client aswell Folder can be created and saved
as via OWA
Send new mail in the Outlook client aswell as via New mail can be created and sent
OWA
See email flowing into their migrated mailbox via A migrated user receives new mail from internal
Outlook and OWA and external users

Existing email can be replied to via Outlook and Can successfully reply to an existing migrated
OWA mail
Reply to an existing calendar invite via Outlook Creator of the orginal invites receives a success
and OWA reply
Open via Outlook and OWA Can successfully open and join an existing
migrated calendar meeting
Create a new meeting via Outlook and OWA New meeting is successfully created and saved

Send a new meeting to various users, both See new replies coming into the mailbox via
migrated and not yet migrated Outlook and OWA
Migrated contacts can be read Existing contact information can be successsfully
read
Create a new contact in migrated mailbox Contact can be created and saved
Result Issue Reference Notes
Pending

Pending [OL] This seems unnecessary

Pending [OL] This seems unnecessary

Pending

Pending [OL] Should probably expand on the message routing


scenarios to cover mail received from people in the
source tenant, Internet mail, etc.

Pending

Pending

Pending

Pending [OL] This seems unnecessary

Pending

Pending
Pending [OL] This seems unnecessary
[OL] Nothing for DeploymentPro? Mobile devices?
Archives?
Issues
All issues identified during testing will be logged in this table and assigned a severity, per
the following table. The assigned severity will influence whether remediation is within
the scope of the project, per the statement of work.

Make sure to reference the SOW for the project to confirm that the standard defect
remediation scope, as documented in the following table, applies to this project. Make
any necessary adjustments to the Description and Remediation in Scope columns.

Severity Description
P1 Blocking defect - Development, testing, or production
launch cannot proceed until this type of defect is
corrected. A defect of this type blocks further progress
in this area. The solution cannot ship and the project
team cannot achieve the next milestone until such a
defect is corrected.

P2 Significant defect - This type of defect must be fixed


prior to moving to production. Such a defect, however,
will not affect test plan implementation.

P3 Important defect - It is important to correct this type


of defect. However, it is possible to move forward into
production through use of a workaround.

P4 Enhancements and low priority defects - P4 defects


consist of feature enhancement and cosmetic defects.
These include design requests that vary from original
concepts.

ID Date Identified Issue


Remediation in Scope
Yes

Yes

No

No

Test Case Severity Status


Resolution/Mitigation Notes