Overview
testgrinder is a tool for automating IBM Maximo tasks such as user acceptance testing, regression testing, stress testing, initial data loads, data updates, data verifications, recording of training videos, consistent change deployment across environments, and others. testgrinder executes scripted scenarios as a human would, by interacting with Maximo through a web browser. testgrinder moves the cursor, clicks buttons, and enters data just like a real user would, while also taking screenshots and recording video of the entire interaction. Along with the testgrinder Application Server (tg-app) AMI you will need to subscribe to the testgrinder Script Runner Server (tg-bot) AMI to complete a testgrinder deployment. See more at https://docs.testgrinder.com/
Highlights
- automated user acceptance, performance, and stress testing of IBM Maximo
- performing initial data loads, data updates, data verifications in IBM Maximo
- recording of training videos for IBM Maximo
Details
Typical total price
$1.038/hour
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Instance type | Product cost/hour | EC2 cost/hour | Total/hour |
---|---|---|---|
t2.medium | $1.00 | $0.046 | $1.046 |
t2.large | $1.00 | $0.093 | $1.093 |
t3.medium | $1.00 | $0.042 | $1.042 |
t3.large | $1.00 | $0.083 | $1.083 |
t3a.medium Recommended | $1.00 | $0.038 | $1.038 |
t3a.large | $1.00 | $0.075 | $1.075 |
m3.medium | $1.00 | $0.067 | $1.067 |
m3.large | $1.00 | $0.133 | $1.133 |
m5.large | $1.00 | $0.096 | $1.096 |
m5a.large | $1.00 | $0.086 | $1.086 |
Additional AWS infrastructure costs
Type | Cost |
---|---|
EBS General Purpose SSD (gp2) volumes | $0.10/per GB/month of provisioned storage |
Vendor refund policy
refunds limited to the first 14 days of subscription
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
- A bug that limited the number of launched bots was fixed.
- The requirements for subnets to assign public IP addresses were removed.
- The FORCE_SSL configuration file parameter was added. When set to false, testgrinder will respond over HTTP. When set to true (or not specified), HTTP requests will be redirected to HTTPS. When testgrinder is launched without user data, FORCE_SSL will default to false to allow interaction until the SSL certificate is configured.
- The export-user-data script was added for exporting configuration files in the User Data format as described in the testgrinder documentation.
- testgrinder bots will now self-terminate if abandoned by testgrinder.
- The MONIT_NOTIFY_FROM_EMAIL configuration file parameter was added, allowing you to specify the email address that will appear in the "From" field of Monit notification emails.
- The stop, start, and status scripts were added for stopping, starting, and checking the status of all testgrinder services.
- The .sh extension was removed from the restart.sh script.
- A delay was added to the starting of testgrinder services until provisioning completes.
- The delay in background jobs posting logs to Papertrail was reduced.
- The number of Delayed Job workers was reduced to 3 from 4.
Additional details
Usage instructions
=== Upgrade Notes ===
- Add 'FORCE_SSL: false' to .env configuration file if you wish for testgrinder to respond to HTTP requests rather than forcing redirection to HTTPS
- Specify MONIT_NOTIFY_FROM_EMAIL in .env configuration file to have Monit use this email in From: field for emails it sends
=== Upgrade Instructions ===
- Backup the database (https://docs.testgrinder.com/smpc/backup-and-restore-database ).
- If the database is hosted on a tg-app server, copy the backup to a secure location.
- Use the export-user-data script to export the existing tg-app configuration files in the User Data format (https://docs.testgrinder.com/smpc/testgrinder-configuration/configuration-files ). Copy the user data to a secure location.
- Stop the old tg-app server.
- Modify the .env configuration file in the user data as described in the Upgrade Notes.
- Launch a new tg-app server (https://docs.testgrinder.com/smpc/deployment-instructions/tg-eval-deployment-steps/launch-tg-app ) using the user data - this will recreate the configuration files on the new server.
- Restore the database from the backup file (https://docs.testgrinder.com/smpc/backup-and-restore-database ).
- Update the following database settings (https://docs.testgrinder.com/smpc/testgrinder-configuration/database-stored-settings ):
- aws_runner_image_id: set to the new tg-bot AMI ID.
- tg_api_url: update with the new tg-app server private address.
- Test the new server to ensure it is functioning properly.
=== Initial Deployment ===
- Choose or create a VPC for testgrinder (https://docs.testgrinder.com/smpc/deployment-instructions/virtual-private-cloud )
- Create security groups for tg-app and tg-bot (https://docs.testgrinder.com/smpc/deployment-instructions/security-groups )
- Create S3 buckets (https://docs.testgrinder.com/smpc/deployment-instructions/s3-buckets )
- Create IAM roles for tg-app and tg-bot (https://docs.testgrinder.com/smpc/deployment-instructions/iam-roles )
- Choose or create a key pair (https://docs.testgrinder.com/smpc/deployment-instructions/key-pair )
- Launch tg-app (https://docs.testgrinder.com/smpc/deployment-instructions/launch-tg-app )
- Use a web browser to access testgrinder at https://<EC2_Instance_Public_DNS> ;
- Finalize configuration files (https://docs.testgrinder.com/smpc/deployment-instructions/finalizing-configuration-files )
- Finalize database stored settings (https://docs.testgrinder.com/smpc/deployment-instructions/finilizing-database-stored-settings )
- Follow the first steps guide to get started using testgrinder (https://docs.testgrinder.com/getting-started/first-steps )
- Contact support@testgrinder.com for assistance
=== Monitoring health of tg-app and tg-bot servers ===
- Navigate to your Amazon EC2 console and verify that you're in the correct region.
- Choose Instance and select your launched instance.
- Select the server to display your metadata page and choose the Status checks tab at the bottom of the page to review if your status checks passed or failed.
- ssh into tg-app to monitor individual components as described in https://docs.testgrinder.com/smpc/monitoring
=== Security notes ===
- Most user provided data is stored in the MongoDB database which is either located on tg-app server (if you choose so) or in an external MongoDB database provided by you. Screenshots and videos recorded during script runs are stored in the S3 buckets that you setup for testgrinder. You may choose any encryption scheme offered by AWS for S3 buckets.
- Sensitive data stored in the MongoDB database is encrypted using keys provided in .env configuration file (https://docs.testgrinder.com/smpc/deployment-instructions/finalizing-configuration-files/configuration-file-.env )
- tg-app servers use an SSL certificate provided by you; follow the steps in https://docs.testgrinder.com/smpc/deployment-instructions/finalizing-configuration-files/ssl-certificate to install or update it
Resources
Vendor resources
Support
Vendor support
assistance with testgrinder deployment support@testgrinder.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.