Skip to main content

Account

The Account tab is only available for the Owner of the Testspace organization. There are two sub-tabs on the Account tab: Plan and Services.

Plan#

The Plan tab provides information regarding:

  • Plan - current plan subscribed to with options to upgrade or downgrade;
  • Payment - a method for payment
  • Owner - which can be changed to another Admin User.
  • Settings - allowable changes to the Organization "friendly" name and/or the subdomain.
  • Cancel - selection to terminate the account.
  • Receipts - list of existing payment receipts.

A Testspace Open plan must be connected to a public GitHub organization, Bitbucket team, or a GitLab group.

Change plan#

The organization owner can upgrade or downgrade the current account plan. Credit card information is required if upgrading from an Open to a Paid organization.

  • Select the Account tab at the organization level (top right)
  • Select the Plan sub-tab
  • Select the Change plan button to the right.

Change card#

The Owner can change the credit Car payment method at any time.

  • Select the Account tab at the organization level (top right)
  • Select the Plan sub-tab
  • Select the Change card button to the right
  • Update the credit card information in the secure form and SUBMIT

Change owner#

The organization owner is the single user with full Owner Permissions. The owner can transfer ownership to another admin user only in the organization.

Once you change ownership you will not be able to view the Account tab

  • Select the Account tab at the organization level (top right)
  • Select the Plan sub-tab
  • Select the Change owner button to the right
  • Select the new owner from the drop-down list of users and SUBMIT.

A change of ownership email will be sent to both the previous and new account owner confirming the change.

Change settings#

The settings allow changing:

  • Organization friendly name
  • Subdomain

Cancel#

The organization owner can cancel the account at any time.

When canceling your account plan, all project information will be immediately and permanently deleted. Refer to the Testspace refund policy.

  • Select the Account tab at the organization level (top right)
  • Select the Plan sub-tab
  • Select the Cancel button to the far right
  • Select the Confirm button to confirm cancellation

Services#

The Services tab manages 3rd party integration. There are three repository based connected services supported: GitHub, Bitbucket, and Gitlab. Testspace also integrates with AWS Lambdas for automated fixturing.

The Testspace account Owner can connect and disconnect to these services at any time.

Services

It is important to note that login credentials are not necessarily the same as the Connected Services credentials. Because Testspace also works as a standalone application, login credentials are viewed independently. For example, a user (owner in this example), could be using Bitbucket credentials to log in, and at the same time using Connected Services with GitHub.

Disconnect#

The Testspace owner can disconnect at any time.

The following disconnection and deletion rules apply to respository based 3rd party services (i.e. GitHub):

  • disconnects from a hosting service, all projects connected to that service will be converted to standalone
  • disconnects from a repo organization, all projects connected to that organization will be converted to standalone.
  • deletes a repo organization, all projects connect to that organization will be converted to standalone.
  • deletes a repository, the single project connected to that repository will be converted to standalone.

Reconnect#

There are several scenarios where you may need to reconnect Testspace to a service.

  • The user account that is linked must be changed. In this case, while logged in the desired repository user account click on the reconnect button. Note that in this scenario if the new user account does not have required access to a particular repo, it will be converted to standalone.
  • If the permissions level to the repository needs to be updated.

GitHub#

An Testspace owner can install Testspace.com to a GitHub organization. If the Testspace owner is a member instead of an owner they can still connect, which will generate an installation request to the owner(s).

GitHub Organizations

To run a Github Action from Testspace a Github token is required that has repo access. This one time only step is required to be added to your Testspace account services.

Add GitHub token

Connection problems#

In the event of a GitHub service connection problem, the following steps are required:

GitHub Connection Problem

  • Select the Account tab on the far right corner of the projects listings page
  • Next, select the Services sub-tab
  • Select the Reconnect button

GitHub Reconnect

  • After generating a new service token you will be redirected to GitHub
  • For some situations, the Save button is not highlighted. If this is the case, select another option once (i.e. Only select repositories) and then re-select your preference. The Save button will be highlighted for your selection.

You will be redirected back to Testspace. Note that in some cases the desired GitHub organizations will be required to be enabled using Testspace:

  • Select the Account tab on the far right corner of the projects listings page
  • Next, select the Services sub-tab
  • Select the GitHub organization(s)

Testspace GitHub Organization selection

Bitbucket#

For Bitbucket - if the Testspace owner is in a user group that has admin privileges to the Bitbucket organization they can connect as well.

GitLab#

For GitLab - if the Testspace owner has admin privileges as a member of a GitLab group, they can connect.

AWS#

When using manual testing automated fixtures, that leverage ASW Lambdas, an access key is required. The keys require at least the minimum permission to invoke lamdas, such as the AWSLambdaRole, which is the default policy for the AWS Lambda service role.

  • Select AWS Connect
  • Provide both the Access key ID and the Secret access key

Refer to AWS access keys for more information.

Note that for a lambda function themselves the Execution role that has permission to upload logs to Amazon CloudWatch Logs (i.e. lambda_basic_execution) is recommended.