ISC Test Case Runner - VS Code ExtensionBuild: 413 Execute ISC test cases by remotely connecting to your ISC tenant directly from VS Code. Features
Requirements
To verify your Java installation, run the following in a terminal:
Expected output (version must be 17 or higher):
InstallationThe extension is distributed as a Option 1 — VS Code UI
Option 2 — Command Line
After installation, reload VS Code when prompted. Setup1. Create
|
| Field | Description |
|---|---|
name |
A label for this connection (e.g. main, dev, prod) |
iscUrl |
Your ISC tenant API base URL |
clientId |
OAuth client ID with the required scopes |
clientSecret |
OAuth client secret |
testCaseApiVersion |
API version to use (currently v2025) |
Note: The extension will automatically create a
connection-properties.jsonwith placeholder values the first time you open a JSON file, if the file does not already exist. Make sure to replace the placeholders before running any test cases.
You can define multiple connections in the connections array and reference them by name from your test case files.
2. Run a Test Case
- Open a
*.isctf.jsontest case file in VS Code - Click the play button (▶) in the editor title bar to run the full test case, or use the inline CodeLens buttons to run individual commands
- View results in the Java Executor output channel
ISCAT Library
The extension doesn't contain the ISCAT Java library. It downloads it from Artifactory into your project the first time you run something, and keeps it up to date.
Before the first run: run ISCAT: Set Artifactory Token from the Command
Palette (Ctrl+Shift+P) and paste a JFrog access or reference token with read
access to the iscat-generic-iscatLibsWithDep-release-local repository. The token is kept
in VS Code's secret storage, not in your settings. If no token is set, you're
asked for one on the first run.
How updates work:
- The library is installed into
lib/in your workspace. This is set byjavaFileExecutor.libDir. If your project uses git, you're offered to add that folder to.gitignore. - Artifactory is asked for a new version at most once a day. This is set by
javaFileExecutor.updateCheckIntervalHours, and the check is shared across all your projects. The library is only downloaded (about 100 MB) when the version changes. - To pin a version, set
javaFileExecutor.libraryVersionto e.g.1.4.0. A pinned version that is already installed never contacts Artifactory. - ISCAT: Check for Library Updates checks immediately.
- The status bar shows the installed version. Click it for more options.
- When you're offline, or Artifactory is unreachable, the installed version keeps working.
Snapshot builds: set javaFileExecutor.libraryChannel to dev to follow
development builds from iscat-generic-iscatLibsWithDep-dev-local. This needs
read access to that repository. A new build of the same snapshot version is
detected and downloaded again.
Using a local build (development): set javaFileExecutor.classPathDirs to
the folders holding your jars. The classpath is then built from exactly those
folders, nothing is downloaded, and the status bar shows ISCAT: local.
Project Structure
<workspace root>/
├── connection-properties.json ← required, created automatically with placeholders
├── lib/ ← ISCAT library, downloaded automatically (add to .gitignore)
└── *.isctf.json ← your test case files