May be divided into more than test cases) Test Case #: 2.3 Test Case Name: Change PIN Page: 1 of 1 System: ATM Subsystem: PIN. Nov 19, 2013 In this software testing tutorial, I explain the importance of test case, what is a test case, inputs for writing test cases, test case syntax (test case format) like test case ID, test case steps. Test Case Example for Manual Testing Below given is an Example of a live project that demonstrates how all the above-listed tips and tricks are actually implemented. Note: Click on any image for an enlarged view. Test Scenarios Examples. Below is the list of test scenarios that are frequently asked in software testing interviews. In these test scenario examples, we are covering scenarios related to UI, functionality, non-functional requirements as well as negative test scenarios.
- Software Testing Dictionary
![Cases Cases](/uploads/1/2/6/2/126273004/642231452.jpg)
- Test case is a set of action which is execute to verify the feature or functionality of software application. In this video tutorial we will learn how to write test cases in manual testing with a.
- Test Scenarios Examples Below is the list of test scenarios that are frequently asked in software testing interviews. In these test scenario examples, we are covering scenarios related to UI, functionality, non-functional requirements as well as negative test scenarios.
- Selected Reading
Manual Test Case Writing
What is Test case?
A test case is a document, which has a set of test data, preconditions, expected results and postconditions, developed for a particular test scenario in order to verify compliance against a specific requirement.
Test Case acts as the starting point for the test execution, and after applying a set of input values, the application has a definitive outcome and leaves the system at some end point or also known as execution postcondition.
Typical Test Case Parameters:
- Test Case ID
- Test Scenario
- Test Case Description
- Test Steps
- Prerequisite
- Test Data
- Expected Result
- Test Parameters
- Actual Result
- Environment Information
- Comments
Example:
Let us say that we need to check an input field that can accept maximum of 10 characters.
Manual Test Case Writing Techniques
While developing the test cases for the above scenario, the test cases are documented the following way. In the below example, the first case is a pass scenario while the second case is a FAIL.
Scenario | Test Step | Expected Result | Actual Outcome |
---|---|---|---|
Verify that the input field that can accept maximum of 10 characters | Login to application and key in 10 characters | Application should be able to accept all 10 characters. | Application accepts all 10 characters. |
Verify that the input field that can accept maximum of 11 characters | Login to application and key in 11 characters | Application should NOT accept all 11 characters. | Application accepts all 10 characters. |
If the expected result doesn't match with the actual result, then we log a defect. The defect goes through the defect life cycle and the testers address the same after fix.
A good Test Case template maintains test artifact consistency for the test team and makes it easy for all stakeholders to understand the test cases. Writing test case in a standard format lessen the test effort and the error rate. Test cases format are more desirable in case if you are reviewing test case from experts.
![Manual Test Case Examples Manual Test Case Examples](/uploads/1/2/6/2/126273004/212101646.jpg)
The template chosen for your project depends on your test policy. Many organizations create test cases in Microsoft Excel while some in Microsoft Word. Some even use test management tools like HP ALM to document their test cases.
Click Below to download Test Case XLS
Irrespective of the test case documentation method chosen, any good test case template must have the following fields
Test Case Field | Description |
---|---|
Test case ID: |
|
Test Priority: |
|
Name of the Module: |
|
Test Designed by: |
|
Date of test designed: |
|
Test Executed by: |
|
Date of the Test Execution: |
|
Name or Test Title: |
|
Description/Summary of Test: |
|
Pre-condition: |
|
Dependencies: |
|
Test Steps: |
|
Test Data: |
|
Expected Results: |
|
Post-Condition: |
|
Actual Result: |
|
Status (Fail/Pass): |
|
Notes: |
|
Optionally you can have the following fields depending on the project requirements
- Link / Defect ID: Include the link for Defect or determine the defect number if test status is fail
- Keywords / Test Type: To determine tests based on test types this field can be used. Eg: Usability, functional, business rules, etc.
- Requirements: Requirements for which this test case is being written
- References / Attachments: It is useful for complicated test scenarios, give the actual path of the document or diagram
- Automation ( Yes/No): To track automation status when test cases are automated
- Custom Fields: Fields particular your project being tested due to client/project requirements.
Test Case Template
Click below to download Test Case Excel File
Click below to download Test Case Word File