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

Was this helpful?

  1. testgrinder uses
  2. Testing

User Acceptance Testing

PreviousTestingNextChange Testing

Last updated 1 year ago

Was this helpful?

testgrinder service will be discontinued on January 31, 2025

User acceptance testing is an essential step in making Maximo available for production use. Automating user acceptance testing is not a simple task as in order for the test results to be credible, the user community needs to validate and accept the test method as valid. If you write user acceptance tests in a cryptic programming-like language, it will create obstacles to the users acceptance of the validity of such tests. testgrinder solves this problem by allowing you to write test scenarios in an easy to understand language. Take this testgrinder script as an example:

Script: Assets - Actions - Change Status
 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

The combination of easy to read test scenarios, screenshots taken for every executed step, and a recorded video for the entire interaction, testgrinder makes tests trustworthy and acceptable for the Maximo user community:

Or see the report in testgrinder here:

https://testgrinder.com/runs/637c06eb97ed05045e54841d