Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Test CaseWriting<br />August, 2011<br />
From Requirements to Test Case Workflow<br /><br /><br />
Definition – Test Case<br />What is a Test Case?<br />Definition 1<br />A set of test steps, execution conditions and expe...
Basic Parts of a Test Case<br />A Test Case is multiple Steps which are comprised of these 4 basics parts:<br />Descriptio...
Test Step<br />A Test Step is the smallest portion of a Test Case. It typically describes a single action in a chain of ac...
Test Cases Structure Example<br />Test Cases: <br />Open a new consumer customer checking account<br /><ul><li>Step 1 Desc...
Expected Result
Actual Result
Step 2 Description
Expected Result
Actual Result
Step 3 Description
Expected Result
Actual Result</li></ul>Open a new consumer customer savings account<br /><ul><li>Step 1 Description
Expected Result
Actual Result
Step 2 Description
Expected Result
Actual Result
Step 3 Description
Expected Result
Upcoming SlideShare
Loading in …5
×

Writing Test Cases 20110808

29,109 views

Published on

A guide for a UAT project I\'m on for writing test cases

  • How To Get Urgent Blank Atm Card....for years now i have been so poor, frustrated and heart broken. i lost my Job and nobody was even ready to assist me, but so lucky for me i got a blank ATM card from a professional hacker, i thought this card wont work like the others, but i just gave it a try and it worked pretty cool like magic,and i am able to withdraw enough money with this blank ATM card without any blockage. i am so blessed to have this card with me, i make withdrawals always and i am so rich now. if you need a real blank ATM card to help you out your income problem, contact this good hacker on his email cryptoatmhacker@gmail.com then you will enjoy what i am enjoying now. thanks
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Writing Test Cases 20110808

  1. 1. Test CaseWriting<br />August, 2011<br />
  2. 2. From Requirements to Test Case Workflow<br /><br /><br />
  3. 3. Definition – Test Case<br />What is a Test Case?<br />Definition 1<br />A set of test steps, execution conditions and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.<br />Definition 2<br />Test cases are specific inputs and procedures that you will follow when you test software.<br />Analogy<br />A Test Case is like a recipe. You follow the steps to produce an end result.<br />
  4. 4. Basic Parts of a Test Case<br />A Test Case is multiple Steps which are comprised of these 4 basics parts:<br />Description of the Test Case<br />Verify that the text is blue.<br />Description of each Step<br />Locate text in first paragraph<br />Expected result each Step<br />The text should be blue<br />Actual result each Step<br />The text is blue<br />
  5. 5. Test Step<br />A Test Step is the smallest portion of a Test Case. It typically describes a single action in a chain of actions which go on to comprise a Test Case:<br />Usually start with a verb such as:<br />Verify, Validate, Navigate<br />Usually are doing something very discrete.<br />Validate color, Verify SSN, Navigate to account<br />Examples:<br />Step 1. Navigate to SSN field. <br />Step 2. Enter a valid ID.<br />Step 3. Validate that the SSN field will only accept a 9 digit number<br />
  6. 6. Test Cases Structure Example<br />Test Cases: <br />Open a new consumer customer checking account<br /><ul><li>Step 1 Description
  7. 7. Expected Result
  8. 8. Actual Result
  9. 9. Step 2 Description
  10. 10. Expected Result
  11. 11. Actual Result
  12. 12. Step 3 Description
  13. 13. Expected Result
  14. 14. Actual Result</li></ul>Open a new consumer customer savings account<br /><ul><li>Step 1 Description
  15. 15. Expected Result
  16. 16. Actual Result
  17. 17. Step 2 Description
  18. 18. Expected Result
  19. 19. Actual Result
  20. 20. Step 3 Description
  21. 21. Expected Result
  22. 22. Actual Result</li></li></ul><li>Things to Consider<br />Points to keep in mind when writing Test Cases:<br />Test Data needs<br />Environment needs<br />“Log on” (user ID) needs<br />Hardware needs<br />Batch requirements<br />Interfacing applications (up and down stream)<br />Positive and negative scenarios* <br />Boundary Test (how big/small can I go and what happens if I do)**<br />* Written Test Cases should focus should be Positive scenarios, in addition to “worst-case” scenarios; however, Negative testing may be done Ad Hoc during the test execution phase.<br />** Boundary testing should have been covered during Product Test.<br />
  23. 23. Best Practices <br />When writing:<br />Avoid lingo (words, abbreviations, acronyms and phrases used in your department or field)<br />The customer will be using ABF financing.<br />The customer will be using Asset Based Financing.<br />Write the case as if you are not going to be executing it.<br />Report should look like Bettys report.<br />Output should be TPS 123 report.<br />Write Test Cases so they Test a limited set of functionality.<br />Verify that all Deposits work in Alnova.<br />Execute a deposit in Alnova.<br />
  24. 24. Example Test Case with Steps<br />For existing consumer and commercial accounts, add an alternative contact address for a statement address using this mailing address: 123 Maple Street, Birmingham, AL<br /> Test Case: Open an existing consumer account: <br />Test Step 1. In business object, enter last name of customer<br />Test Step 2. Choose Add an Address <br />Test Step 3. Enter 123 Maple Street<br />Test Step 4. Etc….<br />
  25. 25. Additional Example - Scenario<br />
  26. 26. Additional Example – Test Case<br />
  27. 27. UAT Scenario Naming Convention <br />Department_Type_ Test Scenario Number_Description<br /><ul><li>Department = See Department Abbreviation 06-28-2011.xls for a list of the Department abbreviations.
  28. 28. Type = Use an abbreviation of the type of transaction that allows you to best identify the Test Scenario
  29. 29. Test Scenario Number – Incremental Number
  30. 30. Description – Brief description of the event that you are testing</li></ul> <br />Example<br />RET_CONSREG_001_Register a Customer <br />This means Retail Department – Registering a Consumer – Incremental number - Scenario Description<br />* 001 is the scenario number and is the number used in the Test Case naming convention<br />
  31. 31. UAT Test Case Naming Convention<br />Department_Type_ Test Scenario Number_Test Case Number _Description<br /><ul><li>Department = See Department Abbreviation 06-28-2011.xls for a list of the Department abbreviations.
  32. 32. Type = Use an abbreviation of the type of transaction that allows you to best identify the Test Scenario
  33. 33. Test Scenario Number – Incremental Number
  34. 34. Test Case Number – Incremental Number (May have multiple Test Cases per Test Scenario)
  35. 35. Description – Brief description of the event that you are testing</li></ul>Example<br />CM_NCONMAINT_001_002_Register a Customer <br />This means Commercial Department – Non-Consumer Maintenance – Test Scenario number– Test Case Number – Test Case Description<br />
  36. 36. Scenario Applied to Test Cases<br />How Scenarios Can be Used for Your Test Cases <br />
  37. 37. Test Case Template<br />Test Case Template<br />
  38. 38. Test Case Template Column Definitions <br />These are the definitions for each column:<br />Test Case Template<br />
  39. 39. UAT Test Case Template Required Fields<br /><ul><li>The first row of every test case must have some value in every cell except A
  40. 40. Subject (cell A) - can be left blank
  41. 41. Test Name - can not exceed 40 characters
  42. 42. Test Name - can not have any unique characters such as , : ; ‘ < () / ^ " *
  43. 43. Test Name - can have an underscore or a period (_ . ) along with numbers and letters
  44. 44. Description, *Pre-Requisites, or *Test Data – if these fields on the first row of a test case are blank, enter TBD or N/A in the field/s
  45. 45. Test Attributes - for UAT test cases must say “User Acceptance Test”
  46. 46. Test priority - must be either A (high), B (medium) or C (low)
  47. 47. Requirement ID - should only list the most applicable requirements
  48. 48. Type - Manual
  49. 49. All following cells (in the rows below the first line) must be blank except the design steps (Step Name, Description – Design Steps, Expected– Design Steps)
  50. 50. Remove Blank rows between tests (they will not be accepted by ALM)</li></ul>*Pre-Requisites = items (non-data) required to perform the test such as hardware, environment needs, batches (example: ATM cards)<br />*Test Data = data required to perform the test (example: valid account information) <br />
  51. 51. UAT Test Case Template Requirements <br /><ul><li>The first row of every test case must have some value in every cell - Manually add if missing
  52. 52. Subject on the first row of every test case must have the path to the upload destination. For example: UAT/Rel 1.0/RET for Retail
  53. 53. Test Name - can not exceed 40 characters - Manually correct
  54. 54. Description - can not have any unique characters such as , : ; ‘ < () / ^ " * Manually remove any unique characters before uploading
  55. 55. Description - can have an underscore or a period (_ . ) along with numbers and letters
  56. 56. Description, Pre-Requisites, or Test Data – if these fields on the first row of a test case are blank, enter TBD in the field/s – Add these if possible or TBD
  57. 57. Test Attributes - for UAT test cases must say “User Acceptance Test”
  58. 58. Test priority - must be either A (high), B (medium) or C (low)
  59. 59. Requirement ID – only one ID is accepted, remove all others
  60. 60. Type – Manual
  61. 61. All following cells (in the rows below the first line) must be blank except the design steps (Step Name, Description – Design Steps, Expected)
  62. 62. Remove Blank rows between tests (they will not be accepted by ALM) Manually add/remove any blank rows
  63. 63. If first row has any blank cells, add TBD or N/A</li></li></ul><li>Test Cases in ALM <br />
  64. 64. Example of Test Case and Test Steps<br />
  65. 65. Sharepoint Link to UAT Naming Conventions<br />http://projectdocuments.compassbnk.com/platformupgrade/Core/Forms/AllItems.aspx?RootFolder=%2fplatformupgrade%2fCore%2fTest%20Coordination%2fR1%2fUAT%2fUAT%20%2d%20R1%20%2d%20UAT%20Tester%27s%20Area&View=%7b047D9B21%2dA186%2d40D5%2dB21F%2d406DD2C061CA%7d<br />

×