Allowing your clients to test your web application prior to release is a good practice in the web application development industry. It is critical to get their approval for the most recent version or branch of your project. This saves you time and resources because it keeps you from having to deal with critical functional problems in production. This template is especially useful for quality assurance managers, project managers, and testers who are looking into organizing their company’s web application UATs. Have all your UAT test cases in one location and link them to related data that can be found in the other tables in this template. Keep track and get an overview of all the UATs in the Tests table. But before you can do that, you first need to put some brief information about each of your clients in the Clients table. Then, followed by the Users table, which listed testers from both your organization and the client’s. Then, the Projects table should have all of your organization’s web app projects. After that, you can now begin to use the Tests table. Lastly, put all test steps or test scripts in the Scripts table. You can group test scripts for different test cases by creating views for every test case. Browse through the sample data found in the following tables to better understand how this template works:

Tests

Find all of your test cases in this table, and use the different table views to understand them better. When the left border of a row is green, it means that all of the related test steps in the Scripts table for the test case have passed testing. A yellow left bar means that at least 70% of the related test steps in the Scripts table passed. A red left bar means that less than 70% passed testing. Also, if the tester assigned is a client from a different project, the background color of the whole row turns red.

Fields

• Test case ID. An autogenerated primary key that serves as the unique identifier for this test case record or row.
• Title. A unique title for this test case.
• Priority. A single select field indicating this test’s urgency or priority.
• Project. This field is linked to the Projects table, indicating the project this test case is related to.
• Description. A detailed technical description of this test case. You may include what this test is specifically for and the test’s entry and exit criteria.
• QA manager. This field is linked to the Users table, indicating the name of your organization’s assigned QA manager for this test.
• Browser. A single select field that indicates the Internet browser required and used for this test.
• Operating system. A single select field that indicates the required and used operating system for the test environment.
• Test result (%). This is a formula field that rounds and formats the output value of this record’s Percentage for filter field.
• Percentage for filter. This is a formula field that computes the percentage of related test steps in the Scripts table that were completed and passed. This field is also used as a filter criterion for this table. This field is hidden by default.
• Is accepted. This is a checkbox field that indicates whether or not the test was passed and accepted by the intended users or clients.
• Client. This field is linked to the Clients table and indicates which client is running this test case.
• Executed by. This field is linked to the Users table, specifying the name of the tester running this test case.
• Notes. Any recent brief description or remarks about this test.
• Date executed. The date this test case was executed.
• Date created. This is an automatically filled-in date indicating the date and time this test case was created.
• Date modified. This is an automatically filled-in date indicating the date and time this test case was updated.
• Attachments. Any technical documentation can be uploaded and attached to this test. You may include your test plans or other technical documentation or files related to this test.
• Related scripts. This field is linked to the Scripts table, identifying all scripts or test steps related to this test case. This field is hidden by default.
• Is tester match. This is a formula field that verifies if the selected tester is under or part of the selected client or company. The entire row’s background color turns to a red shade whenever a tester is assigned to a test case for a different client. This field is hidden by default.

Views

• All tests. Displays all test cases without filters, sorted alphabetically by Test case ID.
• Completed tests. Displays test cases with all the related test steps in the Scripts table completed, sorted alphabetically by Test case ID.
• Incomplete tests. Displays test cases with incomplete execution of test steps in the Scripts table, sorted alphabetically by Test case ID.
• Not started tests. Displays test cases with test steps in the Scripts table that have not been executed yet, sorted alphabetically by Test case ID.
• Accepted tests. Displays test cases that have already passed and have already been accepted by the end-user or client, sorted alphabetically by Test case ID.
• Open tests. Displays test cases that are pending client acceptance or approval, sorted alphabetically by Test case ID.
• By priority. Displays a kanban view of test cases stacked according to the Priority field.
• By browser. Displays a kanban view of test cases stacked according to the Browser field.
• By operating system. Displays a kanban view of test cases stacked according to the Operating system field.
• Add new test. Displays a form view that enables adding new test cases in this table.

Clients

All your organization’s customers should be in this table. This table also serves as a reference for the other tables in this template. A couple of formulas were provided to indicate the number of projects and testers assigned to each customer.

Fields

• Name. The client’s business name.
• Description. A long description about the client’s business.
• Industry. A single select field that indicates the client’s industry or business domain.
• Website. The URL of the client’s official website.
• Notes. This field holds notes or remarks about this client.
• Projects count. A formula field that counts the total number of projects this client has in the Projects table.
• Users count. A formula field that counts the total number of users or testers this client has in the Users table.
• Related projects. This field is linked to the Projects table, identifying all projects linked to this client. This field is hidden by default.
• Related users. This field is linked to the Users table, identifying all users linked to this client. This field is hidden by default.

Views

• All clients. Displays all clients without filters, sorted alphabetically by Name from A to Z.
• Add a client. Displays a form view that facilitates adding new clients to this table.
• By industry. Displays a kanban view of clients stacked according to the Industry field.

Projects

Each version and/or branch of each of your web applications to be tested is listed in this table. A couple of formulas were provided to calculate the total number of test cases and the acceptance rate for each record. When the left border of a row is red, it means that less than 70% of the related test cases in the Tests table were accepted or approved by the client.

Fields

• Name. This is the web application or the project’s name.
• Description. A detailed description of this project.
• Batch ID. This is the project’s version, batch, or release number to be tested.
• Server name. This is the client-accessible server or project environment alias where tests are conducted.
• Client. This field is linked to the Clients table and indicates which clients are using and testing this project.
• Project manager. This field is linked to the Users table, indicating your organization’s project manager or lead for this project.
• Tests count. A formula field that counts the total number of test cases this project has in the Tests table.
• Tests accepted (%). This is a formula field that rounds and formats the output value of this record’s Percentage for filter field.
• Percentage for filter. This is a formula field that computes the percentage of related test cases in the Tests table that passed and were accepted by the intended users or clients. This field is also used as a filter criterion for this table. This field is hidden by default.
• Attachments. Any technical documentation can be uploaded and attached to this project. You may include this project’s server requirements and documents.
• Related tests. This field is linked to the Tests table, identifying all test cases linked to this project. This field is hidden by default.

Views

• All projects. Displays all projects without filters, sorted alphabetically by Name from A to Z.
• With incomplete tests. Displays projects with test cases that are not yet accepted or approved by the client, sorted alphabetically by Name from A to Z.
• With all tests accepted. Displays projects with test cases that are all accepted and approved by the client, sorted alphabetically by Name from A to Z.
• Add a project. Displays a form view that facilitates adding new projects to this table.

Scripts

All test scripts and test steps for each test case listed in the Tests table can be found here. A formula was added to automatically assign a group color to each group of test steps. This allows you to quickly distinguish between test case groupings. The Is pass field in this table aids the Tests table in quickly calculating how many test scripts passed testing. Also, you may create a separate grid view for every test case you have.

Fields

• ID. An autogenerated primary key that serves as the unique identifier for this test step record or row.
• Test case ID. This field is linked to the Tests table, indicating the test case this test step is for.
• Step no.. This is a number field specifying the test step number for this test script for sorting purposes.
• Project. This field is a lookup field based on this record’s Test case ID field, specifying the related project for this test script.
• Description. This is a clear and detailed description of the specific testing step required to be executed for this test script following the order of execution specified in this record’s Step no. field. You may include step requirements and criteria in this description.
• Expected result. This field supports the Description field by defining the specific output this test step is expected to return.
• Is pass. This is a checkbox field indicating whether this test step meets the data in the Expected result field or whether this test step fails. If this test step passed, tick the checkbox. Otherwise, leave this field blank or empty.
• Actual result. This is a brief description of the actual result after performing the test step described in the Description field.
• Notes. This field supports this test step’s expected and actual results while identifying additional defects, comments, or enhancements related to this test step.
• Tester. This field is a lookup field based on this record’s Test case ID field, specifying the user or tester performing this test script.
• Attachments. Any technical documentation can be uploaded and attached to this test. You may include your test plans, error logs, or other technical documentation or files related to this test step.
• Date created. This is an automatically filled-in date indicating the date and time this test step was created.
• Date modified. This is an automatically filled-in date indicating the date and time this test step was updated.
• Group bgcolor. This is a formula field that is used to automatically assign group colors to test scripts. These group colors are used as group background colors to make it easy to tell which test script groups are which. This field is hidden by default.
• Test case for sorting. This is a formula field used for sorting test scripts together based on this test step’s Test case ID field. This field is hidden by default.

Views

• All scripts. Displays all test scripts and test steps without filters, sorted by Test case for sorting and then by Step no.
• TC00001. Displays the test script with all the test steps for the test case with a test case ID equal to TC00001, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00002. Displays the test script with all the test steps for the test case with a test case ID equal to TC00002, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00003. Displays the test script with all the test steps for the test case with a test case ID equal to TC00003, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00004. Displays the test script with all the test steps for the test case with a test case ID equal to TC00004, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00005. Displays the test script with all the test steps for the test case with a test case ID equal to TC00005, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00006. Displays the test script with all the test steps for the test case with a test case ID equal to TC00006, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00007. Displays the test script with all the test steps for the test case with a test case ID equal to TC00007, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00008. Displays the test script with all the test steps for the test case with a test case ID equal to TC00008, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00009. Displays the test script with all the test steps for the test case with a test case ID equal to TC00009, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00010. Displays the test script with all the test steps for the test case with a test case ID equal to TC00010, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00011. Displays the test script with all the test steps for the test case with a test case ID equal to TC00011, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.
• TC00012. Displays the test script with all the test steps for the test case with a test case ID equal to TC00012, sorted by Test case for sorting and then by Step no. This view is specifically created for a certain test case and it can be shared with the respective client for test execution.

Users

This table holds all testers from both your clients and your company, since there were times when both parties had to test the test cases. A couple of formulas were provided to calculate the total number of test cases and the acceptance rate for each record. When the left border of a row is red, it means that less than 50% of the assigned test cases in the Tests table were accepted or approved.

Fields

• Name. This is the user’s full name.
• Photo. This is the user’s photograph.
• Role. This is a single select field specifying the user’s role in this UAT, whether the user is the product manager, QA manager, QA tester, or client’s tester.
• Company. This field is linked to the Clients table, indicating the company or client this user belongs to.
• Phone number. This is the user’s current phone number.
• Email. This is the user’s current email address.
• Tests count. A formula field that counts the total number of test cases this user has in the Tests table.
• Tests accepted (%). This is a formula field that rounds and formats the output value of this record’s Percentage for filter field.
• Percentage for filter. This is a formula field that computes the percentage of related test cases in the Tests table that passed and were accepted by the intended users or clients. This field is also used as a filter criterion for this table. This field is hidden by default.
• Notes. This field holds notes or remarks about this user.
• Is active. This is a boolean field specifying whether this user is currently active or not.
• Related tests as manager. This field is linked to the Tests table, specifying the test cases where this user serves as the QA manager who creates and supervises the related test cases. This field is hidden by default.
• Related projects. This field is linked to the Projects table, indicating the projects this user is managing or leading. This field is hidden by default.
• Related tests as tester. This field is linked to the Tests table, specifying the test cases that this user serves as a tester for. This user can either belong to your organization or the client. This field is hidden by default.

Views

• All users. Displays all users without filters, sorted alphabetically by Name from A to Z.
• With all tests accepted. Displays users with test cases that are all accepted and approved by the client, sorted alphabetically by Name from A to Z.
• With incomplete tests. Displays users with test cases that are not yet accepted or approved by the client, sorted alphabetically by Name from A to Z.
• Without tests. Displays users without assigned test cases, sorted alphabetically by Name from A to Z.
• Users gallery. Displays a gallery view of all active users in the database, sorted alphabetically by Name from A to Z.
• Add a user. Displays a form view that facilitates adding users to this table.