Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Performance Tester
Created by Guest
Created on Aug 22, 2019

Additional error handling functionality for unattended test runs

As originally discussed on the forums, it was suggested to submit a RFE. (

We are looking for a solution to automatically stop/exit the test when run via schedule if it reaches a certain level of failures. In Performance Requirement there is an option for this but no option to add an action if it falls below a threshold. Likewise in the Error Handling tab it does not show an option for test level, only iteration level actions.

One way to handle this could be to trigger an exit based on a net total of errors instead of percentage. Having a variety of parameters to choose from would give us the flexibility to design this exit based on specific status codes (e.g. unhealthy page count, 500s, VP failures, etc.). Also, selecting what time frame should be measured (e.g. full test, moving time frame), and what happens when the threshold is reached (e.g. exit test, exit/kill agent).

Currently, we would like to have an option to exit the test for unhealthy number of pages up to either a certain number of failures total or during a specific time frame.
We'd be happy to discuss/brainstorm ideas with your team.

Idea priority High
RFE ID 135525
RFE Product Rational Performance Tester
  • Guest
    Jun 16, 2022

    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The offering team has carefully reviewed this idea and has decided that it does not fit into our current plans, so the idea will be closed. The idea will be kept in IBM's ideas repository and may still be voted on. It might be reassessed or reopened for additional feedback in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Feb 4, 2020

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Oct 21, 2019

    Following up again on the meeting to discuss design of this feature.

  • Guest
    Sep 4, 2019

    Our team would be happy to work with you to discuss design. Feel free to set up a conference call to discuss further.

  • Guest
    Sep 3, 2019

    We are interested in pursuing this capability and would like to engage with you for a design thinking session to ensure we fully implement what is required in a manner that is useful to yourselves and others.