@devassure/cli
Advanced tools
| "use strict"; | ||
| const minMajor = 18; | ||
| const current = process.versions.node; | ||
| const major = parseInt(current.split(".")[0], 10); | ||
| if (major < minMajor) { | ||
| console.error(` | ||
| ❌ DevAssure CLI requires Node.js ${minMajor} or higher. | ||
| Current: ${current} | ||
| Please upgrade Node.js: https://nodejs.org/ | ||
| `); | ||
| process.exit(1); | ||
| } |
+2
-2
| { | ||
| "name": "@devassure/cli", | ||
| "version": "1.0.6", | ||
| "version": "1.0.8", | ||
| "type": "module", | ||
@@ -31,3 +31,3 @@ "description": "DevAssure CLI application", | ||
| "install:tgz": "node scripts/install-tgz.cjs", | ||
| "preinstall": "node scripts/require-global-install.cjs", | ||
| "preinstall": "node scripts/check-node-version.cjs && node scripts/require-global-install.cjs", | ||
| "postinstall": "node scripts/postinstall-setup.cjs", | ||
@@ -34,0 +34,0 @@ "prepublishOnly": "node scripts/prepublish-check.cjs" |
+27
-1
@@ -1,2 +0,2 @@ | ||
| # DevAssure CLI | ||
| # DevAssure Agent CLI | ||
@@ -226,2 +226,5 @@ Command-line interface for DevAssure Testing Agent - Autonomous agent executing tests from natural language instructions. | ||
| # Use keyword search to filter tests (this will do text match on summary, steps, tags) | ||
| devassure run-tests --filter="query = dashboard" | ||
| # All parameters support plural forms | ||
@@ -402,4 +405,27 @@ devassure run-tests --tags=smoke,regression --priorities=P0,P1 --folders=admin/users | ||
| ## FAQ | ||
| **How to add new test cases?** | ||
| Add YAML files under `.devassure/tests/` (or `test/`), or use a CSV file with `--csv <path>` and optionally `.devassure/csv_mapping.yaml` to map columns to test fields. | ||
| **Is test case YAML always needed or can we use CSV only?** | ||
| No. You can run tests from CSV only: use `devassure run-tests --csv=<path>` and configure `.devassure/csv_mapping.yaml` so your CSV columns map to summary, steps, priority, and tags. | ||
| **What are the mandatory fields for a test case?** | ||
| For YAML test cases, `summary` and `steps` are required. `priority` and `tags` are optional. For CSV, the mapped columns must provide at least the equivalent of summary and steps. | ||
| **How to add a new environment?** | ||
| Add a new top-level key (e.g. `uat`) and its data in `.devassure/test_data.yaml`. Then run with `devassure run-tests --environment=uat` (or `--environment uat`). If you omit `--environment`, the `default` key in test_data.yaml is used. | ||
| **What are the supported browsers?** | ||
| Supported browsers are Chromium, Chrome, Edge. Controlled by `.devassure/preferences.yaml` under `browsers.default.browser`. The default is `chromium`. See the preferences.yaml section above for the structure. | ||
| **How to run with headless mode?** | ||
| In `.devassure/preferences.yaml`, set `browsers.default.headless: true`. | ||
| **How to run the tests in Continuous Integration?** | ||
| Use `devassure add-token <your-token>` to authenticate (no browser). Then run `devassure run-tests` with the options you need (e.g. `--csv`, `--filter`, `--tag`, `--priority`, `--archive` for saving report zips). You can retain only recent sessions with `devassure cleanup --retain-days 7` or `--retain-sessions 10`. | ||
| ## Support | ||
| For more information, visit [DevAssure](https://devassure.io) or run `devassure help` for command-specific help. |
Sorry, the diff of this file is too big to display
Install scripts
Supply chain riskInstall scripts are run when the package is installed or built. Malicious packages often use scripts that run automatically to execute payloads or fetch additional code.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 7 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Found 2 instances in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
Install scripts
Supply chain riskInstall scripts are run when the package is installed or built. Malicious packages often use scripts that run automatically to execute payloads or fetch additional code.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 7 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
222142
1.21%12
9.09%1006
1.31%430
6.44%29
3.57%