Latest Zowe Explorer VS Code extension: Functional Testing needs to be able to download MVS datasets so you need Zowe client software and either IBM RSE API or z/OSMF configured. For more information, see Installing VS Code Extension for Zowe. Once installed, you must create a Zowe team configuration file so that data sets can be found and accessed.
IBM Z Open Debug extension version 5.4.0 or greater. With Z Open Debug extension installed, a zOpenDebug Zowe profile can be created inside the Zowe team configuration file. This profile will be used to make a recording request to the IBM Debug Profile Service API
Getting started
Start by generating a base Galasa project. Open command palette by pressing Ctrl+Shift+P (Windows) or Cmd+Shift+P (MacOS) and execute > IBM Functional Testing: Create Galasa Project. This command will generate a new project and use maven to build it.
Next, update configuration values in zapp.yaml so that debug profile service API can successfully record application.
Add bms file maps into ft/bms-maps and add mfs file maps into ft/mfs-maps.
Generate functional tests
Now you are ready to record your CICS application. Open command palette and execute > IBM Functional Testing: Start recording.
Use a 3270 emulator or a similar tool to interact with your CICS application. Once you captured the actions you'd like to test, stop the recording by clicking the "Cancel" button on the recording popup.
The extension will download the recording file to your local workspace to ft/recordings
Right click on the resulting recording file and choose "Generate Galasa Functional test". This action will generate and write a new test file into your project.
Review the test file, make updates if needed, and add necessary assertion statements.
Accessibility
The IBM Functional Testing extension is designed to be fully accessible to all users, including those using assistive technologies. The extension achieves WCAG 2.1 Level AA compliance through exclusive use of VS Code's native accessible components.
Keyboard Navigation
All extension features are fully accessible via keyboard:
Command Palette:
Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS) - Access all extension commands
Type to search commands with fuzzy matching
Arrow Keys to navigate results
Enter to execute selected command
Tree Views:
Tab - Focus tree view
Arrow Keys - Navigate items
Right Arrow - Expand folder/item
Left Arrow - Collapse folder/item
Enter - Activate selected item
Space - Toggle selection (where applicable)
Shift+F10 or Context Menu Key - Open context menu
Test Explorer:
Ctrl+Shift+T (Windows/Linux) or Cmd+Shift+T (macOS) - Open Testing view
Arrow Keys - Navigate test hierarchy
Enter - Run selected test
Shift+Enter - Debug selected test
Dialogs and Input:
Tab / Shift+Tab - Navigate between fields and buttons
Enter - Activate focused button or submit
Escape - Cancel/close dialog
Space - Toggle checkboxes
Status Bar:
F6 - Cycle focus to status bar
Arrow Keys - Navigate status bar items
Enter - Activate status bar item
Screen Reader Support
This extension is tested with:
NVDA (Windows) - Free, open-source screen reader
JAWS (Windows) - Industry-standard screen reader
VoiceOver (macOS) - Built-in screen reader
Accessibility Features:
All interactive elements have descriptive labels
Tree view items include detailed tooltips explaining their purpose
Status indicators are announced (e.g., "Enhanced with Knowledge JSON")
Error messages and notifications are properly announced
Progress indicators provide status updates
Walkthrough images include extended descriptions
High Contrast Themes
The extension fully supports VS Code's theme system, including high contrast modes:
To enable high contrast:
Press Ctrl+K Ctrl+T (Windows/Linux) or Cmd+K Cmd+T (macOS)
Select "High Contrast" or "High Contrast Light"
All text meets WCAG AA contrast requirements (4.5:1 for normal text, 3:1 for large text).
Reporting Accessibility Issues
If you encounter accessibility barriers while using this extension:
Check the Accessibility Documentation for known issues and workarounds
Report issues via GitHub Issues with the "accessibility" label
Include:
Description of the barrier
Assistive technology used (name and version)
Steps to reproduce
Expected vs. actual behavior
Compliance Status
WCAG 2.1 Level A: ✅ Fully Compliant
WCAG 2.1 Level AA: ✅ Fully Compliant
Section 508: ✅ Compliant
For detailed accessibility information, contact the development team.
