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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Additional error handling functionality for unattended test runs
As originally discussed on the forums, it was suggested to submit a RFE. (https://www.ibm.com/developerworks/community/forums/html/topic?id=7c067db9-35f8-4936-8d86-c29d9848a9e8)
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.
Do not place IBM confidential, company confidential, or personal information into any field.