Skip to content

Commit a94f3b2

Browse files
KyleKincerclaude
andcommitted
docs: update Testing_RunTestsWithCs signature to show all three parameters
Updated CLAUDE.md example code to demonstrate the complete three-parameter signature: Testing_RunTestsWithCs(cs; $hostStorage; $userParams) Previously showed only two parameters (cs and $testStorage), but the method accepts an optional third parameter for user configuration (e.g., trigger control, output format). The syntaxEN.json file already contained the correct three-parameter signature and was updated by 4D's automatic metadata generation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
1 parent 0381b82 commit a94f3b2

File tree

2 files changed

+504
-254
lines changed

2 files changed

+504
-254
lines changed

CLAUDE.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -337,11 +337,14 @@ When running tests from a host project (not standalone), you **must** pass the h
337337

338338
```4d
339339
// In your host project's method to run tests
340-
var $testStorage : Object
341-
$testStorage:=Storage // Pass the host project's Storage
340+
var $hostStorage : Object
341+
var $userParams : Object
342342
343-
// Call the testing component method with both cs and Storage
344-
Testing_RunTestsWithCs(cs; $testStorage)
343+
$hostStorage:=Storage // Pass the host project's Storage
344+
$userParams:=New object // Optional parameters (e.g., "triggers"; "enabled")
345+
346+
// Call the testing component method with cs, Storage, and optional user params
347+
Testing_RunTestsWithCs(cs; $hostStorage; $userParams)
345348
```
346349

347350
**Important:** Components have separate Storage objects from their host projects. By passing the host's Storage, the test framework can set flags that your host project's triggers can check.

0 commit comments

Comments
 (0)