@xano/developer-mcp 1.0.45 → 1.0.46
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -55,6 +55,8 @@ addon.call "<addon_name>" as $result
|
|
|
55
55
|
|
|
56
56
|
### function.call
|
|
57
57
|
|
|
58
|
+
> **Important:** Always use `function.call` in workflow tests, not `function.run`. `function.call` handles errors internally, which is required for `expect` assertions (such as `expect.to_throw`) to work correctly. `function.run` is for calling functions from other primitives (APIs, functions, tasks, etc.) outside of workflow tests.
|
|
59
|
+
|
|
58
60
|
```xs
|
|
59
61
|
function.call "<function_name>" {
|
|
60
62
|
input = { key: "value" }
|
|
@@ -319,7 +321,8 @@ workflow_test "comprehensive_test" {
|
|
|
319
321
|
2. **Tag for filtering** — Use tags like `critical`, `e2e`, `smoke` to organize test suites
|
|
320
322
|
3. **Avoid `datasource = "live"`** — The entire datasource is cloned before each test run, which can be slow. Use no datasource or a smaller custom datasource instead
|
|
321
323
|
4. **Keep tests independent** — Each workflow test should be self-contained and not depend on other tests
|
|
322
|
-
5. **Use
|
|
324
|
+
5. **Use `function.call`, not `function.run`** — `function.call` handles errors so that `expect` assertions work correctly. `function.run` is for calling functions outside of workflow tests
|
|
325
|
+
6. **Use assertions over preconditions** — Prefer `expect.*` assertions for clearer test intent
|
|
323
326
|
|
|
324
327
|
---
|
|
325
328
|
|
package/package.json
CHANGED