Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 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 (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.

Status Not under consideration
Categories Test Execution
Created by Guest
Created on Jul 13, 2023

Is there a straightforward and clean way to create multiple Test case Execution Records with the same environment configuration in the same Test plan and iteration?

That would be for our regression TERs that are basically testing the same stuff .

One prime example of this is our Acceptance test, which is just a basic test for receiving new systems and getting them into test. There are no test environment requirements for these tests and we could run many within the same day/week so we couldn't put these into iterations even if we wanted to.

For acceptance for example, each TCER is intended to track the execution of one system, so we need one by system.
we use just the TCER name for system and there are many systems per release, and every release they change, so it’s not something we would like to put on the environment

It sounds like combination of TE, iteration &TP unique is just a limitation, although not one I understand the reason for. Is it possible to request this limitation be removed in a future version? Is there a technical reason to have it in the first place?

Idea priority High
Needed By Quarter
  • Guest
    Reply
    |
    Jul 21, 2023
    If you are testing several different system, what about creating a separate test plan for each system being tested? This would then be easier to plan the tests, to track the progress and to report on the results for each separate system?