Formats for test cases can differ depending on the company. Setting up a testing procedure for your project is one step closer, though, if you write test cases using a consistent structure.
Additionally, it reduces ad hoc testing, which is carried performed without enough test case documentation. However, even with standard templates, you still need to employ manual methods for the creation of test cases, their review and approval, test execution, and—most importantly—the preparation of test reports.
Also, if you have a process to review the test cases by the business team, then you must format these test cases in a template that is agreed by both the parties.
Recommended Tools
Before continuing with the Test case writing process, we recommend downloading these Test case management tools. This will ease your test plan and test case writing process mentioned in this tutorial.
#1) Katalon Platform
There is more to Katalon Platform than merely a tool for managing test cases. With its user-friendly features, you can quickly and easily automate your desktop, mobile, API, and online tests without writing a ton of code.
An extensive collection of project templates, a keyword library to automate any task, innovative test frameworks, and even artificial intelligence (AI) tools to assist you in creating code from plain text inputs are all at your fingertips right away! When combined, they reduce the length of your testing process.
For managing test cases? Katalon TestOps is there with friendly UI/UX best practices in mind. Katalon automatically updates your test results in the system as soon as a test is completed successfully. These results will later be consolidated into insightful reports on which you can base your decisions.
Test case management is deeply integrated across all stages of the testing process. Right at the beginning of test case creation, you can already create and assign custom tags to help with categorization. You can also share test artifacts (including test cases, objects, profiles, and custom keywords) across teams.
In other words, Katalon is an automation testing tool for all AUTs merged with a test case management tool, a cross-browser execution tool, and a reporting tool.
#2) Testiny
A brand-new, simple test management solution is called Testiny. Built on the newest technologies, this rapidly expanding web application seeks to simplify manual testing and QA management. Its incredibly user-friendly architecture facilitates the construction and upkeep of test cases and enables testers to conduct tests without introducing cumbersome overhead.
Don’t just take our word for it, take a look at Testiny yourself.
Testiny is perfect for small to mid-sized QA teams looking to integrate manual and automated testing into their development process.
Features:
- Intuitive and simple out of the box
- Write test cases using a rich-text editor, copy & paste screenshots, drag & drop to move items
- Choose between different test case templates; add your own custom fields to fit it to your needs
- Organize tests in a tree-structure for better maintenance; easily search and filter for tests
- Manage test cases in test plans and test runs
- Powerful integrations (e.g. Jira, GitLab, Azure DevOps) for llinking requirements and defects
- Instant updates – all browser sessions stay in sync.
- Immediately see if a colleague made changes, completed a test, etc.
- Powerful REST API, SSO, audit logs.
Free for open-source projects and small teams with up to 3 people.
Here is how to make the manual test case management process a bit easier with the help of simple testing templates.
Note:I’ve indicated the most fields that are relevant to the test case. Nonetheless, it is recommended that you use only the fields that your team uses. Additionally, feel free to include any fields that your team uses that aren’t on this list in your personalized template.
Standard Fields for a Sample Test Case Template
There are certain standard fields that need to be considered while preparing a Test case template.
Several standard fields for a sample Test Case template are listed below.
Test case ID: Unique ID is required for each test case. Follow some conventions to indicate the types of the test. For Example, ‘TC_UI_1’ indicating ‘user interface test case #1’.
Test priority (Low/Medium/High): This is really helpful for doing tests. While small user interface cases may have a low priority, business rules and functional test cases may have a medium or higher test priority. The reviewer should always determine the priority for testing.
Module Name: Mention the name of the main module or the sub-module.
Test Designed By Name of the Tester.
Test Designed Date: Date when it was written.
Test Executed By Name of the Tester who executed this test. To be filled only after test execution.
Test Execution Date: Date when the test was executed.
Test Title/Name: Test case title. For example, verify the login page with a valid username and password.
Test Summary/Description: Describe the test objective in brief.
Pre-conditions: Any prerequisite that must be fulfilled before the execution of this test case. List all the pre-conditions in order to execute this test case successfully.
Dependencies: Mention any dependencies on other test cases or test requirements.
Test Steps: List all the test execution steps in detail. Write test steps in the order in which they should be executed. Make sure to provide as many details as you can.
Pro Tip: In order to manage a test case efficiently with a lesser number of fields, use this field to describe the test conditions, test data and user roles for running the test.
Test Data: Use of test data as an input for this test case. You can provide different data sets with exact values to be used as an input.
Expected Result: What should be the system output after test execution? Describe the expected result in detail including the message/error that should be displayed on the screen.
Post-condition: What should be the state of the system after executing this test case?
Actual result: The actual test result should be filled after test execution. Describe the system behavior after test execution.
Status (Pass/Fail): If the actual result is not as per the expected result, then mark this test as failed. Otherwise, update it as passed.
Notes/Comments/Questions: If there are any special conditions to support the above fields, which can’t be described above or if there are any questions related to expected or actual results then mention them here.
Add the following fields if necessary:
Defect ID/Link: If the test status fails, then include the link to the defect log or mention the defect number.
Test Type/Keywords: This field can be used to classify tests based on test types. For Example, functional, usability, business rules, etc.
Requirements: Requirements for which this test case is being written for. Preferably the exact section number in the requirement doc.
Attachments/References: This field is useful for complex test scenarios in order to explain the test steps or expected results using a Visio diagram as a reference. Provide a link or location to the actual path of the diagram or document.
Automation? (Yes/No): Whether this test case is automated or not. It is useful to track automation status when test cases are automated.
With the help of the above fields, I’ve prepared an example test case template for your reference.
Download Test Case Template with Example (Format #1)
Also, here you can refer to a few more articles on writing effective test cases. Use these test writing guidelines and the above template to write and manage the test cases effectively on your project.
Sample Test Cases:
Tutorial #1: 180+ Sample Test Cases for Web and Desktop Applications
One More Test Case Format (#2)
Without a doubt, the test cases will vary based on the program functionality for which they are designed. Nevertheless, you may always utilize the template provided below to record the test cases without worrying about what your application is actually doing.
Sample Test Cases
Based on the above template, below is an example that showcases the concept in a much understandable way.
Let’s assume that you are testing the login functionality of any web application, say Facebook.
Below are the Test Cases for the same:
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 implemented.
Conclusion
A test case management tool is what I personally like to utilize. An open-source tool is a good place to start. In addition to saving you a great deal of time compared to manually maintaining these papers, it will be a nice addition to your efforts to set up the testing process.
Additionally, test case templates and a few examples with excellent documentation have been shown to us. I hope you found this essay useful.
YOU MAY BE INTERESTED IN
The Art of Software Testing: Beyond the Basics
Automation testing course in Pune