SlideShare une entreprise Scribd logo
1  sur  21
Test CaseWriting August, 2011
From Requirements to Test Case Workflow  
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.
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
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
Test Cases Structure Example Test Cases:  Open a new consumer customer checking account ,[object Object]
Expected Result
Actual Result
Step 2 Description
Expected Result
Actual Result
Step 3 Description
Expected Result
Actual ResultOpen a new consumer customer savings account ,[object Object]
Expected Result
Actual Result
Step 2 Description
Expected Result
Actual Result
Step 3 Description
Expected Result

Contenu connexe

Tendances

Manual testing concepts course 1
Manual testing concepts course 1Manual testing concepts course 1
Manual testing concepts course 1Raghu Kiran
 
Test Management introduction
Test Management introductionTest Management introduction
Test Management introductionOana Feidi
 
TESTING LIFE CYCLE PPT
TESTING LIFE CYCLE PPTTESTING LIFE CYCLE PPT
TESTING LIFE CYCLE PPTsuhasreddy1
 
Software Testing 101
Software Testing 101Software Testing 101
Software Testing 101QA Hannah
 
Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)Leonard Fingerman
 
SOFTWARE TESTING UNIT-4
SOFTWARE TESTING UNIT-4  SOFTWARE TESTING UNIT-4
SOFTWARE TESTING UNIT-4 Mohammad Faizan
 
Why RTM (Requirement Traceability Matrix) is important in testing?
Why RTM (Requirement Traceability Matrix) is important in testing?Why RTM (Requirement Traceability Matrix) is important in testing?
Why RTM (Requirement Traceability Matrix) is important in testing?BugRaptors
 
Manual testing interview questions by infotech
Manual testing interview questions by infotech Manual testing interview questions by infotech
Manual testing interview questions by infotech suhasreddy1
 
Manual testing interview question by INFOTECH
Manual testing interview question by INFOTECHManual testing interview question by INFOTECH
Manual testing interview question by INFOTECHPravinsinh
 
Software Testing Process
Software Testing ProcessSoftware Testing Process
Software Testing Processguest1f2740
 
Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...
Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...
Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...Ankit Prajapati
 

Tendances (20)

Test case writing
Test case writingTest case writing
Test case writing
 
Test case development
Test case developmentTest case development
Test case development
 
Test cases
Test casesTest cases
Test cases
 
Effective Software Test Case Design Approach
Effective Software Test Case Design ApproachEffective Software Test Case Design Approach
Effective Software Test Case Design Approach
 
Manual testing concepts course 1
Manual testing concepts course 1Manual testing concepts course 1
Manual testing concepts course 1
 
Test Management introduction
Test Management introductionTest Management introduction
Test Management introduction
 
TESTING LIFE CYCLE PPT
TESTING LIFE CYCLE PPTTESTING LIFE CYCLE PPT
TESTING LIFE CYCLE PPT
 
Software test life cycle
Software test life cycleSoftware test life cycle
Software test life cycle
 
Software Testing 101
Software Testing 101Software Testing 101
Software Testing 101
 
Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)
 
Software Testing or Quality Assurance
Software Testing or Quality AssuranceSoftware Testing or Quality Assurance
Software Testing or Quality Assurance
 
SOFTWARE TESTING UNIT-4
SOFTWARE TESTING UNIT-4  SOFTWARE TESTING UNIT-4
SOFTWARE TESTING UNIT-4
 
Testing fundamentals
Testing fundamentalsTesting fundamentals
Testing fundamentals
 
Why RTM (Requirement Traceability Matrix) is important in testing?
Why RTM (Requirement Traceability Matrix) is important in testing?Why RTM (Requirement Traceability Matrix) is important in testing?
Why RTM (Requirement Traceability Matrix) is important in testing?
 
Manual testing interview questions by infotech
Manual testing interview questions by infotech Manual testing interview questions by infotech
Manual testing interview questions by infotech
 
Manual Testing.
Manual Testing.Manual Testing.
Manual Testing.
 
Stlc ppt
Stlc pptStlc ppt
Stlc ppt
 
Manual testing interview question by INFOTECH
Manual testing interview question by INFOTECHManual testing interview question by INFOTECH
Manual testing interview question by INFOTECH
 
Software Testing Process
Software Testing ProcessSoftware Testing Process
Software Testing Process
 
Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...
Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...
Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...
 

Similaire à Writing Test Cases 20110808

Testcase training
Testcase trainingTestcase training
Testcase trainingmedsherb
 
Essential information to be included in test cases
Essential information to be included in test casesEssential information to be included in test cases
Essential information to be included in test cases99tests
 
Software Testing-Dynamic testing technique-Mazenet solution
Software Testing-Dynamic testing technique-Mazenet solutionSoftware Testing-Dynamic testing technique-Mazenet solution
Software Testing-Dynamic testing technique-Mazenet solutionMazenetsolution
 
Best practices for test case creation & maintenance
Best practices for test case creation & maintenanceBest practices for test case creation & maintenance
Best practices for test case creation & maintenance99tests
 
Testcase definition
Testcase definitionTestcase definition
Testcase definitionOana Feidi
 
Less01 1 introduction_module
Less01 1 introduction_moduleLess01 1 introduction_module
Less01 1 introduction_moduleSuresh Mishra
 
Testing lab manual Testing lab manual sqa
Testing lab manual Testing lab manual sqaTesting lab manual Testing lab manual sqa
Testing lab manual Testing lab manual sqaMuhammadAdnan845624
 
ISTQB, ISEB Lecture Notes- 4
ISTQB, ISEB Lecture Notes- 4ISTQB, ISEB Lecture Notes- 4
ISTQB, ISEB Lecture Notes- 4onsoftwaretest
 
Test design techniques
Test design techniquesTest design techniques
Test design techniquesBipul Roy Bpl
 
Exam viewimportutilityuserguide ver 9
Exam viewimportutilityuserguide ver 9Exam viewimportutilityuserguide ver 9
Exam viewimportutilityuserguide ver 9William McIntosh
 
Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...
Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...
Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...KarenMiner
 
AJRA Test Strategy Discussion
AJRA Test Strategy DiscussionAJRA Test Strategy Discussion
AJRA Test Strategy Discussionajrhem
 
Importance of Software testing in SDLC and Agile
Importance of Software testing in SDLC and AgileImportance of Software testing in SDLC and Agile
Importance of Software testing in SDLC and AgileChandan Mishra
 

Similaire à Writing Test Cases 20110808 (20)

Testcase training
Testcase trainingTestcase training
Testcase training
 
Essential information to be included in test cases
Essential information to be included in test casesEssential information to be included in test cases
Essential information to be included in test cases
 
Software Testing-Dynamic testing technique-Mazenet solution
Software Testing-Dynamic testing technique-Mazenet solutionSoftware Testing-Dynamic testing technique-Mazenet solution
Software Testing-Dynamic testing technique-Mazenet solution
 
Best practices for test case creation & maintenance
Best practices for test case creation & maintenanceBest practices for test case creation & maintenance
Best practices for test case creation & maintenance
 
Lesson 2....PPT 1
Lesson 2....PPT 1Lesson 2....PPT 1
Lesson 2....PPT 1
 
CTFL Module 04
CTFL Module 04CTFL Module 04
CTFL Module 04
 
Testcase
TestcaseTestcase
Testcase
 
Testcase
TestcaseTestcase
Testcase
 
Testcase definition
Testcase definitionTestcase definition
Testcase definition
 
Less01 1 introduction_module
Less01 1 introduction_moduleLess01 1 introduction_module
Less01 1 introduction_module
 
Testing lab manual Testing lab manual sqa
Testing lab manual Testing lab manual sqaTesting lab manual Testing lab manual sqa
Testing lab manual Testing lab manual sqa
 
Black Box Testing
Black Box TestingBlack Box Testing
Black Box Testing
 
PEOPLESOFT PTF
PEOPLESOFT PTFPEOPLESOFT PTF
PEOPLESOFT PTF
 
ISTQB, ISEB Lecture Notes- 4
ISTQB, ISEB Lecture Notes- 4ISTQB, ISEB Lecture Notes- 4
ISTQB, ISEB Lecture Notes- 4
 
Test design techniques
Test design techniquesTest design techniques
Test design techniques
 
Test Driven
Test DrivenTest Driven
Test Driven
 
Exam viewimportutilityuserguide ver 9
Exam viewimportutilityuserguide ver 9Exam viewimportutilityuserguide ver 9
Exam viewimportutilityuserguide ver 9
 
Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...
Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...
Solved Practice questions for Microsoft Querying Data with Transact-SQL 70-76...
 
AJRA Test Strategy Discussion
AJRA Test Strategy DiscussionAJRA Test Strategy Discussion
AJRA Test Strategy Discussion
 
Importance of Software testing in SDLC and Agile
Importance of Software testing in SDLC and AgileImportance of Software testing in SDLC and Agile
Importance of Software testing in SDLC and Agile
 

Writing Test Cases 20110808

  • 2. From Requirements to Test Case Workflow  
  • 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
  • 6.
  • 14.
  • 22.
  • 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….
  • 27.
  • 28. Type = Use an abbreviation of the type of transaction that allows you to best identify the Test Scenario
  • 29. Test Scenario Number – Incremental Number
  • 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
  • 33. Test Scenario Number – Incremental Number
  • 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
  • 37. Test Case Template Test Case Template
  • 38. Test Case Template Column Definitions These are the definitions for each column: Test Case Template
  • 39.
  • 40. Subject (cell A) - can be left blank
  • 41. Test Name - can not exceed 40 characters
  • 42. Test Name - can not have any unique characters such as , : ; ‘ < () / ^ " *
  • 43. Test Name - can have an underscore or a period (_ . ) along with numbers and letters
  • 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. Test Attributes - for UAT test cases must say “User Acceptance Test”
  • 46. Test priority - must be either A (high), B (medium) or C (low)
  • 47. Requirement ID - should only list the most applicable requirements
  • 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)
  • 59. Requirement ID – only one ID is accepted, remove all others
  • 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. Remove Blank rows between tests (they will not be accepted by ALM) Manually add/remove any blank rows
  • 63.
  • 64. Example of Test Case and Test Steps
  • 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