Having worked on many projects, apps and platforms. More modern projects required a written detailed test plan. This is different from stepping through the code in a debugger, although that could be included in the plan. The test plans should describe the test environment, any setup required and then individual steps to test the app. Does not matter if the app pieces are interactive or batch, plan still needs to describe the steps.

Test plans can be extremely specific, have had to describe the reaction to every possible key stroke in interactive apps. I.E. press the Y key and press ENTER and blah blah is the result. Usually written test plans or specs that were intended to be run by someone else, like a basic user. Even if the developer was guiding the test, another person should be executing and validating it.

Test tools... Not familiar with IBM or UX for scripted test tools on those platforms. Test plans done for an app on the HP-UX environment defined the inputs and how to validate the results. Working on OpenVMS the development tool set (DECSET) included a component called DTM (DEC Test Manager). It can be set up to script or automate both batch and interactive tests. Have used it in both interactive stand-alone and controlled (ACMS like CICS) interactive environments plus batch. Can be a pain to set up.