testgrinder
Go to testgrinder
  • Overview
  • testgrinder uses
    • Testing
      • User Acceptance Testing
      • Change Testing
      • Regression Testing
      • Performance Testing
      • Stress Testing
    • Data management
      • Data verification
    • Configuration management
    • Training videos development
  • Getting Started
    • Video: Get Started with testgrinder
    • First steps
    • Example Scripts
    • Writing your first scenario
    • Scenarios
    • Run reports
  • Writing Scenarios
    • Anatomy of Maximo UI
      • Maximo login page
      • Start Center
      • Application Screen
      • Value lists
      • Advanced Search
      • Targeting fields with no labels
    • Finding the right steps
    • Step autocompletion
    • Scenarios vs Scenario Outlines
    • Snippets and Templates
      • testgrinder Templates Project
      • testgrinder Snippets Project
  • Examples
    • Interacting with electronic signature dialog
    • Automated granting of application access
    • Add a job plan
    • Add an item
    • Add an item to storeroom
  • Administration
    • Accessing Maximo behind a firewall
    • Managing User Access
    • Using Git to Back Up and Version Control testgrinder Projects
  • Self Managed Private Cloud (SMPC)
    • testgrinder SaaS vs testgrinder SMPC
    • Releases
      • Version 1.0.8
      • Version 1.0.0
    • testgrinder Architecture
    • testgrinder Configuration
      • Configuration Files
      • Database Stored Settings
    • Deployment Instructions
      • Prerequisites
      • Subscribing to testgrinder on AWS Marketplace
      • Virtual Private Cloud
      • Security Groups
      • S3 Buckets
      • IAM Roles
      • Key Pair
      • Launch tg-app
      • Finalize Configuration File .env
      • Finalizing Database Stored Settings
      • Minimal Deployment Complete
      • Install SSL Certificate
      • Force HTTP to HTTPS
      • External Database
      • Configure Auto Scaling Group
        • Target Groups
        • Load Balancers
        • Launch Template
        • Auto Scaling Group
        • Finalize Auto Scale Group Deployment
    • Test the Deployment
    • Monitoring
    • Backup and Restore Database
Powered by GitBook
On this page
  • testgrinder service will be discontinued on January 31, 2025
  • testgrinder SMPC was discontinued as of February 1, 2024
  • AWS Account
  • SMTP Server
  • testgrinder Domain Name and Elastic IP Address
  • Key Pair
  • External Database
  • Papertrail Integration
  • Bugsnag Integration

Was this helpful?

  1. Self Managed Private Cloud (SMPC)
  2. Deployment Instructions

Prerequisites

testgrinder service will be discontinued on January 31, 2025

testgrinder SMPC was discontinued as of February 1, 2024

This page provides a list of the necessary prerequisites that will be required during the deployment of testgrinder.

AWS Account

REQUIRED

testgrinder is designed to run on Amazon Web Services platform. You will need to have an account with AWS to deploy testgrinder.

SMTP Server

REQUIRED

testgrinder requires a way to send emails to its users. You can use your own SMTP server or the AWS Simple Email Service (SES) for this purpose. In either case, testgrinder will need the following configuration items:

SMTP_HOST:      SMTP server host, e.g. email-smtp.us-east-1.amazonaws.com
SMTP_PORT:      SMTP server port, e.g. 587
SMTP_USERNAME:  SMTP username, e.g. my-username
SMTP_PASSWORD:  SMTP password, e.g. my-password

testgrinder Domain Name and Elastic IP Address

REQUIRED

To use testgrinder, you'll need to select and register a domain name with your DNS server, such as Route53 provided by AWS. You'll also need to allocate an Elastic IP (EIP) address and assign it to the domain name. If you're using an Auto Scaling group to manage tg-app instances, you may want to consider assigning a dedicated EIP to each availability zone for improved fault tolerance. Once you've completed these steps, testgrinder will be able to respond to requests made to the specific domain name you've chosen.

DOMAIN_WEB:  domain name for testgrinder to respond to, e.g. tg.my-company.com
EIP:         Elastic IP that will be assigned to testgrinder   

Key Pair

REQUIRED

To set up and monitor testgrinder servers, you will need to specify the Key Pair that you will use when launching the servers.

KEY_NAME:    name of the Key Pair in AWS EC2 to which testgrinder servers will allow access

External Database

RECOMMENDED

MONGODB_URL:    the URI to the external database

Papertrail Integration

OPTIONAL

PAPERTRAIL:    the endpoint supplied to you by Papertrail

Bugsnag Integration

OPTIONAL

BUGSNAG_API_KEY:    Bugsnag API Key provided to you by Bugsnag
PreviousDeployment InstructionsNextSubscribing to testgrinder on AWS Marketplace

Last updated 1 year ago

Was this helpful?

To use testgrinder, a MongoDB database is required. If you're just evaluating testgrinder, a preinstalled database is provided for you. However, this preinstalled database is not intended for production use. The deployment instructions will guide you on how to subscribe to a MongoDB database hosted by or provide your own database.

To use this feature, you will need to sign up for a account and obtain the necessary log destination information. Once you have this information, you can configure testgrinder servers to send their logs to Papertrail by including the log destination information in the testgrinder configuration files. This will allow you to easily collect, search, and monitor all testgrinder logs in one place.

testgrinder can send issue reports to , allowing you to instantly receive notification of any problems that occur during operation and receive detailed information to help resolve them.

mongodb.com
Papertrail
Bugsnag