Troubleshooting TrueTest issues

This document lists out all the common issues and solutions you can encounter when setting up and using TrueTest. You can look for the troubleshooting with the corresponding error code.

02-03-0014

You are unable to generate user journey map.

This error happens when:

• the data collected by TrueTest agent is insufficient
• the created user sessions are too simple to generate a map.

For example, if the application under test is just one static page, the user session created on that page will be simple.

Create user sessions on dynamic pages, ensuring that the sessions are complex enough to generate a journey map.

04-06-0015 & 04-06-0025

TrueTest is unable to push generated test artifacts into the integrated Git repository.

This error happens due to the following reasons:

• The Personal Access Token (PAT) of the Git repository is expired

• The Git URL format is not supported

• If the PAT has expired, you need to generate a new one and add it to the Script Repository settings in TestOps. See Configure a Git repository in TestOps.
• If the URL format is not supported, you need to use the format that TrueTest supports. The correct format should look like https://dev.azure.com and does not include your username.

04-06-0035

Failed to clone the script repository due to incorrect credentials.

When configuring script repository in TestOps, you can input email or Git username in the Username field. However, TrueTest Agent cannot commit test cases to a script repository with an email form username.

To work with TrueTest, you need to edit the integrated script repository with a Git username instead of email form username.

04-06-0045

Personal Access Token is not granted with WRITE permission.

TrueTest Agent failed to generate user journey map.

The agent failed to generate test cases because it was not able to commit the tests to the repository.

To generate and store test cases, TrueTest Agent requires Write permission to the configured Git repository. When setting up test environment for the agent, you need to link a Git script repository with Write permission.

If your Git script repository is not configured with Write permission, you need to reconfigure the script repository's personal access token with Write permission. See: Configure a Git repository in TestOps.

The following are some specific examples of Write permission configuration for different Git providers.

• GitHub personal access token: you need to provide the repo:status scope. See: GitHub available scopes.
• GitLab personal access token: you need to assign the write_repository scope. See: GitLab personal access token scopes.
• Atlassian Bitbucket Repository Access Token: you need to provide the repository:write permission. See: Bitbucket Repository Access Token permissions.
• Azure DevOps access token: you need to provide the vso.code_write scope. See: Azure DevOps access token scopes.
• AWS CodeCommit Git credentials: you need to create an IAM policy with write access to repository. See: AWS managed policies for CodeCommit.

04-06-0055

Failed to push test artifacts to a protected git branch.

The TrueTest agent cannot push and commit generated test artifacts to a protected git branch although the Personal Access Token has been granted with WRITE permission.

Set the git branch to non-protected or select a different non-protected git branch.