17 User Acceptance Testing Templates [Examples + Download]

User acceptance testing templates are documents that help teams plan and execute UAT testing.

The end goal of UAT are to find out if:

• End users run into any issues when testing
• The software works in a real-world business context

Successfully running UAT (user acceptance testing) is challenging, so having the right processes and workflows in place is crucial.

In this blog post, we provide you with free user acceptance testing templates you can easily copy or download to implement with your team.

Whether your organization uses Jira, GitHub, Trello, GitLab, or Asana, or keeps a backlog in an Excel spreadsheet, in a Word document, or via email, we've got you covered.

To start mapping our your UAT process, you'll need the following:

• A UAT test plan template. This document is the foundation of your UAT testing plan. It outlines business requirements, the testing team, assignments, the testing process, and the testing strategy used during UAT execution. It can also work as a UAT document template for project managers, business analysts, and other business users.
• A UAT test case template. These are real-world scenarios and step-by-step instructions that show testers how to validate a specific feature and the business processes around it in a website or software application. Depending on your setup, this may look like a UAT test script template or a user acceptance testing template.
• A UAT checklist. This takes you through all the steps you need to follow to conduct UAT. You can find a downloadable user acceptance testing checklist on our blog.

Get started with our UAT test plan template and then find what works for you in our list of 16 more test case templates, which you can navigate to in the margin table of contents:

1. GitHub
2. Jira
3. Trello
4. GitLab
5. Asana
6. Teamwork
7. Shortcut
8. Monday
9. ClickUp
10. Wrike
11. Excel
12. Google Sheets
13. Word
14. Google Docs
15. PDF
16. Email

What is user acceptance testing, and what is a UAT template?

User acceptance testing (UAT) is performed at the later stages of the software development lifecycle, in a production or (production-like) environment. UAT focuses on whether the software meets business needs, user expectations, and business objectives before sign-off.

The process ensures that real end-users of a site or product can use it successfully, without getting confused or dropping out of the journey. Unlike QA, where a team will primarily check that there are no bugs or technical issues, UAT is more about making sure that whatever’s being tested meets the needs of the users and the business.

To succeed, you need to put a plan together, which is where a good UAT template comes in. User acceptance testing templates are quick, editable docs, files, or even blocks of copy you can customize and drop into your user acceptance testing tools of choice.

Here are 17 user acceptance testing templates you can start using today.

UAT Test Plan Template

This user acceptance testing template is your one source of truth for UAT planning, whether you need a UAT test plan template, a UAT testing plan template, or a UAT sign-off template.

It contains:

• Scope, business requirements, and objectives. Why are we building this new feature? What's the pain point/main functionality? What are technical objectives?
• Testing team. Every individual on the quality assurance team is assigned a responsibility – the who, the what, and the when.
• Milestones and deliverables. Every phase of acceptance testing is documented here: testing process design, staging environment, training, UAT execution, sign off, and test result reporting.
• Environmental requirements. Hardware (in some cases) and software requirements are listed here.
• Features to be tested. What are we expecting to discover during testing? What are the pass/fail criteria and acceptance criteria for each feature? What features do we want to avoid testing? What should our test cases look like? What are the exit criteria?”

This document is 100% editable – simply fill in the blanks with your own data. If you prefer docs, you can use it as a UAT test plan template Word file in Google Docs or Microsoft Word, alongside the rest of your UAT documents.

Here's a sneak peek:

You can download the full test plan in this Google Doc.

Remember to create a copy first, or you won't be able to edit it with your own data.

UAT test case templates

In user acceptance testing, test cases are real-world scenarios performed by real users, business users, or the end user.

The goal here is to write step-by-step instructions that lead testers to the expected result, but you also want to ensure your app is self-explanatory and user-friendly enough – in other words, you can’t hold testers’ hands through the entire process

Think about real-world usage, such as signing in through the login page or completing a forgot password flow. For example:

1. Log on to the app on “staging.acme.com”.

vs.

1. Go to “staging.acme.com”, then click the blue “log on” button in the top right of the screen.

The first example here is far better: it's clear what the desired result is, yet it allows:

• testers to figure out how to get there by themselves;
• the QA team to identify any friction in the process, which is the whole point of UAT testing.

Here's what you can include in most UAT test cases:

1. ID or Name. A unique identifier or a descriptive name that's easy to come back to.
2. Description. Insert what needs to be tested, but don't go into too much detail.
3. Test steps. Keep it brief, but make it clear what the end goal is.”
4. Expected result. Tell the end user what’s supposed to happen once they have completed the steps above. Example: “You should now be logged on to the dashboard.”
5. Actual result. This field is filled by testers and describes what actually happened. Example: the dashboard is loading indefinitely.
6. Status (Pass/Fail). Whether the task was successfully completed or not. This is typically a radio button.

Our UAT templates are designed to be customizable, yet comprehensive. Although there are a few types of user acceptance testing, UAT usually involves non-technical users. It makes sense to collect this data, as it would otherwise potentially be lost or incorrectly reported.

GitHub test case template

If your team uses GitHub, you can use the following format during user acceptance testing (UAT):

As you can see, this task contains all the basic fields you need for your test scenarios, including:

• ID
• Description
• Test steps
• Expected result
• Actual result
• Status

If you use Marker.io with GitHub, the following info will be collected automatically:

• Reporter name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If your team is on GitHub, consider signing up for a free Marker.io trial.

Jira test case template

If your team is on Jira, you can use the following user acceptance testing template.

If you use Marker.io with Jira, the following info is added automatically:

• Reporter name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If you need help setting up custom issue types and test cases in Jira, check out our guide on how to write test cases in Jira.

If your team is on Jira, consider signing up for a free Marker.io trial.

Trello test case template

If Trello is your PM tool of choice, you can use the following for your test cases:

If you use Marker.io with Trello, the following info is added automatically:

• Reporter name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If your team is on Trello, consider signing up for a free Marker.io trial.

GitLab test case template

If you use GitLab for your test scenarios, you can use this markdown-style format:

If you use Marker.io with GitLab, the following info is added automatically:

• End user name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If you use Marker.io for GitLab, the following info is added automatically:

Asana test case template

If you use Asana for user acceptance testing (UAT), you can use this for your test cases:

If you use Marker.io with Asana, the following info is added automatically:

• Reporter name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If your team is on Asana, consider signing up for a free Marker.io trial.

Teamwork test case template

If you use Teamwork to gather feedback during your test cases, you can use this task format:

Don't forget to add custom fields for ID and Status.

If you use Marker.io with Teamwork, the following info is added automatically:

• End user name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If your team is on Teamwork, consider signing up for a free Marker.io trial.

Shortcut test case template

If Shortcut is your go-to project management tool, you can use this markdown format for your test scenarios:

Don't forget to create a custom Status field with Pass and Fail as values.

If you use Marker.io with Shortcut, the following info is added automatically:

• Reporter name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If your team is on Shortcut, consider signing up for a free Marker.io trial.

Monday test case template

If you're using Monday for user acceptance testing, you can use this format for your test cases:

If you use Marker.io with Monday, the following info is added automatically:

• End user name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If you use Marker.io for Monday, the following info is added automatically:

ClickUp test case template

If ClickUp is your tool of choice for user acceptance testing, you can use this for your test cases:

If you use Marker.io with ClickUp, the following info is added automatically:

• User name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…)

If your team is on ClickUp, consider signing up for a free Marker.io trial.

Wrike test case template

If you use Wrike for user acceptance testing, you can use this format for your test cases:

If you use Wrike for user acceptance testing, you can use this format for your test cases:

If you use Marker.io with Wrike, the following info is added automatically:

• User name
• Source URL
• Screenshot
• Console logs and session replay
• Environment info (device type, browser, screen size, OS…

If your team is on Wrike, consider signing up for a free Marker.io trial.

Excel test case template

If you prefer Excel (.xls/.xlsx) to conduct user acceptance testing, you can use this format as a UAT testing template Excel teams can share.

Download the files here: Excel acceptance testing template format

If your team still uses spreadsheets, the UAT Excel template works well as a test plan template Excel file, or a UAT checklist template Excel option.

Google Sheets test case template

If you use Google Sheets, here is a UAT template you can use: Google acceptance testing format

Microsoft Word test case template

Microsoft Word is still used extensively for day-to-day work.

If that’s your jam for UAT testing, we’ve got you covered. This format works well as a UAT test plan template file for Word, or a simple UAT document template:

Download the files here: Microsoft Word (.docx) format

Google Docs test case template

Google Docs has many users, thanks to its ease-of-use and connection with the rest of the Google Suite.

Download the files here: Google Docs format

PDF Test Case Template

If your testers report via a PDF file, you can use a format similar to the previous MS Word and Google Docs options.

Even though PDFs aren’t very flexible, you might be a requirement to use them inside your organization.

If that's the case, Here’s the document from above in a PDF file.

Email Test Case Template

We don’t recommend using email for user acceptance testing, but it may be your only option. If that’s the case, you can use this format to gather UAT feedback and bug reports:

You can download the email file as a .txt here.

How Marker.io can help

Marker.io connects with many of these tools to create a smooth workflow, including:

• GitHub
• Jira
• Trello
• GitLab
• Asana
• Teamwork
• Shortcut
• Monday
• ClickUp
• Wrike

Whenever the end user spots a problem on your website or app, they can take a screenshot with Marker.io and add annotations to get their point across.

With just one click, the tool converts it into a new GitHub issue, Whenever the end user spots a problem on your website or app, they can take a screenshot with Marker.io and add annotations to get their point across.

In just one click, the tool converts it into a new GitHub issue, task, card, or story – depending on the integration.

If you’re a user of any of these tools and starting a UAT process, consider signing up for a free Marker.io trial.

Wrapping up...

Successful user acceptance testing is often challenging – for both testers and the quality assurance team aiming for a bug-free release.

It’s crucial to have a solid testing strategy in place and to ensure everything is tested thoroughly during alpha testing and beta testing, after system testing has been completed.

For successful UAT execution, you’ll need:

• A UAT test plan or UAT testing plan template
• Solid UAT testing tools
• A UAT test case template or UAT test script template, depending on the tools you use to conduct UAT

We hope the examples provided in this post have helped you find the right UAT template for your process, so business users can confirm the developed software meets business needs in a real environment.

Questions or feedback? Let us know on Twitter or via email!