Chuyển tới nội dung
Home » Test Case Example Excel | How To Write A Test Case In Manual Testing?

Test Case Example Excel | How To Write A Test Case In Manual Testing?

Software testing using excel - How to build test cases

How ProjectManager Helps With Test Cases and More

The test case template is a fine tool, but as we’ve shown above with the kanban board feature of our software, it can certainly be improved upon. But that’s only one thing that project management software can do to facilitate your test cases. The kanban board might not be your ideal tool to use, which is why we have multiple project views for you to work how you want to work. Besides flexibility, we also have mobile accessibility and features that integrate with third-party apps so you can do it all from one platform.

Use Multiple Project Views to Plan and Execute IT Projects

Test cases can be executed on kanban boards, but you might want to collect your requirements on our task list. Our unlimited file storage means you can have all your project documentation in one place that can be accessed anywhere and at any time. The test case is part of a larger project, which can be scheduled on our powerful Gantt charts, which link all four types of dependencies, filter for the critical path and can set a baseline to capture that plan and compare it to your actual progress in real time to help you stay on track.

Monitor Progress With Real-Time Dashboards and Reports

Whether you’re working on one project or multiple projects you need to have quick, real-time access to data to track implementation timelines and then present progress reports to executives. Our real-time dashboards automatically collect live data and deliver it as easy-to-read graphs and charts on cost, time, workload and more, for one project or a portfolio. Unlike lightweight tools that require a lot of training and setup, our dashboard is ready when you need it. Plus, our customizable reports help you get more detail and also filter presentations for executives to show them the data they’re interested in.

Why You Need a Test Case Template

The point of a test case is to be methodical and not haphazard when testing a feature or a software product. This provides a more thorough test of the feature or software product and avoids missing possibly crucial scenarios that will damage the release. The last thing software engineers want is for the end user to have a software product that’s full of bugs.

The test case is a tool that developers and testers use to discover errors that might have happened as the software was being developed. There could also be defects that were missed. The test case, then, is a way to carefully check every aspect of the software to ensure that it’s working as planned. This is an important step before releasing the software to the public.

By using our free test case template for Excel, developers and testers are more likely to have good test coverage and reduced maintenance and software support costs. Our test case template codifies the process to ensure that you don’t miss any steps. It also creates a paper trail of test case documentation that can be archived and used as historical data to help when working on similar projects.

Test case templates, though, will only get you so far. Project management software gives you more control over the process. ProjectManager is award-winning project management software that has kanban boards that mimic the test case template. Our customizable kanban columns can define each of the test case steps, while the kanban cards can be test case scenarios. You can attach unlimited files to each task to have all the software documentation at your fingertips while managing the test case process. Get started with ProjectManager today for free.

Software testing using excel - How to build test cases
Software testing using excel – How to build test cases

What Is a Test Case Document?

A test case document is a set of steps that a team can execute to test certain scenarios based on the needs of the function, from clinical trials to software updates and even project management changes. Each test case includes a set of preconditions as well as test data, expected results, actual results, and post-conditions that help determine the success or failure of a test.

All steps of a test case are meant to check the functionality and applicability of each test, based on the preconditions and expected results. A test case is considered the smallest unit of a testing plan and contributes to the overall test script or user story.

To begin a test case, one must first describe the actions and parameters they mean to achieve, verify, or challenge regarding any expected behavior of a test. There are sets of conditions and variables that the tester uses to determine the quality and success of a system, trial, feature, or software, and the end results can confirm these facts.

What is a Test Case?

A test case is a specific scenario designed to verify the functionality and reliability of a software system. In the test case, testers outline the specific steps to be taken, the input data to be used, and the expected outcomes to determine if the software behaves as intended.

Test cases are typically documented in a dedicated testing document (such as Google Sheets, or text document) or a test case management tool (TestRail, Zephyr, qTest, and PractiTest). For automated testing, test cases can be written directly within code files using programming languages and testing frameworks.

Read More: What is a Test Plan? Test Plan vs. Test Strategy

How To Write TEST CASES In Manual Testing | Software Testing
How To Write TEST CASES In Manual Testing | Software Testing

What is a Test Case?

A test case template is a document that comes under one of the test artifacts, which allows testers to develop the test cases for a particular test scenario in order to verify whether the features of an application are working as intended or not. Test cases are the set of positive and negative executable steps of a test scenario which has a set of pre-conditions, test data, expected results, post-conditions, and actual results.

Most of the companies are using test case management tools such as Quality Center (HP QC), JIRA, etc., and some of the companies still using excel sheets to write test cases.

Check the below video to watch “How To Write Test Cases Manually”

How To Write a Test Case in Manual Testing?

Manual testing, as its name suggests, is all about executing test cases manually, with no help from automation testing tools or scripts. Testers also have to consider all of the components of the test cases mentioned above, then build a spreadsheet to document all of that.

Read More: Manual Testing vs Automation Testing: A Full Comparison

How to Write Test Cases in Manual Testing with Template
How to Write Test Cases in Manual Testing with Template

Conclusion

The role of testing in website design cannot be overemphasized. If a company rolls out a website with insufficient testing, the results could be catastrophic for their consumer relations.

Good test cases are to ensure your website is bug-free and works as the user expects.

BugHerd’s bug tracking tool can simplify testing execution by integrating with just about any test management tool out there and enabling a point-and-click process that is far simpler than any other method.

Try it out for free with our 14-day trial.

Test Case Template with Examples: Free Excel & Word Sample for Download

Having a good test case template comes with tons of benefits. Not having to re-invent the wheel is one of them. Drawing from years of experience in the software testing industry, we have created a detailed template for you to note down your test case in the most organized manner, so that you can dedicate your time and effort to other high-value tasks. Scroll down and download your template, and if you want to get some tips on how to best write a test case, read on, we got you covered!

What is a test case?

In order to get the best out of a product at the end of its production phase, you will need to make sure that it is bug-free. You can do that by hiring a tester and giving him a test case, but what is a test case exactly?

The easiest way to understand it is with the help of its dictionary meaning. “A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies the requirements or works correctly.”When it is worded like that, it’s simple, isn’t it?

There is no need to worry, creating a test case or a template for it is nothing overcomplicated. For now, all you need to know is that essentially, this is a process where the tester gets in contact with a system and with the help of preset conditions, he tests the system and confirms the end result.

You may have noticed that this sounds a lot like a scientific method and we have to say that it is pretty similar in comparison. A test case, may in the end, be a scientific method not only for detecting bugs but for creating a hypothesis on how to remove them. Here are some examples of steps that a person could test:

  • Confirm login functionality when entering valid username and password
  • Test results when entering a valid username but invalid password
  • Check results when the username field is filled by password field is empty

As you can see, if you’re writing a code for a website and you need to test some basic functions of it like the login page, the first things a tester would do is check out if the signing in functions works. You may have noticed that these test case examples are very specific, you will see in the following sections that a test case needs to be exactly like that. Some tests may end up being vague, but in most cases, a tester will need to check a specific thing.

Test Case Formatting : Excel Feature that Every tester must know - Part 1
Test Case Formatting : Excel Feature that Every tester must know – Part 1

What Is the Purpose of a Test Case?

A test case can help you easily identify any problems, unplanned issues, or missed details in a project, update, or trial. Additionally, test cases provide the following benefits for the individuals or teams who carry them out:

  • Minimize ad-hoc testing
  • Make manual test case management easier and more streamlined
  • Save valuable time when testing and analyzing results
  • Enable testers to develop individual test cases for specific scenarios
  • Verify the success of updates or changes
  • Make it easier to share results with stakeholders and gain buy-in from all involved parties
  • Lessen the effort and error rate involved in testing
  • Define and flesh out all positive and negative test results or behavior
  • Divide tests into positive and negative segments
  • Eliminate the number of bugs or errors in an end product
  • Communicate all specific conditions from the start in order to eliminate confusion
  • Keep management updated on the quality status of a test
  • Help testers generate detailed summaries and reports on test status, defects, bugs, etc.
  • Track productivity and trace all problems back to the source
  • Help testers write and report on more comprehensive test case results

What Is A Test Case?

A test case is a list of instructions for specific actions to ensure the website functions as expected.

Its purpose is to provide direction to software testing engineers to verify that each website component is bug-free.

One website design could require hundreds of test cases. These test cases are grouped and organized in what is considered the test suite as part of the overall test plan.

Typically, designers can create test cases. But if the test case design is complex, testing engineers may also be involved in test case writing.

Functional testing has three different types of test cases, and their differences concern input versus outcome.

Positive Test Case

A positive test case is when the inputs produce a positive outcome.

For example, when testing login functionality, a positive test case would result in the arrival of the welcome page when clicking on the login button and entering the correct credentials.

Negative Test Case

In a negative test case, the purpose is to test the results of a negative outcome.

For the same example, a negative test case would involve the user experience clicking on the login button and entering the wrong credentials.

This negative test case will be successful if the wrong credentials result in a notification that the password was entered incorrectly.

Destructive Test Case

Destructive test cases are meant to test how much load a webpage can handle.

Destructive tests may include applying a heavier load than normal, fast-clicking, or implying malicious intent.

Test case Template   Excel 2023 03 27 15 58 06 Test Case Design Techniques, how to create test cases
Test case Template Excel 2023 03 27 15 58 06 Test Case Design Techniques, how to create test cases

Should you use software for managing your test cases?

Test case management tools are important for the inexperienced as they help you both with maintaining and managing your test case examples. Some of the notable parts of these tools are the following:

  • They help you with documenting current test cases
  • You can execute current test cases and record the results instantly
  • Defect tracking is automated as the failed tests are instantly recorded in the bug tracker, the software may even notify the developer of this
  • Protects your test cases from being lost or corrupted

Although it isn’t entirely necessary for you to buy or use a free software for keeping your test cases safe and automatically managed, it can really help those who are inexperienced or those who create a lot of cases. If you don’t want to waste money on buying these test case managers, you can always try to do everything alone and see if you’re up to the task.

Test Case Template for Word

Click below to download Test Case Word File

Download the above Test Case Template(.docx)

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: Each test case should be represented by a unique ID. To indicate test types follow some convention like “TC_UI_1” indicating “User Interface Test Case#1.”
Test Priority: It is useful while executing the test.
Name of the Module: Determine the name of the main module or sub-module being tested
Test Designed by: Tester’s Name
Date of test designed: Date when test was designed
Test Executed by: Who executed the test- tester
Date of the Test Execution: Date when test needs to be executed
Name or Test Title: Title of the test case
Description/Summary of Test: Determine the summary or test purpose in brief
Pre-condition: Any requirement that needs to be done before execution of this test case. To execute this test case list all pre-conditions
Dependencies: Determine any dependencies on test requirements or other test cases
Test Steps: Mention all the test steps in detail and write in the order in which it requires to be executed. While writing test steps ensure that you provide as much detail as you can
Test Data: Use of Test Data as an input for the test case. Deliver different data sets with precise values to be used as an input
Expected Results: Mention the expected result including error or message that should appear on screen
Post-Condition: What would be the state of the system after running the test case?
Actual Result: After test execution, actual test result should be filled
Status (Fail/Pass): Mark this field as failed, if actual result is not as per the estimated result
Notes: If there are some special condition which is left in above field

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.
Software Testing Tutorial #32 - How to Write Test Cases
Software Testing Tutorial #32 – How to Write Test Cases

Test Case Components

No matter what method to document the test case was chosen, we should include the following fields in the test case:

  1. Test Case ID: A unique identifier for the test case.
  2. Title/Description: A concise description of the purpose of the test case.
  3. Test Objective: The specific goal or objective of the test.
  4. Preconditions: Any necessary conditions that must be met before the test is executed.
  5. Test Steps: A step-by-step sequence of actions to perform during the test.
  6. Input Data: The data or parameters to be used as input for the test.
  7. Expected Results: The anticipated outcomes or behaviors after executing the test steps.
  8. Actual Results: The actual outcomes observed when executing the test.
  9. Test Environment: Details about the system, hardware, software, and configurations used for testing.
  10. Test Data Preparation: Instructions on how to set up the required test data.
  11. Test Execution Date: The date and time when the test was executed.
  12. Test Execution Status: The pass/fail status of the test case after execution.
  13. Test Conclusion: A summary of the results and observations of the test.
  14. Test Verdict: A judgment about the overall success of the test.
  15. Bug Details (optional): If a defect is identified, details about the issue, its severity, and steps to reproduce it. Generally teams will manage the bugs found in another dashboard, but if you want to link the bug found to a specific test case, you can totally include this field there
  16. Attachments: Any relevant files, screenshots, or documentation associated with the test.
  17. Test Case Author: The person responsible for creating the test case.
  18. Test Case Reviewer: The person who reviewed and approved the test case.
  19. Test Case Version: The version or revision number of the test case.
  20. Notes/Comments: Additional information, insights, or comments related to the test case.

If you want to go all in, you can even classify the bug by its stages in the bug life cycle or its severity. Make sure to tweak the test case to include only the information you need for the project.

What is a Test Case Template?

Most organizations want to maintain uniformity across different projects, be it during the development phase or the testing phase.

In order to follow a uniform testing process, a test case template is defined which is nothing but a template that contains the different fields that the test cases should have.

Now, we will see the different fields of a test case – both mandatory as well optional.

TestCaseId

This field uniquely identifies a test case. It is mapped with automation scripts(if any) to keep track of automation status. The same field can be used for mapping with the test scenarios for generating a traceability matrix. E.g. – GoogleSearch_1

Component/Module

This field specifies the specific component or module that the test case belongs to. E.g. – Search_Bar_Module.

Priority

This field is used to specify the priority of the test case. Normally the conventional followed for specifying the priority is either High/Medium/Low or P0/P1/P2/P3, etc with P0 being the most critical.

Description

In this field describe the test case in brief. E.g. – Verify that when a user writes a search term and presses enter, search results should be displayed.

Pre-requisites

In this field specify the conditions or steps that must be followed before the test steps execution e.g. – “Browser is launched”.

Test Steps

In this field, we mention each and every step for performing the test case. The test steps should be clear and unambiguous e.g.-

  • Write the URL – https://google.com in the browser’s URL bar and press enter.
  • Once google.com is launched, write the search term – “Apple” in the Google search bar.
  • Press enter and observe the search results.

Test Data

In this field, we specify the test data used in the test steps. E.g. in the above test step example, we could use the search term-“apple” as test data.

Expected Result

This step marks the expected result after the test step execution. This is used to assert the test case. E.g. search results related to ‘apple’ should be displayed.

Actual Result

In this step, we specify the actual result after the test step execution. E.g. – search results with the ‘apple’ keyword were displayed.

Status/Test Result

In this step, we mark the test case as pass or fail based on the expected and actual results. Possible values can be – Pass, Fail, or Not executed.

Test Executed by

In this field, we specify the tester’s name who executed the test case and marked the test case as pass or fail.

Apart from these mandatory fields, there are many optional fields that can be added as the organization or application needs like-

  • Automation status – For marking if a test case is automated or not.
  • TestScenarioId – For a mapping test case with its test scenario.
  • AfterTest step – For specifying any step required to be executed after performing the test case.
  • TestType – To specify if the test comes under any specific testing category like regression, sanity, smoke, etc.
Test Case Template for Excel (Step by Step Guide)
Test Case Template for Excel (Step by Step Guide)

Test Cases Example

Let’s take an example to write a Test cases example for a web application. They will be around Login, logout functionality test cases, and other functionality-related test cases. UI and performance-related test cases will also be part of test cases. With the different number of browsers these days, it is very important to test the web application on different browsers with different versions. Hence compatibility test cases are also very important.

Test Case ID Test Case Description Test Data Test Steps Expected Test Result Actual Test Result Status Pass/Fail
TC_01 Verify whether a user is able to login with valid username and password Username : ABCDEFG

Password: 123456

1. Open URL : {website homepageurl}

2. Click on Login button from header and navigate to login page

3. Enter registered user’s username in the username field

4. Enter valid password

5. Click on Login button

User should be logged in gracefully Same as Expected Pass
TC_02 Verify whether it allows user to login with a valid username and an invalid password. Username : ABCDEFG

Password: 1233333

1. Open URL : {website homepageurl}

2. Click on Login button from header and navigate to login page

3. Enter registered user’s username in the username field

4. Enter invalid/incorrect password

5. Click on Login button

1. It should not allow user tologin

2. It should display validation message for invalid credentials

3. Incorrect input filed should get highlighted with different color

Same as expected Pass
TC_03 Verify the login page when the fields are blank and Submit button is clicked. N/A 1. Open URL : {website homepageurl}

2. Click on Login button from header and navigate to login page

3. Click on Login button

1. It should not allow user tologin

2. Validation message should be display to enter credentials

3. Username and Password field should get highlighted with different color

Same as expected Pass

Test Case Point Estimate Template

Download Test Case Point Estimate Template

Assess the approach needed to test software, determine testing checkpoints and preconditions, and analyze all test results with this comprehensive test case point estimate template. Use this template to rate priorities and complexities based on a high-to-low measure, allocate testing time for each specific step, and determine the amount of work associated with each test.

How to write test case in excel | How to write test cases for Linkdin Login page in manual testing
How to write test case in excel | How to write test cases for Linkdin Login page in manual testing

What Are the Components of a Test Case?

A test case is comprised of many different components: It assesses what is being tested, the expected results of a test, and the process involved in testing each specified element of a case.

In general, test cases should include the following:

  • Test Process: This includes the test review and approval, the test execution plan, the test report process, use cases (if applicable), and performance risks.
  • Positive and Negative Tests: Positive tests should help check whether the functionality is performing correctly, while negative tests should check every reverse situation where an error or issue could occur.
  • Test Case ID: This helps you correctly and uniformly document each test case and its corresponding results; it also helps you avoid retesting the same things.
  • Test Scenario: This includes all the information about a test in the form of specific, detailed objectives that will help a tester perform a test accurately. It will not, however, include specific steps or sequences.
  • Test Steps: The steps should tell a tester, in detail, exactly what they should do during each step, including specific objectives.
  • Test Data: This section includes all the information and data that a test collects throughout the duration of the process.
  • Expected Results: This includes any detailed and precise information or data that a tester should expect to see and gather from a test.
  • Actual Results: This includes all positive and negative results that you receive from a test and that help you confirm or reject the expected results and detect any issues or bugs.
  • Confirmation: This is the part of the process during which testers discuss and review whether or not a test was a success or a failure, based on the results.

How To Write Test Cases in Manual Testing

Follow the below steps to write the test cases.

Step #1 – Test Case ID:

Each test case should be represented by a unique ID. It’s good practice to follow some naming convention for better understanding and discrimination purposes.

Step #2 – Test Case Description:

Pick test cases properly from the test scenarios

Example:

Test scenario: Verify the login of GmailTest case: Enter a valid username and valid password

Step #3 – Pre-Conditions:

Conditions that need to meet before executing the test case. Mention if any preconditions are available.

Example: Need a valid Gmail account to do login

Step #4 – Test Steps:

To execute test cases, you need to perform some actions. So write proper test steps. Mention all the test steps in detail and in the order how it could be executed from the end-user’s perspective.

Example:

  • Enter Username
  • Enter Password
  • Click Login button

Step #5 – Test Data:

You need proper test data to execute the test steps. So gather appropriate test data. The data which could be used an input for the test cases.

Example:

Step #6 – Expected Result:

The result which we expect once the test cases were executed. It might be anything such as Home Page, Relevant screen, Error message, etc.,

Example: Successful login

Step #7 – Post Condition:

Conditions that need to achieve when the test case was successfully executed.

Example: Gmail inbox is shown

Step #8 – Actual Result:

The result which system shows once the test case was executed. Capture the result after the execution. Based on this result and the expected result, we set the status of the test case.

Example: Redirected to Gmail inbox

Step #9 – Status:

Finally set the status as Pass or Fail based on the expected result against the actual result. If the actual and expected results are the same, mention it as Passed. Else make it as Failed. If a test fails, it has to go through the bug life cycle to be fixed.

Example:

Result: Pass

Other important fields of a test case template:

Project Name: Name of the project the test cases belong to

Module Name: Name of the module the test cases belong to

Reference Document: Mention the path of the reference documents (if any such as Requirement Document, Test Plan, Test Scenarios, etc.,)

Created By: Name of the Tester who created the test cases

Date of Creation: When the test cases were created

Reviewed By: Name of the Tester who created the test cases

Date of Review: When the test cases were reviewed

Executed By: Name of the Tester who executed the test case

Date of Execution: When the test case was executed

Comments: Include value information which helps the team

How to write test case in excel | How to write test cases in manual testing with example
How to write test case in excel | How to write test cases in manual testing with example

What does a test case template consist of?

This will depend most of the times on the software that is being tested and on the number of requirements that the tester should fill out, but in the end, all test case templates are generally similar. If you’re making a template, make sure that it includes the following:

  • Test Case ID
  • Test Scenario
  • Test Steps
  • Test Data
  • Results Expected
  • Results Received
  • Confirmation

Before actually getting into the details of each step and part of the template, you need to know what a good test case should be about. When a tester gets in contact with the system you created, he should only resort to testing out specific parts of the system. In order to avoid any confusion or wasted hours because you didn’t tell the tester exactly what he/she should do, try to avoid any vague objectives.

For a better perspective, avoid giving your tester vague objectives like “Test login functionality of the page”, “Confirm that the program fulfills its target mission” and so on. Instead of that, try telling him exactly what he should do as well as variants of it. Variants are important because they can help with getting rid of hidden bugs. An example would be to test a login page with both valid and invalid data. Now let’s talk about the parts of a test case template.

Test Case ID

A test case ID is important because you will be able to document your results with ease. Not only will you document it, you will also be able to avoid testing the same things over and over again. An ID can be marked however you want, if you’re doing multiple systems you can start with the name with a short acronym of the programs name or even with the full name.

If you’re doing multiple tests, you can also put the objective of the test in the name of the template. Naming it like XXLoginPage01, where the XX stands for the acronym or full name of the software is a good example.

Test Scenario

The test scenario field will include all possible information about the testing. It won’t contain any sequences or steps of the testing phase, but it will contain a specific objective that the tester should keep in mind. This field could contain information like “Check admin login page with valid data”.

In order to make it easier for the tester, always try to keep this field as specific as possible. Don’t try to add anything vague or anything unnecessary to the testing that might confuse the tester. Try to avoid idioms as well so that the tester can do his job properly.

Test Steps

As we have already told you in the previous field, a test scenario should only include the information about the testing and exclude any steps. But the next field that you should have is the Test Steps field. With this area, you can tell the tester exactly what to do in steps and even add some prerequisites about the system.

Always try to include a large number of steps that have specific objectives. Don’t write steps that have too many words and don’t add commentary in this field. Here is what a test steps field should look like:

  1. Start up the software
  2. Head over to the registration area
  3. Insert data in all fields
  4. Submit the data by clicking register

See? It is plain and simple and contains all the info needed in concise short steps. Depending on how complicated the objective is, you may need to give the tester a few more steps, but always keep them short and specific.

Test Data

The test data field is entirely optional because it depends on the system the tester will use. If his objective demands any additional information that he needs to input in order to complete his objective, then you must have a field in which you will place that information.

If you’re following our login page examples, if for an objective where the tester needs to test its functionalities by placing the data and trying to log in, he will need that login information. If he is only limited to placing the username and password data, he will need that information in order to fulfill his objective.

Results Expected

This is the most important part because this field will explain the tester on what results he should expect, given that the system is bug-free. If the tester is trying to log into an account on the given software, the expected results could for an example say that he should end up logging into his account.

This could take a twist, perhaps the tester is given invalid data for the login fields, then naturally he should have expected that the website or software does not let him log into his account. Make sure that the expected results field should be precise as well and that it includes everything that the software is intended to do in that step.

Results Received

Once the tester fulfills all the test steps and inserts all the test data, he should now get the results of his testing. The results can be both positive and negative, they can either confirm that the program is working as intended or that it gives an entirely different result.

Although it is more preferred to have positive results, negative results will help you a lot by detecting that there is, in fact, a bug hidden in the code. For an example, if clicking a picture of a red button should convert its color into blue, then the results are as expected if that’s what the system is supposed to do. But if the color of the button stays the same or if it changes into yellow, then there is a problem that should be fixed.

Confirmation

A confirmation field is a lot similar to the Results Received field. While the Results Received field will just consist of the tester saying if he got the expected results, a confirmation field will just point out if the testing was a success or a fail.

With this, we don’t talk about the actual testing process failing or succeeding, we are talking about whether the system has or has not fulfilled its intended objective. This field could only consist out of the words pass or fail, but if you wish you can also tell the tester to write any comments about the process. You can also make the commentary into another field, but it is all up to you.

Conclusion

Personally, I prefer to use a Test Case Management tool. You can start with an open-source tool. It will be a good addition to your efforts to set up the testing process and meanwhile, it will also save a lot of time instead of manually maintaining these documents.

We have also seen test case templates and a few examples using very good, quality documentation. I hope this article was helpful to you.

We would be glad to know your thoughts, comments/suggestions about this article.

Over the course of the software development life cycle, a test case is one of the test artifacts that are given to the project’s stakeholders. It’s a way to see if the product or a feature of that software is working. Our free test case template allows you to evaluate various test scenarios.

Download our free test case template for Excel to thoroughly test your software and fix bugs before you release it to the public.

14-2-2024 | The Hindu Newspaper Analysis in English | #upsc #IAS #currentaffairs #editorialanalysis
14-2-2024 | The Hindu Newspaper Analysis in English | #upsc #IAS #currentaffairs #editorialanalysis

Information to include while drafting a test case

In the previous section, we have explained exactly out of what a test case template should consist of. We also mentioned which fields it has and what information those fields would include. Now we will mention some tips about drafting a test case, as well as some other information that you should include.

  • Test case should be specific and shouldn’t include more than 15 steps
  • Include any sort of proof or attachments
  • Add a description of what requirement is tested
  • Explain in detail how the system will be tested
  • Provide actions and expected results, as well as inputs and outputs
  • Make sure to use active case language

Another important thing is that the test setup of the tester should be compatible with the site or program, this is extremely important when it comes to testing out games or software that is demanding. For an example, perhaps the tester should test some parts of a demanding game, in this case, the setup of the tester should consist of a powerful PC that can handle it. If the PC isn’t powerful enough for the game, then it may interfere with the results of the testing. Make sure to include the following info for the test setup:

  • Version of the system that the tester is using
  • Operating system required for the software
  • Hardware requirements for the software
  • Include the software itself and any data files that are needed
  • Add prerequisites such as other tests

Things to do in order to write a good test case example

So far, we have talked about what a test case actually is, what a test case consists out of, and which information you should additionally provide to your tester. Now you will have a certain picture in mind before you start and write your own test case, but before you do that we recommend you to follow these tips:

Make it simple and transparent

When making a test case example, make sure that it is as simple as it can be. Never try to give the tester over complicated objectives that may need more than 15 steps and make sure that it is clear and easy to understand. Failing to do so will make you end up with a tester who can’t execute the steps.

Don’t use unnecessary words and don’t keep it casual, make sure to use assertive language that is concise; we have already placed examples of steps like these in the previous sections. If you make it simple, a tester will be able to execute the software faster.

Keep in mind the end user as well

A test case template should not only be easy to understand, it should also have objectives that ensure customer needs. When setting out the objective, make sure that it is something important, something that the end user will get in contact with and will certainly use.

A login page is a good example, if you’re creating a website or an internet forum that resolves around communities, you need to make sure that the future users can successfully register and login. For a good test case template, you should always think about the end user.

Avoid repeating the same tests

Once you have confirmed that the software created is bug-free in a specific area, you should not give your testers any more case tests for that area. Most of the time you will avoid repeating the same test cases by using a proper test ID.

Create an ID for the test you created and even place it as the filename. Keep in well documented and make sure that the objective of it is implicated in the name of the ID. This way you can save time by making test case templates for other objectives.

Confirm all software requirements

As difficult as it is to create software, another difficult thing is to make sure that the created software is compatible with most systems. If you already created the software and know that it can’t, for an example, work on operating systems older than Windows 7, you should include that in the test case template.

Place every single software requirement in the test case example you’re making so that the tester can execute his objective faster and so that the testing doesn’t get interfered by the wrong testing system. By doing this you will get precise results.

Make the ID easy to identify

If you’re making a test case example for an objective that needs several steps and prerequisites, make sure that all of your documents have IDs that are identified with ease. If you’re telling the tester to change the settings of his account on the system, he must be able to log into his account in the first place.

By placing an ID that can be identified easily, you can then search and correct the prerequisite by checking if the user can even log into his account. You can name it in any way you want, just make sure that you can know what it is about later.

Use testing techniques

Testing a system or a program is hard, not only that the testing needs to be taken care of, you also need to think of all the possible bugs that can occur, as well as the conditions that need to be made. With the help of a testing technique, you can get a few test cases that have the highest possibility of finding a bug in your software.

  • Equivalence Partition. This will partition the range into groups that have similar behavior
  • Error Guessing Technique. This method will guess the most probable error that may occur during testing, it relies on the experience of the tester
  • Boundary Value Analysis. This technique will help you define boundary testing for a specified range of values

Make it repeatable

Once your tester has made sure that the objective is completed and that the software works as intended, you should make sure that the same test can be repeated several times and that you get the same results. By making sure that you always get the same results, you will ensure that your software works.

In order to do this, you can get multiple testers to work on the same objective, you can even tell them to test it with both correct and incorrect data. By doing this, your program will always work no matter who uses it.

Get your test case designs reviewed

This is especially important if you’re just a beginner when it comes to writing a test case template, but know that this is important no matter how much experience you have. Getting your templates reviewed by your colleagues will help you get a template that is easily understood and works as intended.

Your colleagues can also help you discover any defects in your design or anything that you may have left out. So before sending your test case example to your tester, make sure to get it reviewed by colleagues and friends.

2024 Ford Endeavour / Everest is coming to India. Driving it in Nepal. Detailed walkaround video
2024 Ford Endeavour / Everest is coming to India. Driving it in Nepal. Detailed walkaround video

What is a Test Case Template?

A test case template is a predefined structure that provides a standardized way to document and create test cases. We have provided them as guidelines for testers to ensure that all necessary information about a test scenario is captured consistently across different test cases. With a good test case template, testing teams can maintain uniformity and improve the clarity and completeness of their test documentation.

Test Case vs Test Scenario

A test scenario is a broader concept than test case, referring to a high-level description of a particular functionality or feature of the software that needs to be tested.

A test scenario outlines the general conditions, goals, and boundaries within which a group of test cases will be executed, while test cases focus on the minute details of that test. In other words, test scenarios typically cover multiple test cases that collectively ensure comprehensive testing of a particular aspect of the software.

You can have a look at this table to have a more structured understanding of both concepts:

Aspect

Test Case

Test Scenario

Definition

Specific set of steps and expected results

High-level description of functionality

Focus

Tests a single aspect or condition

Encompasses multiple related test cases

Identification

Has a unique identifier (Test Case ID)

Often identified by a descriptive title

Purpose

Detailed verification of a small unit

Provides context for a group of test cases

Granularity

Very specific and focused

More general and covers broader functionality

Contents

Test steps, inputs, expected results, etc.

High-level description, related test cases

Reusability

May be reused in different scenarios

Often used as a reference for grouping

Coverage

Addresses one specific behavior/scenario

Covers multiple test scenarios

Example

Testing user login with invalid password

Testing the user registration process

NEW! Microsoft Excel Tricks & Tips for 2024 to maximise your productivity
NEW! Microsoft Excel Tricks & Tips for 2024 to maximise your productivity

What is a Test Case?

A test case is a specific scenario designed to verify the functionality and reliability of a software system. In the test case, testers outline the specific steps to be taken, the input data to be used, and the expected outcomes to determine if the software behaves as intended.

Test cases are typically documented in a dedicated testing document (such as Google Sheets, or text document) or a test case management tool (TestRail, Zephyr, qTest, and PractiTest). For automated testing, test cases can be written directly within code files using programming languages and testing frameworks.

Read More: What is a Test Plan? Test Plan vs. Test Strategy

Test Case Planning and Execution Template

Download Test Case Planning and Execution Template

Excel | Word | PDF | Smartsheet

With this complete test case planning and execution template, you can map out test plans for individual components of a project or trial, seamlessly execute tests, and analyze the data that comes from a test. You can also track tests by test ID and name, identify each step of a test, add priority levels and notes, and compare actual versus expected results. This complete testing template is compatible for all tests, from clinical trials to software updates.

Can You Pass This Excel Interview Test?
Can You Pass This Excel Interview Test?

SQL Server Integration Services Testing Test Case Template

Download SQL Server Integration Services Testing Test Case Template

Manage, test, and track all SQL server integration services with this detailed test case template. You can use this SQL test case template to ensure that all programming and data management systems are working correctly and test any updates or quick fixes.

Test Case Template Xls Free Download

Now you can download the test case template in Xls format. Along with the template, we have also provided a sample test case for your reference.

This completes our tutorial on the test case template. Feel free to use this template in your project and let me know in the comments if you have any questions.

How to Write Test Cases: Test Case Template With Examples

How to write test case
How to write test case

Test Case Use Cases

You can leverage test cases for a variety of purposes: to gain insight into how processes are performing; to determine how software updates are being used; and to figure out how business trials or tests are progressing.

Some of the most common use cases for test cases include the following:

  • Confirming login functionality on a username and password combination
  • Checking to see how the login function reacts to a valid or invalid username or password
  • Seeing what happens when someone inputs an empty response for either the username or password component

Numerous companies, such as HP Quality Center and Jira, use test cases to track and update their processes.

User Acceptance Testing Test Case Template

Download User Acceptance Testing Test Case Template

With this user acceptance testing (UAT) test case template, test newly designed software to ensure that it matches the designated specifications and meets all user-provided requirements. Track individual applications, the steps to execute them, and both the expected and actual results with this comprehensive testing template.

You’re using ChatGPT wrong
You’re using ChatGPT wrong

How to Write Test Cases in an Excel Sheet

For writing test cases in excel you need to make an excel sheet. There is no specific template for writing test cases that have 10 different columns – Test Case ID, Test Case Description, Assumptions, Test Data. Pre-Condition, Test Steps, Expected Result, Actual Result, Status, and Comments. Suppose you want to write a test case to test a login functionality.

Test Case ID: Test Case ID will be the test case number of story number in JIRA.

Test Case Description: The description will be a short description of the functionality.

Assumptions: Assumptions should be mentioned in the assumptions columns if any.

Test Data: Test Data is the data with which you are performing the testing.

Pre-condition: Pre-condition should be anything that is done before the execution of the test case.

Test Steps: In Test Steps, you must mention steps like Login to application, Enter Username, and password, click the login button, Verify the page redirects to splash page.

Expected Result: The expected Result should indicate the behavior of the application after the execution of the test case. For successful Login expected Result would be a redirection to the splash page.

Actual Result: The actual Result indicates the actual behaviour of the application on the execution of the test case.

Status: Status can be marked as passed or fail depending on the actual Result.

Comments: Last is the optional comments.

Download Test Case Template

A sample Test Case – Template for your reference.

Related posts:

  • How To Write Test Scenarios With Examples
  • Test Cases for Gmail
  • Test Cases for ATM
  • Test Cases for Login Page
  • Test Cases for Registration Page
  • Difference Between Test Scenario Vs Test Case
  • 20 Skills Of Highly Effective Software Tester

CHAPTERS

OVERVIEW

A test case template contains a series of test cases that are required to be tested by the QA team. These test cases can differ according to the organization. Test case template is made such that it can be easily understood by all members of the team.

It is a document that outlines the steps, inputs, and expected results for a specific test scenario. A test case template is used to plan and organize software testing efforts, ensuring that all necessary test cases are executed and that any defects are identified and tracked.

Each test case template contains a particular structure. This structure includes different fields for each test case. Some of the fields can be mandatory or optional.

Here you can see an image of a test case template that shows respective test cases along with their fields.

As an example let’s take into account different fields of the very first test case from the above test case template.

A test case template contains different test cases these come under different types of testing, like functional testing, performance testing, security testing, and acceptance testing. Each type of testing has its own unique set of test cases and requirements.

The organization also creates a test plan which contains the scope and approach of testing activities this further contains test suite. A test suite is a group based on functionality or features, which contains various test cases.

The organization can add various test cases according to their needs. When creating test cases, it’s also essential to consider the different roles and responsibilities of the testing team.

Test lead, test manager, test analyst, and test engineer are a part of testing team. They all play different roles like the test lead is responsible for overall testing efforts and ensures that the testing team has the resources and support it needs. The test manager manages test schedule and coordinates with other teams. The test analyst is responsible for creating and executing test cases. The test engineer is responsible for testing the application and identifying defects.

You will find different test cases based on various categories through our learning hub of test case template, as we are constantly updating new test case templates.

Template is a document which contains a list of different test cases according to different test scenarios like in relation to user, system, security and so on. The test case template helps testers to improve the communication, efficiency along with traceability within the organization.

Test case template as such has no fixed format as such but there are certain essential parameters that should be included in your test case template. These are Test ID, Test Description, Pre Condition, Expected Result, Actual Result, Post Condition, Pass/Fail, and Test Owner.

Test case checklist contains items or a catalog of test cases that are to be checked. This checklist allows us to identify & ensure that all relevant aspects of test case are covered. It helps us to improve the quality of test cases and prevent errors and omissions thus creating a effective testing strategy.

An Agile test case template is a standardised document used in Agile software development to specify the essential information for testing. It often comprises sections such as test case ID, description, test stages, expected results, actual results, and remarks. This template promotes efficient and uniform test case documentation in Agile projects.

To start creating a test case template in Excel, define column headers such as Test Case ID, Description, Test Steps, Expected Results, Actual Results, and Notes. Use Excel’s formatting features to improve readability and organization. Consider using conditional formatting to highlight test case status or specific criteria. You can also include formulas or data validation to automate calculations and guarantee data consistency. Save the file as a template for future usage, allowing for easy replication and customization for different testing conditions.

A test case is a detailed set of instructions and conditions designed to verify the functionality and quality of a software system. It includes inputs, expected outcomes, and steps to execute. For example, a test case could involve entering specific data into a form and confirming that the system correctly processes and displays the entered information.

To create a test plan, follow these steps: Define test objectives and scope. Identify test deliverables, Develop a test strategy, Create a test schedule, Define team roles and responsibilities, and obtain approvals, These steps ensure a comprehensive and structured test plan for successful testing.

Test case tools are software programmes or platforms that aid in the development, management, and execution of test cases. These technologies improve overall testing efficiency and effectiveness by offering capabilities such as test case generation, version control, test case reuse, reporting, and interaction with other testing and development tools.

Test case structure refers to the organization and components of a test case. It typically includes elements such as test case ID, description, preconditions, test steps, expected results, actual results, and status. A well-defined test case structure ensures clear documentation and facilitates efficient test execution, analysis, and reporting.

Get 100 minutes of automation test minutes FREE!!

Reviewer’s Profile

Harshit Paul

Harshit is currently the Director of Product Marketing at LambdaTest. His professional experience spans over 7 years, with more than 5 years of experience with LambdaTest as a product specialist and 2 years at Wipro Technologies as a certified Salesforce developer. During his career, he has been actively contributing blogs, webinars as a subject expert around Selenium, browser compatibility, automation testing, DevOps, continuous testing, and more.

Development of test cases plays a key role in the efficacy of a product. Designing test cases should be done in such a way that reduces the bug leakage ratio to a very minimum. From beginners to experienced professionals, you must know the art of writing test cases covering all basic to edge-case scenarios. Any tester can write test cases but optimizing them is an art. Let’s first look at the very essentials of the tutorial.

90 Overall in Just 2 Weeks - PTE All Module Study Plan | Skills PTE Academic
90 Overall in Just 2 Weeks – PTE All Module Study Plan | Skills PTE Academic

Test Case vs Test Scenario

A test scenario is a broader concept than test case, referring to a high-level description of a particular functionality or feature of the software that needs to be tested.

A test scenario outlines the general conditions, goals, and boundaries within which a group of test cases will be executed, while test cases focus on the minute details of that test. In other words, test scenarios typically cover multiple test cases that collectively ensure comprehensive testing of a particular aspect of the software.

You can have a look at this table to have a more structured understanding of both concepts:

Aspect

Test Case

Test Scenario

Definition

Specific set of steps and expected results

High-level description of functionality

Focus

Tests a single aspect or condition

Encompasses multiple related test cases

Identification

Has a unique identifier (Test Case ID)

Often identified by a descriptive title

Purpose

Detailed verification of a small unit

Provides context for a group of test cases

Granularity

Very specific and focused

More general and covers broader functionality

Contents

Test steps, inputs, expected results, etc.

High-level description, related test cases

Reusability

May be reused in different scenarios

Often used as a reference for grouping

Coverage

Addresses one specific behavior/scenario

Covers multiple test scenarios

Example

Testing user login with invalid password

Testing the user registration process

What is the difference between Test Scenario vs Test Case?

Test Scenario: Test Scenario gives the idea of what we have to test. Test Scenario is like a high-level test case. Learn more on how to write test scenario here.

For example: Verify the login functionality of the Gmail account.

Also read Test Scenario vs Test Case

Assume we need to write test cases for a scenario (Verify the login of the Gmail account).

Here are some test cases.

1. Enter valid User Name and valid Password2. Enter valid User Name and invalid Password3. Enter invalid User Name and valid Password4. Enter invalid User Name and invalid Password

Test Cases For Amazon | Test Cases for Flipkart | Test Cases for E-Commerce Website
Test Cases For Amazon | Test Cases for Flipkart | Test Cases for E-Commerce Website

What Is the Difference between a Test Case and a Test Scenario?

Although they may seem quite similar, test cases and test scenarios are two very different aspects involved in testing the functionality of a new software, update, or process. Test cases are specific conditions under which a new functionality is tested, whereas a test scenario is the overall end-to-end functionality of an application when it is working correctly.

Test cases are usually lower-level actions that can be created or derived from test scenarios. They give information about preconditions, what is being tested, how the test will be carried out, and the expected results.

Test cases require detailed documentation in order to assess how a test is proceeding, and a test case verifies the output of a function.

On the other hand, test scenarios are made up of test procedures, which encompass many test cases. Test scenarios are generally considered to be higher level and include groups of test cases, depending on the following factors: the functionality being tested, the type of test being performed, and the duration of the test.

Overall, test scenarios help reduce the complexity and confusion involved in creating a new product or updating a new function.

Conclusion

Creating a properly designed test case template can be beneficial for both you, the developer and the customers who will end up using the product you created. By bringing the testing phase to the end, you’re also ending the coding phase of your product which marks the beginning of selling the software or licensing it.

We hope that we helped you with this guide, now you can finally create a test case example that is simple for both you and your tester to use. Keep in mind the management software that we mentioned, if you have troubles in the future you should consider using these tools.

Top 10 Excel Interviews Questions – How to pass any Excel Assessment Test
Top 10 Excel Interviews Questions – How to pass any Excel Assessment Test

Best Practices To Write A Good Test Case

With those test case templates downloaded, you can now start to document all of the test cases you are working on for a more structured and comprehensive view. Here are some best practices and tips to help you best utilize the template we provide:

  • You can clone the template and have separate test case sheets for different areas of the software
  • Follow a consistent naming convention for test cases to make them easily searchable.
  • You can group similar test cases together under a common feature/scenario
  • Familiarize yourself with the requirement or feature you’re testing before creating the test case so that you’ll know what information to include
  • Use action verbs at the start of each test step like “Click”, “Enter” or “Validate”. If needed, you may even create a semantic structure to describe your test case. You can check out how it is done in BDD testing.
  • Include any setup or prerequisites needed before executing the test.
  • Ensure that the test cases you included are not only the “common” scenarios but also the negative scenarios that users don’t typically face but do happen in the system
  • Use formatting to make your test cases easier to read and follow
  • Make sure to update your test cases regularly

FAQs on Test Case Template

What is an Agile test case template?

An Agile test case template designed specifically for Agile testing. This template typically includes fields for user stories, acceptance criteria, test steps, expected outcomes, and integration with automated testing, which are all important Agile practices.

What are popular test case management tools?

Some popular test case management tools widely used in the industry include TestRail, qTest, Zephyr, and PractiTest. These tools provide features like test case creation, organization, execution tracking, integration with issue tracking systems, reporting, and collaboration.

What are the three parts of a test case?

A test case consists of three main parts:

  • Preconditions establish the initial conditions required for the test to be executed.
  • Test steps outline the series of actions performed during the test.
  • Expected results define the anticipated outcomes or behaviors that the software should exhibit after each step.

These components together form a comprehensive test case, aiding in systematic and effective testing.

Every day I keep on getting several requests for a Test Case Template. I’m surprised that many testers are still documenting test cases with Word docs or Excel files.

Most of them prefer excel spreadsheets because they can easily group test cases by test types and most importantly they can easily get test metrics with Excel formulas. But I’m sure that as the volume of your tests goes on increasing, you will find it extremely difficult to manage.

If you are not using any Test case management tool, then I would strongly recommend you to use an open-source tool to manage and execute your test cases.

Table of Contents:

How To Write A Test Case? | Test Case In Software Testing | Software Testing Tutorial | Edureka
How To Write A Test Case? | Test Case In Software Testing | Software Testing Tutorial | Edureka

Related IT Content

If you’re still looking for more IT-related information, you’ve come to the right place. ProjectManager is not only award-winning software but the online hub for all things project management. We publish weekly blogs, have guides, eBooks, tutorial videos and, of course, templates. Here’s some of the stuff we’ve published about how project management and the IT industry intersect.

  • IT Project Management: The Ultimate Guide
  • What Is IT Management? Why Is IT Important For Business
  • 15 Free IT Project Management Templates for Excel, Word and More

How To Write a Test Case in Manual Testing?

Manual testing, as its name suggests, is all about executing test cases manually, with no help from automation testing tools or scripts. Testers also have to consider all of the components of the test cases mentioned above, then build a spreadsheet to document all of that.

Read More: Manual Testing vs Automation Testing: A Full Comparison

Writing test cases in excel | Software Testing
Writing test cases in excel | Software Testing

Related IT Templates

If you’re not ready to upgrade to ProjectManager yet, we understand. It’s a big decision. As you make that decision, here are some of the IT-related free templates that we have to help you with your IT project management. They’re just a few of the dozens of free project management templates we have for Excel and Word. Download them today.

IT Project Plan Template

Our free IT project plan template helps you list all your tasks, costs, resources, time and deliverables. This free template will get your IT project started right from the start. Best of all, you can create that plan on any of our multiple project views to work how you want to.

IT Risk Assessment Template

All projects have risks. To mitigate those risks in your IT project, use our IT risk assessment template for Excel. It helps you identify risks and assess them, but also define control activities, monitor them and more.

Server Maintenance Checklist

IT project managers have a lot of work they need to do, one of the most important ensuring the server is up and running. Our free server maintenance checklist template for Excel will help them by making sure they’re thorough when doing such an important task.

Types of Test Cases

There are different test cases based on the testing methodologies you are following in your project. Some are Functional, API, Performance, Security, Usability, UI, Database, and Unit Test Cases. Functional Test Cases are the ones that are written to test every functionality of the application against user requirements defined by stakeholders. API Test Cases are the ones that are executed before UI is developed for functionality. We test various APIs against different sets of inputs and conditions. Performance and Security Test cases are used to test the application’s load capacity and vulnerabilities, respectively.

Usability Test Cases are executed to evaluate how user-friendly is our application. Database test cases are mostly SQL or No SQL-based testing. Unit test cases are written by developers to test their code effectively.

Test Cases for Amazon, Flipkart in Excel Sheet.
Test Cases for Amazon, Flipkart in Excel Sheet.

Popular Test Case Management Tools

some of the popular tools for the test management process are

  1. PractiTest
  2. Test Rail
  3. Testpad
  4. Qase
  5. Klaros
  6. Test Collab
  7. QMetry
  8. Meliora Testlab
  9. TestLodge
  10. TestCaseLab

Don’t miss this detailed article on Best Test Case Management Tools in the market.

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 very useful during test execution. Test priorities for business rules and functional test cases can be medium or higher, whereas minor user interface cases can be of a low priority. Testing priorities should always be set by the reviewer.

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.

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)

– Test case DOC file template and– Test case Excel file template

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)

Undoubtedly, the test cases will differ depending upon the functionality of the software that it is intended for. However, given below is a template that you can always use to document the test cases without bothering about what your application is 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:

=> Download the above Test case format with example data

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.

[Note: Click on any image for an enlarged view]

How to Write test cases in Excel
How to Write test cases in Excel

Test Case Components

No matter what method to document the test case was chosen, we should include the following fields in the test case:

  1. Test Case ID: A unique identifier for the test case.
  2. Title/Description: A concise description of the purpose of the test case.
  3. Test Objective: The specific goal or objective of the test.
  4. Preconditions: Any necessary conditions that must be met before the test is executed.
  5. Test Steps: A step-by-step sequence of actions to perform during the test.
  6. Input Data: The data or parameters to be used as input for the test.
  7. Expected Results: The anticipated outcomes or behaviors after executing the test steps.
  8. Actual Results: The actual outcomes observed when executing the test.
  9. Test Environment: Details about the system, hardware, software, and configurations used for testing.
  10. Test Data Preparation: Instructions on how to set up the required test data.
  11. Test Execution Date: The date and time when the test was executed.
  12. Test Execution Status: The pass/fail status of the test case after execution.
  13. Test Conclusion: A summary of the results and observations of the test.
  14. Test Verdict: A judgment about the overall success of the test.
  15. Bug Details (optional): If a defect is identified, details about the issue, its severity, and steps to reproduce it. Generally teams will manage the bugs found in another dashboard, but if you want to link the bug found to a specific test case, you can totally include this field there
  16. Attachments: Any relevant files, screenshots, or documentation associated with the test.
  17. Test Case Author: The person responsible for creating the test case.
  18. Test Case Reviewer: The person who reviewed and approved the test case.
  19. Test Case Version: The version or revision number of the test case.
  20. Notes/Comments: Additional information, insights, or comments related to the test case.

If you want to go all in, you can even classify the bug by its stages in the bug life cycle or its severity. Make sure to tweak the test case to include only the information you need for the project.

Manual Testing Test Case Template

Download Manual Testing Test Case Template

With this manual testing test case template, you can record testing steps and data, analyze expected results versus actual results, and determine whether or not you can consider a test to be a success. With space to record each individual step of the testing process, the test ID and name, and additional notes to consider during analysis, this template allows you to run through every possible result in a trial and determine if it passed or failed inspection.

Sample Test Case Template Document Excel
Sample Test Case Template Document Excel

What is Test Case Template?

A Test Case Template is a well-designed document for developing and better understanding of the test case data for a particular test case scenario. 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.

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.

Template for Test Case Management

Test case formats may vary from one organization to another. However, using a standard test case format for writing test cases is one step closer to setting up a testing process for your project.

It also minimizes Ad-hoc testing that is done without proper test case documentation. But even if you use standard templates, you need to set up test cases writing, review & approve, test execution and most importantly test report preparation process, etc. by using manual methods.

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

Katalon Platform is an all-in-one, simple automation tool for web, API, mobile, and desktop trusted by over 850,000 users.

It simplifies automation for those without a coding background to create automation test cases from manual tests’ steps, a rich library of project templates, record & playback, and a friendly UI.

#2) Testiny

Testiny – a new, straightforward test management tool. It is a fast-growing web-application built on the latest technologies and aims to make manual testing and QA management as seamless as possible. Its design is extremely intuitive, makes writing and maintaining test cases easy, and helps testers perform tests without adding bulky overhead to the testing process.

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 listed the maximum number of fields related to the test case. However, it is advised to use only those fields used by your team. Also, if you think any fields used by your team are missing from this list, then feel free to add them to your customized template.

How To Generate Manual Test Cases Automatically With Screenshot | Testcase Studio
How To Generate Manual Test Cases Automatically With Screenshot | Testcase Studio

ProjectManager Helps IT Professionals

ProjectManager is online project management software that connects everyone on the IT team, whether they’re in the office, out in the field or anywhere in between. They can share files, comment at the task level and much more to better collaborate, plan and mitigate resource constraints. Our resource management features help you with delivery times and keep everyone working at capacity. Get started with ProjectManager today for free.

From broken links to missing images, there’s no doubt about it: a janky website isn’t good for business.

Each test needs to be documented, but first explained, which is done in the form of a test case.

This article will explain how to write a test case in various common scenarios.

Contents:

  1. What Is A Test Case
  2. The 9 Basic Steps Of Writing A Test Case
  3. Test Case Templates
  4. Tips For Writing Good Test Cases
  5. Conclusion

Best Practices To Write Good Test Case

Characteristics of a good test case are

  • Easy to understand and execute
  • Create Test Cases with End User’s perspective
  • Unique Test case Identifiers must be used. It allows us to track them easily.
  • Prerequisites should be listed clearly. Helps to execute the test case without any issues.
  • Test data should be defined to evaluate each functional area.
  • Test case description should be concise.
  • Test Steps should be in detail and clear.
  • Specify the exact expected result.
  • Position condition should be listed if any.
  • Test cases should neither too simple nor too complex.
  • Test cases must be distinctive. There should not be no repeated test cases.
  • Test cases should be written by following test case design technqiues.
  • Test cases must be comprehensible. So that any tester (even a newly appointed testers) can understand them by perusing once.
  • Needs to provide clear environment details where we need to execute them.
  • Test cases should be reusable & maintainable
  • Get peer review.

If you follow the best practices to write test cases then anyone in the team can understand and execute the well-written test case easily. It should be easy to read and understand, not only for whoever wrote it but also for other testers as well.

Easy to understand and execute:

To make the test cases easy to understand and execute faster we need to use simple and easy to understand language like “Go to login page”, “enter username”, “enter password”, “click on login button” and so on.

Create Test Cases with End User’s perspective:

Create test cases by keeping end-user in mind. The test cases you create must meet customer requirements.

Use unique Test Case ID:

It’s good practice to follow a unique id with some naming convention for better understanding and discrimination purposes.

Have a clear description:

Your test case description should be clear enough to understand what the tester is going to do with this test case.

Add proper preconditions & postconditions:

In some cases, test cases need to meet some conditions before execution or achieve some conditions after execution. These conditions we need to mention properly in the Pre and postconditions.

Specify the exact expected result:

Include the Expected result: Expected result tells us what will be the result of a particular test step. Testers decide the pass or fail criteria based on the expected result.

Test cases should be reusable & maintainable:

A well written test case is reusable and maintainable. There ar times where developers change the code, and testers need to update the test cases. If our test cases are easy to read and understand then it would be easy to update them not only by whoever wrote it but also by other testers as well.

Utilize testing techniques:

Use testing techniques whenever necessary. Software test design techniques are used to derive the test cases from the Requirement Specification document and also based on testers expertise

  • Equivalence Partitioning
  • Boundary Value Analysis
  • Decision Table
  • State Transition
  • Exploratory Testing
  • Error Guessing

Get peer review:

Let your peers review your test cases to uncover the defects in your test case design.

HP ALM - Import Test Cases From Excel
HP ALM – Import Test Cases From Excel

Test Case Templates

Would you like to see some test case examples?

Take a look at some of these templates using test case management tools and programs to see how you can structure your next test case.

Google Sheets

By using Google Sheets, you’ll have a dynamic hub for a test case.

The key advantage here is that if you have multiple people working on this project, you can give them edit access too to make changes or add their own notes.

Check out the template made by BugHerd just for you!

Microsoft Excel

Using an excel spreadsheet is old school but still viable for standard test cases.

You can fill the spreadsheet horizontally or vertically to fit the format that best suits your preferences.

You can see an example of a horizontal spreadsheet test case here.

There are several more downloadable excel spreadsheets for test cases here.

Jira

There are no set presets for test cases in Jira, but you can use the “issue type” feature and customize it for test cases.

To complete the test case, add subtasks that correlate to the nine steps for test cases.

Or, use Zapier to connect your BugHerd bugs to Jira.

Read more: Combine BugHerd With Jira For The Ultimate Bug Tracking Tool

Trello

You can use Trello as a management tool by following the test steps laid out below:

  1. Create a workspace.
  2. Create a board.
  3. Make your board workspace visible to allow testers to use the board.
  4. Change the list names for each website or software application you are testing.
  5. Create cards for each function you write a test case for.
  6. Assign these cards a test ID and description, and attach the test data.
  7. Add a checklist to the card as the steps to follow.
  8. You can create different checklists for positive, negative, and destructive test cases.
  9. Testers can check off the steps as they go.

Or, like with Jira, you can connect BugHerd to Trello using Zapier.

monday.com

monday.com is another great task management tool that can be used to create test cases. They have the process outlined on their blog here, along with a free template to use.

You can also connect BugHerd to monday.com to make test case creation super convenient.

What’s Included in Our Test Case Template?

Our free test case template for Excel outlines all the steps you need to take when testing software. If you have a different sequence or want to add or delete something from our template, know that the template is fully customizable. These are the steps we’ve outlined on our test case template.

  • Test case ID: Each of your test cases should have a unique identifier so that you can easily look one up (there will be many tests). Choose a naming convention and stick to it, whether you use ours or one of your own.
  • Test case scenario: Here’s where you’ll choose one of the many test scenarios your developers and testers have created. A test case should only focus on one specific scenario at a time. This is where you’ll describe that test case scenario.
  • Test case: At this point, you’ll take the test scenario chosen and explain how it will be tested. In our example, we chose to test the login. Therefore, one test case is to use the correct user ID and correct password. Another scenario would be to use the incorrect user ID and correct password and so forth.
  • Pre-conditions: These are the conditions that need to be met before executing the test case. Again, in our example, the pre-conditions are having a valid user ID and password to test that functionality.
  • Test steps: Here’s where you’ll list the actions needed for the test case scenario. Be sure to mention all the steps in as much detail as necessary and the order in which they should be executed. This should be done from the end-user’s perspective. Looking at our example on the template, those steps would be to enter the correct user ID and correct password and then click the login button.
  • Test data: To run the test case, you need to have the right data. In the case of our example, that’d be having the correct user ID and correct password to test the login function of the software.
  • Expected results: This is where you note the result you expect to happen, which ideally is that the login works and the user is given access to the software. But you might not think the test will work in which case you’d write what you think will happen, perhaps an error message or nothing at all.
  • Post-condition: This is the condition that needs to happen for the case to be successfully executed. For example, the login works.
  • Actual results: Of course, the actual results may be very different from what you expect as the post-condition of the case test. This is where you’ll put those actual results. It could be that the login worked, which is great. But if the login doesn’t work, you’ll need to detail what happened to mitigate the bug.
  • Status: The test case will have one of two outcomes: pass or fail. If it passes, you can move to the next scenario. If it fails, then you’ll have to fix the problem and do another test case until it passes. Our template has a dropdown menu with a red failure or a green pass to indicate the status of the test case.
Test Case Formatting : Excel Feature that Every tester must know- Part 2
Test Case Formatting : Excel Feature that Every tester must know- Part 2

Best Practices To Write A Good Test Case

With those test case templates downloaded, you can now start to document all of the test cases you are working on for a more structured and comprehensive view. Here are some best practices and tips to help you best utilize the template we provide:

  • You can clone the template and have separate test case sheets for different areas of the software
  • Follow a consistent naming convention for test cases to make them easily searchable.
  • You can group similar test cases together under a common feature/scenario
  • Familiarize yourself with the requirement or feature you’re testing before creating the test case so that you’ll know what information to include
  • Use action verbs at the start of each test step like “Click”, “Enter” or “Validate”. If needed, you may even create a semantic structure to describe your test case. You can check out how it is done in BDD testing.
  • Include any setup or prerequisites needed before executing the test.
  • Ensure that the test cases you included are not only the “common” scenarios but also the negative scenarios that users don’t typically face but do happen in the system
  • Use formatting to make your test cases easier to read and follow
  • Make sure to update your test cases regularly

Automation Testing Test Case Template

Download Automation Testing Test Case Template

Use this automation testing test case template to review the success or failure of an automated software, application, or feature. Document the test name and ID, the test duration, each separate step and component, and any notes about the test, including the parts of the test that are automated. Simply download and fill out this form to fit the needs of whatever automated application you are testing.

Test Case Formatting : Excel Feature that Every tester must know- Part 5
Test Case Formatting : Excel Feature that Every tester must know- Part 5

What are Test Cases?

A test case is a test scenario to test functionality with a different set of input and parameters. We test the expected Result of the test case with the expected one. The test case is marked as passed if the output matches and is marked as failed if the output of expected and doesn’t match. Test cases can be executed manually or via automation.

Test cases are maintained in test management tools like Jira, HP QC, and others. Let’s look at the main components of test cases.

  • Test Case ID
  • Test Case Description
  • Assumptions
  • Test Data
  • Pre-Condition
  • Test Steps
  • Expected Test Result
  • Actual Test Result
  • Status Pass/Fail
  • Comments

Tips For Writing Good Test Cases

Well-written test cases can make the testing process more efficient and accurate.

Here are some tips to follow when writing test cases:

Use Testing Techniques

There are several different testing techniques available to use. Of course, you can’t expect to use every technique in your testing process.

However, selecting the technique that will provide the greatest possibility of detecting bugs is best.

The testing of one website may employ several different testing techniques in its testing execution.

Some of the most popular testing techniques include:

Equivalence Partitioning

With this technique, you divide the test cases into groups. These groups should all work under one condition.

Then if one test case works under that condition, all in the group should also work.

State Transition Testing

This technique is used when previous actions may dictate the transition from one input to the next.

Boundary Value Analysis

With boundary value analysis (BVA), a specific range of values is used to test the website function.

For example, for a website about beer, you would want to test a prompt asking for the user’s age.

The minimum acceptable value for admittance to the site is 21. BVA would be the correct testing technique to put in place for this function.

Error Guessing Technique

Error guessing doesn’t follow any rules, but instead uses the tester’s prior experience with the website to test scenarios at random.

What kind of random situations would a software tester think of testing?

How about entering alphabetical values into a numerical field, or submitting an email signup form without entering a valid email address?

Implementing this technique may require creativity, but it certainly aids in ensuring complete test coverage.

Decision Table Technique

The decision table technique follows the cause-and-effect pattern for functions with relationships between inputs.

To use this technique, testers would create a table with conditions or actions followed by columns for each test case. After testing the conditions, testers would mark the columns accordingly.

Keep End-User Perspective

The user is who you are testing for, so it only makes sense to write test cases with the end user in mind.

Whether testing for functionality or compatibility, user experience is always key to ensuring your website is well-designed. Go through all your test cases and consider the practical value they provide to the end user.

Use Clear And Concise Language Throughout

Effective test cases cannot be vague in any manner. Clear and concise language must be used throughout the test case.

This includes the test description and expectations. It is especially important when writing out the steps to follow.

Test cases need to be written without assuming testers have background knowledge. Even new testers should be able to execute the test from the steps in the test case.

Make Sure It Is Reusable

When any updates are done on your website or any of the coding is changed, the testing process will need to be repeated.

For that reason, it is always a good idea to make your test cases reusable.

Always keep a master copy and then make a duplicate for use to perform the test.

That way, you can simply make another duplicate for your next update or even use it for a new website project in the future.

Also, remember that test cases will need many revisions and updates, as website requirements are always changing.

Get Peer Review

Before issuing a test case, allow others to read it. They may catch things you missed or offer some advice on clarity or word usage.

Getting a peer to review your test case is one of the best forms of quality assurance.

Make Sure They’re Self-Cleaning

While conducting the test cases, no permanent change should be made to the test environment. Testers should be able to return to the pre-test state after completing the test.

Stick To Specification Documents

When writing test cases, do not assume any functions of the website. Instead, use the specification documents to dictate the parameters of your test case.

How to write test case in excel | How to write test cases in manual testing with example in English
How to write test case in excel | How to write test cases in manual testing with example in English

What is a Test Case Template?

A test case template is a predefined structure that provides a standardized way to document and create test cases. We have provided them as guidelines for testers to ensure that all necessary information about a test scenario is captured consistently across different test cases. With a good test case template, testing teams can maintain uniformity and improve the clarity and completeness of their test documentation.

Conclusion

Now, you must be clear on how to write effective test cases. Start downloading our sample test case document and continue with test case designing. It takes time to be an expert in writing test cases, but in no time, you will be an expert by following the above tips. If you still have any doubts get a free estimation from us and make your test cases development process more efficient at minimum cost.

When developing software, one of the most important objectives is to minimize the number of bugs for the end-product. Although most bugs are usually removed during the alpha and beta phases of software, it is important that you test it through the entire building phase.

Table of Contents

  • 1 Test Case Templates
  • 2 What is a test case?
  • 3 Test Case Examples
  • 4 What does a test case template consist of?
  • 5 Test Case Documents
  • 6 Information to include while drafting a test case
  • 7 Things to do in order to write a good test case example
  • 8 Test Case Samples
  • 9 Should you use software for managing your test cases?
  • 10 Conclusion

The most effective way to do this is to get a tester who will run the entire program and reported anything unusual back, but there is a lot more to it than that. You will need to create a test case template first, by creating one you can give the tester several sequences of steps that will help him confirm if the program is free of bugs.

Software testing using excel - How to create a test script
Software testing using excel – How to create a test script

Improve Your Test Cases with Free Test Case Templates in Smartsheet

Empower your people to go above and beyond with a flexible platform designed to match the needs of your team — and adapt as those needs change.

The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed.

When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time. Try Smartsheet for free, today.

Test Case Template with Examples: Free Excel & Word Sample for Download

Having a good test case template comes with tons of benefits. Not having to re-invent the wheel is one of them. Drawing from years of experience in the software testing industry, we have created a detailed template for you to note down your test case in the most organized manner, so that you can dedicate your time and effort to other high-value tasks. Scroll down and download your template, and if you want to get some tips on how to best write a test case, read on, we got you covered!

FAQs on Test Case Template

What is an Agile test case template?

An Agile test case template designed specifically for Agile testing. This template typically includes fields for user stories, acceptance criteria, test steps, expected outcomes, and integration with automated testing, which are all important Agile practices.

What are popular test case management tools?

Some popular test case management tools widely used in the industry include TestRail, qTest, Zephyr, and PractiTest. These tools provide features like test case creation, organization, execution tracking, integration with issue tracking systems, reporting, and collaboration.

What are the three parts of a test case?

A test case consists of three main parts:

  • Preconditions establish the initial conditions required for the test to be executed.
  • Test steps outline the series of actions performed during the test.
  • Expected results define the anticipated outcomes or behaviors that the software should exhibit after each step.

These components together form a comprehensive test case, aiding in systematic and effective testing.

Hello friends! In this post we will present a test case template in Excel/spreadsheet, describing the use of each field in detail. Ideally, a test case management tool should be used for managing the test cases and test execution cycles. But for smaller projects, many organizations still prefer to use spreadsheets for avoiding the overhead of maintaining and configuring a tool.So, let’s begin.

Content

How to write effective Test Cases

Now, we have looked at the way test cases are written and how to optimize them. This mystery is still not solved yet. Let’s now dig into detail to write effective test cases.

  • Always stick to user requirements and never write test cases on assumptions. Always stick to the SRS document or clear your doubts, if any, but never deviate to another lane while writing test cases.
  • As we follow agile, it is very important to update yourself on the latest functionalities. Communicate as much you can with stakeholders and technical guys so that you can keep the SRS updated with agile dynamism.
  • The test Case description should always be to the point so that it is very easy to segregate the test cases on functionality by just reading the Description.
  • Always write test cases by mimicking yourself as a customer. Put yourself in the shoes of a customer, which will help you cover all test scenarios that a customer can execute.
  • Your test steps should be granular instead of writing lengthy, detailed test steps. They should be crisp and clear. If a step is big, break it into granular steps to make the test case easy to understand and execute for anyone.
  • Test Cases should be assigned to you if you have written them. Ownership of test cases is very important for the maintenance of test cases.
  • Use a test management tool to organize your test cases, test plan, test cycles, and reports. It will act as a common medium for all team members, and it will help you better manage your test cases.
  • It is very important to get the test cases reviewed by your team so that no duplicate test cases are written which help to get rid of unnecessary test cases.
  • Exploratory testing is very important to find bugs. So, it is very important to have a mindset of a critic in your mind while executing test cases so as not to miss important bugs.
  • Don’t have too many objectives in a test case. Always stick to the fact that a single test case will follow a single objective.
  • Prioritization of test cases is very important in crunch times. It is very you have a priority defined for your test cases so that you don’t miss your test cases when you have very little time left.
  • Learning automation and starting with the automation of manual test cases is equally important as this will reduce manual efforts and will help in finding a greater number of bugs. You must be thinking How to write test cases in java. You can use any automation tool like Selenium/ Cypress with Java to write your functional test cases. This can be integrated with reporting tools like TestNG, Allure, and Extent for amazing reports.
  • Always have cross-browser test cases so that no bugs are leaked to production.
  • One more thing you must be confused at the fact: Who writes UAT test cases? User acceptance testing is done by stakeholders in pre-prod and production. Hence, we leave this part for business analysts and stakeholders to have crucial test places in place by following the above steps.

Tips to Write, Implement, and Track Test Cases

In order to gain the most from the tests you are running, you must create comprehensive, detailed, and test-specific test cases that describe exactly what is being tested, why it is being tested, and what the expected results should be.

To run the most effective test cases and gain powerful, actionable insights, follow these simple tips:

  • Make the test steps as clear as possible, avoiding vague objectives and directions.
  • Ensure that the test has no more than 15 steps to avoid confusion. If there are more than 15 steps, break the test into separate tests.
  • In the test directions, include any additional documents or references that might be relevant to the test itself.
  • Include a detailed description of the requirement being tested, and explain in detail how the test should be carried out for each requirement.
  • Provide details on all the expected results, so the tester can compare the actual results against them. Of course, this step is unnecessary if the expected results are obvious.
  • Use active case language when writing the steps, and make sure they are as simple and clear as possible.
  • Avoid repeating any of the same steps, as this could add confusion to an already complicated process.
  • Include the test name and ID in the testing instructions.
  • Keep the end user in mind as you develop the test and its variables.
  • Reread and peer review the test case instructions before finalizing them.
  • Remember that the test case should be repeatable, traceable, and accurate.

The 9 Basic Steps Of Writing A Test Case

There are nine basic steps to writing a complete test case. With these elements in place, test execution should always be possible from the written test case.

Test Case ID

A unique ID should be created for each test case.

These IDs should follow a numerical or alphabetical pattern for less confusion in identifying individual cases.

Test Description

The test description outlines what is being tested and how that will be verified.

A common sentence structure for the test description is as follows:

“Verify ‘function’ by ‘action’ with ‘another action.’”

i.e., verify authentication by using a correct password in Gmail.

Preconditions

Preconditions (or prerequisites) are conditions that need to be met before testing can begin.

Without these in place, test coverage will be invalid.

Test Data

Test data is any input or data necessary to perform the test. These could include the login and password, test script, or exact URL.

Steps To Be Executed

These steps from the end user’s perspective will need to be followed to verify the end goal.

They must be written clearly and concisely for the testing team to understand. Using a traceability matrix can ensure that every condition and function is tested.

Expected Results

The expected result is what should happen with a bug-free website if all the steps in the test case are followed.

Postconditions

A postcondition is something that should happen as a result of a successful test outcome.

For example, if your expected result of inputting your username and password into the login page is to gain admittance to the home page, a postcondition is to have the home page load.

Actual Result

Did the test case result in the expected results?

If not, what was the result?

This is the actual result, which may or may not differ from the expected results.

Pass/Fail

If the expected results were met, the test passed. If not, it failed.

What if a test fails?

Time for a bug report!

The bug lifecycle will need to be followed and corrected. Then regression testing must be conducted.

Read more: Bug Reporting: What Is A Bug Report And How To Create Good Bug Reports

Keywords searched by users: test case example excel

Test Case Template For Excel (Step By Step Guide) - Youtube
Test Case Template For Excel (Step By Step Guide) – Youtube
Test Case Template (Download Sample Excel)
Test Case Template (Download Sample Excel)
Free Test Case Templates | Smartsheet
Free Test Case Templates | Smartsheet
43 Test Case Templates / Examples From Top Software Companies ᐅ Templatelab
43 Test Case Templates / Examples From Top Software Companies ᐅ Templatelab
43 Test Case Templates / Examples From Top Software Companies ᐅ Templatelab
43 Test Case Templates / Examples From Top Software Companies ᐅ Templatelab
Test Case Template For Software Feature Troubleshooting
Test Case Template For Software Feature Troubleshooting
Sample Test Case Template Document Excel - Youtube
Sample Test Case Template Document Excel – Youtube
Free Test Case Templates | Smartsheet
Free Test Case Templates | Smartsheet
Test Case Template: Free Samples To Download In Excel & Word
Test Case Template: Free Samples To Download In Excel & Word
Sample Test Case Template With Test Case Examples [Download]
Sample Test Case Template With Test Case Examples [Download]
Free Test Case Templates | Smartsheet
Free Test Case Templates | Smartsheet
43 Test Case Templates / Examples From Top Software Companies ᐅ Templatelab
43 Test Case Templates / Examples From Top Software Companies ᐅ Templatelab
Test Case Template For Excel (Free Download)
Test Case Template For Excel (Free Download)
Test Case Template – Techno Pm - Project Management Templates Download
Test Case Template – Techno Pm – Project Management Templates Download
Test Case Template (Download Sample Excel)
Test Case Template (Download Sample Excel)

See more here: kientrucannam.vn

Trả lời

Email của bạn sẽ không được hiển thị công khai. Các trường bắt buộc được đánh dấu *