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
  • Welcome to testgrinder! - A short video showcasing its key features.

Was this helpful?

Overview

NextTesting

Last updated 1 year ago

Was this helpful?

testgrinder service will be discontinued on January 31, 2025

testgrinder automates Maximo by interacting with it just like a human would - solely through the Maximo UI (user interface) by moving the mouse, clicking buttons, entering field values, etc. - by following the steps in scenarios you provide and reporting the outcome in a run report complete with screenshots and video. It is great for:

Welcome to testgrinder! - A short video showcasing its key features.

You write testgrinder scenarios in steps that sound like natural language, which makes the scenarios easy to follow by anyone familiar with Maximo. As an example, here's a scenario that creates a new Maximo asset and changes its status to ACTIVE:

Scenario: Assets - Actions - Change Status - Active

Given I login to Maximo as User
  And I go to the Assets / Assets application
  And I click the 'New Asset' toolbar button
  And I enter 'Test Asset' in the description field of the Asset field
  And I successfully save the record
    
 When I select action 'Change Status'
  And I select Active in the dropdown list for the 'New Status' field
  And I click the OK button
    
 Then I see the value ACTIVE in the Status field
  And I logout

Once you kick off a run, you may watch it execute in real time. As scenarios execute, testgrinder compiles a run report including screenshots for every step as well as a video for each of the scenarios. You may share a run report with others if you choose to do so. Here's the run report for the above scenario:

As testgrinder executes a run, it will employ several tgBots, each running one scenario at a time. This allows scenarios to run in parallel, greatly reducing the total runtime. For example, a run with about 200 scenarios, totaling over 6,000 steps, being executed on 50 tgBots will take about ten minutes to complete. For comparison, if such a task were to be done manually in Maximo, it would require dozens of man-hours.

Welcome to testgrinder!
testgrinder run report