test

name	test
description	Run Jython gateway tests or Playwright e2e tests. Usage — /ignition-scada:test [module|package|ui|e2e|smoke]

Run Tests

Run tests for the current Ignition project. Routes to gateway tests (Jython) or browser tests (Playwright) based on arguments.

Arguments

$ARGUMENTS

Routing

Default is always gateway (Jython) tests. Only route to Playwright when explicitly asked with ui or e2e.

Argument	Action
(empty)	Run all gateway Jython tests
<short-name> (e.g. changeover)	Translate to module path and run gateway test: try <name>.__tests__ first, search for matching module
<dotted.path> (contains .)	Run as gateway module or package filter
ui or e2e	Run all Playwright browser tests
ui <area>	Run Playwright tests in e2e/tests/<area>/
ui smoke	Run Playwright smoke tests (e2e/tests/smoke/)
smoke	Run gateway Jython tests — NOT Playwright. "Smoke test" without ui prefix means gateway tests.

Ambiguity rule: If the user says "smoke test", "run tests", "test it", or any unqualified test request — always default to gateway Jython tests, not Playwright. Only use Playwright when the user explicitly says "ui", "e2e", "browser", or "playwright".

Gateway Tests

1. Detect the project using the detect-project script:

   ${CLAUDE_PLUGIN_ROOT}/scripts/detect-project.sh
   

2. Check that test infrastructure exists (existing_testing.jython_framework and existing_testing.webdev_endpoints). If not, tell the user: "Test infrastructure not found. Run /ignition-scada:init-testing first."

3. Commit pending changes before proceeding. The force scan in the next step can trigger the Designer or Git module to write back to the project directory — uncommitted work could be overwritten. Avoid git stash here: stashing removes the edits from the working tree, so the test run would exercise old code rather than your current changes.

4. Bump resource.json versions for any script modules that were edited since the last test run. Ignition's Jython runtime caches compiled modules in sys.modules — a project scan alone does NOT flush this cache. Incrementing the version field is the strongest signal to force re-import.

   For each modified code.py, increment version in the adjacent resource.json:

   { "version": 2, ... }
   

5. Trigger a gateway project scan with forceUpdate=true:

   TOKEN_FILE="${IGNITION_API_TOKEN_FILE:-}"
   if [ -n "$TOKEN_FILE" ] && [ -f "$TOKEN_FILE" ]; then
     TOKEN=$(cat "$TOKEN_FILE")
     curl -k -fsS --max-time 10 -o /dev/null -X POST -H "X-Ignition-API-Token: $TOKEN" \
       "<gateway>/data/project-scan-endpoint/scan?updateDesigners=true&forceUpdate=true"
   fi
   

   Why forceUpdate=true? Without it, the scan may skip resources it considers unchanged. Combined with the version bump, this ensures the gateway picks up the new bytecode.

   If no API token is configured, warn the user that tests may run against stale Jython state. They can manually trigger a scan by saving from Designer or restarting the gateway before proceeding.

6. Wait 3-5 seconds for scan propagation.

7. Run the tests:

   # All tests
   curl -k -s -X POST "<gateway>/system/webdev/<project>/testing/run"
   
   # Specific module
   curl -k -s -X POST "<gateway>/system/webdev/<project>/testing/run?module=<module>"
   
   # Package filter
   curl -k -s -X POST "<gateway>/system/webdev/<project>/testing/run?package=<package>"
   

8. Parse the JSON response and present results:

   • Summary: total, passed, failed, skipped, errors, duration
   • On failure: show each failure with test name, error message, and traceback
   • On success: report concisely

Playwright Tests

0. Check for inheritable parent project. Run detect-project.sh and check is_parent and has_perspective.

If is_parent == true AND has_perspective == false, this project has no Perspective views — E2E tests must run through a child project:

• Check the children array for entries where has_e2e == true
• One child with E2E: Tell the user: "This is an inheritable project with no Perspective views. Running E2E tests through child project {child.name}." Then execute Playwright from {child.root}/e2e/ (continue to step 3 below with E2E_DIR={child.root}/e2e).
• Multiple children with E2E: Ask the user which child to target, then run from that child's e2e/ directory.
• No children with E2E: Check if any children have has_perspective == true. If so, suggest: "Child project {child.name} has Perspective views but no E2E setup. Run /ignition-scada:init-e2e from that project first." If no children have Perspective at all, explain that E2E tests need a project with Perspective views. Suggest using /ignition-scada:test (no ui argument) for Jython gateway tests, which work normally in this project.

If is_parent == true AND has_perspective == true: proceed normally (parent has its own views).

1. Check that e2e/node_modules exists. If not, tell the user to run cd e2e && npm install && npx playwright install chromium.

2. Check that e2e/.auth/user.json exists. If not, tell the user to run cd e2e && npx playwright test --project=setup.

3. Run the tests:

   # All e2e tests
   cd e2e && npx playwright test
   
   # Specific area
   cd e2e && npx playwright test tests/<area>/
   
   # Smoke only
   cd e2e && npx playwright test tests/smoke/
   
   # Add --headed if the user says "headed" or "watch"
   

4. Parse the output and report results.

5. On failure, suggest: cd e2e && npx playwright show-report