3. Definition – Test Case What is a Test Case? Definition 1 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. Definition 2 Test cases are specific inputs and procedures that you will follow when you test software. Analogy A Test Case is like a recipe. You follow the steps to produce an end result.
4. Basic Parts of a Test Case A Test Case is multiple Steps which are comprised of these 4 basics parts: Description of the Test Case Verify that the text is blue. Description of each Step Locate text in first paragraph Expected result each Step The text should be blue Actual result each Step The text is blue
5. Test Step 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: Usually start with a verb such as: Verify, Validate, Navigate Usually are doing something very discrete. Validate color, Verify SSN, Navigate to account Examples: Step 1. Navigate to SSN field. Step 2. Enter a valid ID. Step 3. Validate that the SSN field will only accept a 9 digit number
23. Best Practices When writing: Avoid lingo (words, abbreviations, acronyms and phrases used in your department or field) The customer will be using ABF financing. The customer will be using Asset Based Financing. Write the case as if you are not going to be executing it. Report should look like Bettys report. Output should be TPS 123 report. Write Test Cases so they Test a limited set of functionality. Verify that all Deposits work in Alnova. Execute a deposit in Alnova.
24. Example Test Case with Steps For existing consumer and commercial accounts, add an alternative contact address for a statement address using this mailing address: 123 Maple Street, Birmingham, AL Test Case: Open an existing consumer account: Test Step 1. In business object, enter last name of customer Test Step 2. Choose Add an Address Test Step 3. Enter 123 Maple Street Test Step 4. Etc….
30. Description – Brief description of the event that you are testing Example RET_CONSREG_001_Register a Customer This means Retail Department – Registering a Consumer – Incremental number - Scenario Description * 001 is the scenario number and is the number used in the Test Case naming convention
31.
32. Type = Use an abbreviation of the type of transaction that allows you to best identify the Test Scenario
34. Test Case Number – Incremental Number (May have multiple Test Cases per Test Scenario)
35. Description – Brief description of the event that you are testingExample CM_NCONMAINT_001_002_Register a Customer This means Commercial Department – Non-Consumer Maintenance – Test Scenario number– Test Case Number – Test Case Description
36. Scenario Applied to Test Cases How Scenarios Can be Used for Your Test Cases
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. Remove Blank rows between tests (they will not be accepted by ALM)*Pre-Requisites = items (non-data) required to perform the test such as hardware, environment needs, batches (example: ATM cards) *Test Data = data required to perform the test (example: valid account information)
51.
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. Test Name - can not exceed 40 characters - Manually correct
54. Description - can not have any unique characters such as , : ; ‘ < () / ^ " * Manually remove any unique characters before uploading
55. Description - can have an underscore or a period (_ . ) along with numbers and letters
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. Test Attributes - for UAT test cases must say “User Acceptance Test”
58. Test priority - must be either A (high), B (medium) or C (low)
65. Sharepoint Link to UAT Naming Conventions 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
