You can use this user acceptance testing (UAT) list as a guide to check for issues after you install or upgrade Domino. You can also use this list to help establish your instance’s baseline functionality before an upgrade.
Each item in the list pertains to a Domino feature and its expected behavior. Treat these items as suggested tests to confirm that the feature works correctly.
|
Note
| Some of the test items might not apply to your Domino instance. For example, you might only have Domino File System projects, but the list includes items about Git-based projects. Modify the list to address your organization’s needs. |
-
Access the executions page to view pods, node details, and deployment logs for an execution.
-
Stop a test execution.
-
-
Access the infrastructure page to view a list of currently active compute and platform nodes.
-
Verify that the number of compute and platform nodes on the infrastructure page matches the intended solution design.
-
-
Verify that user activity reports are set up.
-
Set Central Configuration flags that match your organization’s needs. For example:
-
Send a license usage report is sent to usage@dominodatalab.com.
-
Configure the maximum number of simultaneous executions per user.
-
-
Access the workspaces page as an administrator.
-
Access the control center and verify that the metrics display as expected.
-
Verify that users and organizations receive in-app system notifications.
-
Verify that the following events trigger an email notification:
-
Create a new user account or sign in with single sign on (SSO) to your Domino instance.
-
Access your Domino instance from a user account and verify that pages load correctly.
-
Verify that you can access the following as a user:
-
Install the Domino CLI.
-
Sync a project from the Domino CLI.
-
Execute a batch run from the Domino CLI, and verify that results sync with your local machine.
-
Create a new compute environment and verify that it builds successfully and pushes the associated image to Domino’s Docker registry.
-
Add a new package and build a new compute environment.
-
Add pre-run, post-run, pre-setup, and post-setup scripts and verify that they execute when you perform a run.
-
Start a session in each of the following and execute code:
-
Upload files to create Datasets and snapshots.
-
Verify that shared Datasets and snapshots are mounted in a project.
Connect to Data Sources that your organization uses.
-
Create a Git-based project.
-
Switch branches in the workspace via file changes workspace UI option.
-
Resolve merge conflicts manually in Domino and push code to a remote repository.
View the following:
-
Workspace logs.
-
Execution logs.
-
Model API logs.
-
Setup logs for workspaces and runs.
-
User output logs for workspaces and runs.
-
Publish a model API.
-
Send test calls to the model API.
-
Use workspace checkpoints to open a previously published Model API version in a workspace.
-
Create a new project.
-
Upload files to a project from a project’s Files Tab.
-
View the files page and verify that files render.
-
-
Revert a project’s files to a previous commit.
-
Add a Git repository to the project.
-
Commit, push, and sync with a Git repository.
-
Edit the volume size and launch new workspaces with the updated volume.
-
Verify that results from the following actions sync back to Domino:
The following items require that you first create the respective workspace and cluster compute environments.
Attach the following to a workspace or job:
-
Start a Python Flask app and publish it from Domino.
-
Verify that Domino creates a shareable link to the app.
-
-
Start a R Shiny app and publish it from Domino.
-
Verify that Domino creates a shareable link to the app.
-
-
Verify that environment variables are visible and available in workspaces.
-
Start a Jupyter workspace and execute Python code.
-
Verify that results sync back to Domino.
-
-
View the following from the workspace settings page:
-
Start a workspace in a Domino File System project, sync a new file, and stop the workspace. Verify that you can perform the following:
-
View the history of the workspace and the file state.
-
Open a new workspace with a new branch from a previous commit.
-
In the files section of the project, view the branch name you created in the previous test.
-
-