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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
From version 10.2.2 a new configuration option within test suites is available to control the verbosity of logging, this can also be over-ridden on the command line for use in CI/CD pipelines.
Hi,
The request is to provide an option to turn off test logging to result database like stubs.
In order for us to correctly understand your requirements would it be possible for you to answer the following questions:
1. You are asking to be able to turn off results database logging for some Test Suites in a project but not others, is this a setting that you expect to see on the test suite itself?
2. Alternatively, is this a mode of execution to be selected at the point where the test is launched, either as an option when running or as a preference within the tool?
3. Do you need this to be available from other places such as the command line when using RunTests?
Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.
We also struggle with maintenance of our results DB.
Our current approach is to wait for it to fill up and everything comes crashing to a halt, then we remove EVERYTHING, so we have no log of recent results data and go again. We're lucky that we got allocated some significant disk space to extend our Tablespaces onto, so this tends to happen about once every 5 or 6 weeks.
Housekeeping routines using IntegrationTester.cmd (or .exe or whatever) do not seem to work.