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
  • Technology
  • tg-app servers
  • tg-bot servers
  • Monit
  • MongoDB database
  • S3 buckets
  • SMTP server
  • Integration with optional external services

Was this helpful?

  1. Self Managed Private Cloud (SMPC)

testgrinder Architecture

An overview of SMPC testgrinder architecture

PreviousVersion 1.0.0Nexttestgrinder Configuration

Last updated 1 year ago

Was this helpful?

testgrinder service will be discontinued on January 31, 2025

testgrinder SMPC was discontinued as of February 1, 2024

Major elements of a SMPC testgrinder deployment include:

  • tg-app servers - one or more testgrinder application servers

  • tg-bot servers - script runners dynamically launched by tg-app

  • MongoDB database

  • two S3 buckets

  • SMTP server for sending emails out

  • (optional) integration

  • (optional) integration

Technology

testgrinder is a application written in the programming language. It consists of two major components - the application server tg-app, and the script runner tg-bot, both built on top of Ubuntu linux. SMPC testgrinder consists of two AMIs (tg-app and tg-bot) on the AWS Marketplace. testgrinder uses as its database.

tg-app servers

At the core of testgrinder deployment is one or more testgrinder application servers (tg-apps). They are responsible for interacting with the users and managing the script runners (tg-bots).

If you are deploying testgrinder for evaluation, one tg-app server is adequate. For production, a more robust deployment utilizing at least two tg-app severs managed by an Auto Scaling Group is advisable.

tg-bot servers

When a run is kicked off in testgrinder, tg-app will launch (and later terminate) one or more tg-bot servers to handle scenario execution.

Monit

MongoDB database

S3 buckets

You will need to provide two S3 buckets for testgrinder. One for storing screenshots and videos generated during runs, and the other for storing testgrinder project user files.

SMTP server

You will need to provide testgrinder with an SMTP server which it will use for sending out emails. It can be Amazon SES (Simple Email Service).

Integration with optional external services

You may choose to integrate your deployment of testgrinder with the following optional services:

Both tg-app and tg-bot are equipped with for monitoring their health and attempting repair if need be. You may choose to receive email notifications whenever monit detects an abnormal situation or takes an action to remediate it.

testgrinder uses MongoDB as its database. tg-app comes with a MongoDB database preinstalled, which is adequate for testgrinder evaluation, but not advisable for production use. For production use, either provide your own instance of MongoDB, or sign up for one at .

- for aggregation of logs generated by tg-app and tg-bot instances

- for bug reports

papertrail.com
bugsnag.com
Ruby on Rails
Ruby
MongoDB
monit
mongodb.com
papertrail.com
bugsnag.com