Legal part

To use SaaS instance like <something>.testops.cloud you need to agree to the general terms and conditions (GTC) and the privacy policy and respect the conditions described on the initial instance request from.

Before you start using the service, we strongly recommend to read GTC and privacy policy, and consult with your legal advisor, if you can accept the said terms. If you proceed to the usage, then the GTC and Privacy policy are considered as accepted.

The GTC and privacy policy links are present in the instance request form.

If you did not read the documents, they are still applicable to the relations between all end-users of the requested instance and Qameta Software Inc.

If for some reason you skipped this step, please do familiarise with the said documents.

• General Terms and Conditions
• Privacy Policy

Technical part

Trial duration

• The trial period lasts 14 days, starting from the moment the instance is created. 
• After the trial, if no payment method (credit/debit card) is provided, the instance will be switched to a Read-Only state for 7 days. 
• If no payment method is provided during these 7 days, the instance will become suspended, meaning it will no longer be accessible to end users.

• To reactivate the suspended instance and continue using the service, the requester must file a request with the sales department and then provide a payment method in their account (payment terms and methods are managed via the Stripe UI).

• If the end user fails to provide payment details within 14 days after the instance is suspended, all data will be wiped, and it will not be possible to revive the instance.

Storage

• Storage is used to keep test results and test case artifacts (attachments).
• The storage is limited to 60 GB per instance.
• End users must enable cleanup rules to respect the limit of the dedicated storage.
• Currently, it is not possible to extend the storage.

Usage of the API

• End users can utilise the API of Allure TestOps
• End users must use the authentication method described in the documentation.
  • end users need to create one Bearer token for the whole API calls session.
  • end users need to use this single Bearer token for all API calls in the scope of one session.

Commercial terms

• Service is provided on a prepaid basis.
• The minimal commitment from the end user is 1 (one) month and 1 (one) paid seat.
• A seat represents 1 individual authorised to perform CRUD actions in the system. This includes:
  • Creation of entities (test cases, test plans, dashboards, test results).
  • Updating of the said entities.
  • Deletion of the said entities.
• One seat cannot be used by multiple people as this would violate the licensing agreement and could lead to the suspension of the service.
• Users can add team members with read-only access (Guests) on a complimentary basis.