Create automated tests with the Nextworld recording tool
Application developers use the Nextworld recording tool to log their own interactions with applications. These interactions are saved as test steps that can later be performed by a simulated user in an automated test.
While you're recording, the recording sidebar displays your user interactions with the platform as you perform them. These interactions are listed as test steps. You can edit steps, delete steps, add system steps, and more from the recording sidebar. Then, you can save your recording to create a test action, update test designs, and more.
There are multiple ways to start recording:
- Temporary Tenants - Test application—Select the Record in New Tab row action on the temporary tenant you want to record in. This automatically signs you into the tenant and opens the recording sidebar.
- Test Design Definitions application—Navigate to the case objective you want to automate and select the Record in New Tab row action to specify a temporary tenant to sign into and begin recording. This method includes the case objective details in the recording sidebar. Select the checkboxes next to each essential validation as you record them to indicate that they're covered by an automated test when you save your recording.
- User Profile menu—Turn on the Automation Recording toggle on the Settings page of the User Profile menu to begin recording in the current environment.
Add systems steps and validations
Use the recording tool to add system steps, which are steps in an automated test that don't involve a user interaction with the user interface.
The following system steps are available as form or row actions in applications when you are recording:
- Validate Model Values— Opens a window where you can select the fields you need to be validated by the automated test. You can validate field values, whether fields are hidden or disabled, and more. Before validating field values, check to make sure that they are actually the values you expect. When an automated test runs, it attempts to validate whatever the value was when you validated the fields while recording.
- Wait for Workflow— Prevent the automated test from continuing until the workflow state transitions. You can select multiple records and then use the Wait for Workflow row action to prevent the automated test from continuing until all selected records transition.
The following system steps can be added from the recording sidebar:
- Wait for Async Operations to Finish—Prevent the automated test from continuing until all background jobs triggered by the simulated user are complete. By default, the test fails after 30 minutes if the jobs are not complete, but you can customize the time limit with Action Options.
- Wait for Condition—Prevent the automated test from continuing until a condition is met. For example, a condition could be a specific number of records in a table, or a specific value in a field.
- Set to Ignore Errors—Prevent the automated test from failing when an error message displays. This step allows you to validate that error messages display after a user takes a particular action.
- Set to Fail on Errors—Cause the automated test to fail when an error message displays. Always add this step after you validate an error message to ensure that any errors you're not actively testing cause the test to fail if they occur.
Save your recording to create test actions, update test designs, and more
When you save your recording from a personal tenant, the test steps you recorded are exported to a new or existing record in the Test Action Definitions application in your development environment. If you specify an existing test action, test steps are appended after any other test steps.
You can also create or update other automated testing records with the data from your recording when you save, including:
- Test flows—Specify an existing test flow definition to automatically append the test action to the end of the test flow.
- Test designs and case objectives—Specify an existing test design and case objective combination to update the case objective with any essential validations and pre-validation actions you've included in the recorded test steps. You can also create a new test design and case objective. Only the essential validations and pre-validation actions in the case objective include the data from your recording, so you must manually update the case objective details, business context, and more in the Test Design Definitions application.
You don't have to specify test flows or test designs when you save your recording. You can leave these fields empty and either select Save and Next for more options, or export to the test action.
Environment considerations
Automated tests always run in a new temporary tenant. You should always use the recording tool in a temporary tenant so that the data you interact with is the same as the data in the tenant the automated test is run.
Be aware of the data in the temporary tenants you sign into to record your test actions. All test actions and test suites run in a new temporary tenant by default. However, test actions that are part of a test suite run in sequence in the same personal tenant.
For example, you may have two test actions, one to delete a record, and one to edit that same record. Both actions pass when you submit them individually because they run in separate temporary tenants. However, if the actions run as a part of test flows in a test suite, the order of the actions matters. If the action to delete the record comes first, the test suite fails on the action to edit the record. This means you may have to prepare the data in the temporary tenant before you start using the recording tool to create test actions that are later in the sequence within the test suite.
Review automated test results
Application developers use multiple applications to review the results of their automated tests. Use the Test Results Inquiry application to examine automated test failures in detail. Use the Batch Job Metrics Inquiry application to examine overall results for batch submissions of your active test suites and find trends.
Investigate individual test results
Every time an automated test is submitted, either by an application developer or by a scheduled job, a record in the Test Results Inquiry application is created. These test results records contain the details of the test submission, including whether it passed, how long it took to complete, and more.
When a test fails, use the information included in the test results record to investigate the cause of the failure and then address it. Each failed test has a Failure Category that you can use to group failures and find trends. Failed tests also include the test step that caused the failure in the Console Log field so you can quickly pinpoint the cause of the failure. In addition, videos of each test action being performed by the simulated user are attached to the test results record.
Validate automated test configuration
In addition to investigating problems with your applications, use the Test Results Inquiry application to validate the design of your automated tests as you configure them.
For example, you might be configuring an automated test to validate an error message. If you forget to add the test step that is meant to cause the error, your automated test fails. In the Test Results Inquiry application, you can use the information in the Console Log field to determine that the test failed on the step that validates the error message. Then, you can use the attached video to see that the action meant to trigger the error wasn’t performed by the simulated user. After you add the appropriate test step to the test action and submit it again, the test passes.
Monitor batch submissions
After you schedule your active test suites to run on a regular basis, use the Batch Job Metrics Inquiry application to monitor them.
The Batch Job Metrics Inquiry application aggregates the test results from each batch submission into a central location. Use the application to view the data about your tests in different ways. You can see trends across all batch submissions, all the results for a single submission, the results of a single test suite across multiple batch submissions, and more. You can also navigate to individual test results records or test suites.
When a test suite that has been passing successfully in previous batch submissions fails, this can indicate a problem with the application. For example, a test suite for the Company Directory application might fail because there is a problem with the UI logic block that hides the Gender field when the Contact Type for a directory record is set to Organization. In the Batch Job Metrics Inquiry application, you can navigate to the individual test result record and see that the test step that caused the failure was attempting to validate that the Gender field was hidden. After you fix the logic block, the next submission of the test suite should pass, informing you that the Company Directory application is functioning as intended.
The Batch Job Metrics Inquiry application only shows the test results of active test suites that are submitted automatically by a scheduled job, or those that you submit manually with the Batch Submit form action in the Test Suite Definitions application. The results of individual test suites you submit manually are not included in this application. Learn more in Schedule automated tests.
Test Results Inquiry application
Application developers use the Test Results Inquiry application to validate the configuration of their automated tests and to investigate individual test failures in detail.
Each time an automated test action or test suite is submitted, a record in the Test Results Inquiry application is created. You can see how long the test took to complete, whether it passed, how many times it was submitted before, and more. Results for test suites include each test action that makes up the suite on the Details page.
When an automated test fails, use the Failure Category and the Console Log fields to investigate the failure. For more detail, each test results record with a Test Status of Failure has videos attached that correspond to each test action. Each video shows the simulated user performing the test action step by step so you can determine exactly what caused the test to fail.
Use the Test History action to see all the times this automated test was submitted, and the View Test action to navigate to the automated test and make changes as needed.
To view trends across test suite submissions and monitor your scheduled automated tests, use the Batch Job Metrics Inquiry application. Learn more in Review automated test results.
Batch Job Metrics Inquiry application
Application developers use the Batch Job Metrics Inquiry application to monitor their test suites for failures and to examine trends.
Each record in the Batch Job Metrics Inquiry application represents a batch submission of automated test suites. The list form displays a high level view of test results over time. The detail form displays all the test results for each test suite in a single batch submission. From the detail form, you can examine individual test results in detail, navigate to the test suites, or use the Suite History row action to view the results of a single test suite across batch submissions.
There are multiple types of batch submissions you may see in the Batch Job MetricsInquiry application:
- Scheduled batch submissions—After you schedule them, all of your active test suites are submitted in a single batch on a regular interval. Learn more in Schedule automated tests.
- Reruns—The test suites that fail in each scheduled batch submission are submitted again automatically after the scheduled batch submission is processed. Sometimes, automated tests fail due to problems outside of Nextworld. When a test fails in both the batch submission and in the rerun, there is an issue you need to investigate. Failed test suites are only submitted again for scheduled batch submissions.
- Manual batch submissions—Submit a single batch of test suites based on your criteria by using the Batch Submit form action in the Test Suite Definitions application.