IBM Z Software
Hide about this portal


This portal is to open public enhancement requests against IBM Z Software 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 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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Developer for z/OS
Categories zUnit
Created by Guest
Created on Sep 13, 2023

RELATED IDEAS

Input / Expected Output terminology is not clear in Test Case Editor

See this idea on ideas.ibm.com

The headlines for Input and Expected Output is confusing in the test case editor for database calls and sub program calls. 

The phrasing is seen from the calling program (Program under test). An “input” is input to the calling program (PROGRAMA) , and not input to the sub program (PROGRAMB). The usual way of describing this for most COBOL developers will be that the parameter that PROGRAMA provides to PROGRAMB is the Input to PROGRAMB, and the data being returned to PROGRAMA is the output from PROGRAMB. 

Also the the first column in the editor is the “Input” which is the data returned from PROGRAMB, whereas the data we expect PROGRAMA to provide as input to PROGRAMB is the second column. As a result, the reading order is opposite of the timing of the call, as first we validate the second column (Expected Output), then we a providing the data from Input column as the data returned from the stubbed version of PROGRAMB.

 The column heading makes sense for the input and the expected output from the module under test (PROGRAMA)– alas the column heading is fine for PROCEDURE DIVISION.

 One suggestion could be to have multiple panes/tabs. One for the input/output to the module under test, and another for the stubbed data to modules/data called from the module under test.

Idea priority Medium
  • Admin
    Mohit Satoskar
    Reply
    |     Oct 22, 2024

    Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our clients, so your input is always very important to us.

    Your request is currently inline with our IBM Test Accelerator for Z product strategy and we have transferred this (here) to IBM Test Accelerator for Z.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.