• Like

Thanks for flagging this SlideShare!

Oops! An error has occurred.

HealthCare Project Test Case writing guidelines

  • 6,263 views
Published

 

Published in Education , Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
6,263
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
72
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. H2K Infosys is business based in Atlanta, Georgia – United States Providing Online IT training services world wide. www.H2KINFOSYS.com USA - +1-(770)-777-1269, UK - (020) 3371 7615USA - +1-(770)-777-1269, UK - (020) 3371 7615 Training@H2KInfosys.com / H2KInfosys@Gmail.comTraining@H2KInfosys.com / H2KInfosys@Gmail.com
  • 2. H2K INFOSYS PROVIDES WORLD CLASSH2K INFOSYS PROVIDES WORLD CLASS SERVICES INSERVICES IN
  • 3. 1. Test case writing guidelines 2. Testing Process – Review doc 3. Review test case scenarios – Review doc 4.Review sample test case documents – Review doc 5. Review UAT(User Acceptance Testing) document – Review Doc Table of Contents
  • 4. 1. Name - Select the Test type from the list and name the test as “TC_XXXX” (where XXXX is the functional area – e.g. “TC_Register a new Member Functionality”) 2. Identify any pre-requisite steps for the test case in the description section of the test plan • What needs to be set-up before the test case is executed • If there are no pre-requisites step for the test case, enter the following – “PRE-REQUISITE: NONE” • Enter the test case purpose and the requirements tested in the description window - Test Case purpose for each case is provided in the Case Purpose column in the UAT Test Case tracking workbook 3. Design the structure of the test case based on the test case purpose – clearly define the step name and description in the design steps window 4. At the bottom of the description window, set the severity level of the test 5. Identify the record(s) to be used and then gather data 6. Document key information of the selected record(s), data to be verified, and data to be changed to, in the tracking workbook’s. The advantage of doing this is that it will facilitate defect investigation, as the information documented will provide evidence of how the test case was designed; and will also avoid the data integrity issue that may arise when the same record is being used in multiple test cases. Test Case writing guidelines
  • 5. Thank you Your feedback is highly important to improve our course material and teaching methodologies. Please email your suggestions. USA +1-(770)-777-1269 UK (020) 3371 7615 Training@H2KInfosys.com H2KInfosys@Gmail.com H2K Infosys is e-Verified business based in Atlanta, Georgia – United States H2K Infosys acknowledges the proprietary rights of the trademarks and product names of other companies mentioned in this document.
  • 6. DISCLAIM ER H2K Infosys, LLC (hereinafter “H2K”) acknowledges the proprietary rights of the trademarks and product names of other companies mentioned in any of the training material including but not limited to the handouts, written material, videos, power point presentations, etc. All such training materials are provided to H2K students for learning purposes only. H2K students shall not use such materials for their private gain nor can they sell any such materials to a third party. Some of the examples provided in any such training materials may not be owned by H2K and as such H2K does not claim any proprietary rights for the same. H2K does not guarantee nor is it responsible for such products and projects. H2K acknowledges that any such information or product that has been lawfully received from any third party source is free from restriction and without any breach or violation of law whatsoever.
  • 7. DISCLAIM ER H2K Infosys, LLC (hereinafter “H2K”) acknowledges the proprietary rights of the trademarks and product names of other companies mentioned in any of the training material including but not limited to the handouts, written material, videos, power point presentations, etc. All such training materials are provided to H2K students for learning purposes only. H2K students shall not use such materials for their private gain nor can they sell any such materials to a third party. Some of the examples provided in any such training materials may not be owned by H2K and as such H2K does not claim any proprietary rights for the same. H2K does not guarantee nor is it responsible for such products and projects. H2K acknowledges that any such information or product that has been lawfully received from any third party source is free from restriction and without any breach or violation of law whatsoever.