
Security News
Feross on the 10 Minutes or Less Podcast: Nobody Reads the Code
Socket CEO Feross Aboukhadijeh joins 10 Minutes or Less, a podcast by Ali Rohde, to discuss the recent surge in open source supply chain attacks.
@devassure/cli
Advanced tools
Command-line interface for DevAssure Testing Agent - Autonomous agent executing tests from natural language instructions.
Install DevAssure CLI globally using npm:
npm install -g @devassure/cli
Or using pnpm:
pnpm add -g @devassure/cli
After installation, verify it's working:
devassure version
Authenticate with DevAssure:
devassure login
This will open your browser for OAuth2 authentication.
Alternatively, you can add an authentication token directly (recommended for CI/CD pipelines):
devassure add-token <your-token>
Initialize DevAssure configuration in your project:
devassure init
This will:
.devassure folder with configuration filesAdd test cases to the project by adding yaml files to the .devassure/tests folder in the project directory.
Example test case file:
```yaml
summary: Sample test case
steps:
- Open the application url
- Verify if the page loads successfully
- Verify if there are no error messages
priority: P0
tags:
- sanity
- app-load
Run tests using the current directory as test cases directory:
devassure run-tests
# or use the alias
devassure run
Any required test data can be added to .devassure/test_data.yaml in the project directory.
Example test data file:
default:
url: 'http://localhost:3000'
users:
default:
user_name: 'user@test.com'
password: 12345678
admin:
user_name: 'admin@test.com'
password: 12345678
devassure login - Login to DevAssure using OAuth2 authenticationdevassure logout - Logout from DevAssure and clear stored tokensdevassure add-token <token_value> - Add and validate an authentication tokendevassure init - Initialize DevAssure configuration in the current directory
.devassure folder with configuration filesdevassure run-tests - Run tests using current directory as test cases directory
--path <path> - Project path (default: current directory)--tag <tags> / --tags <tags> - Comma-separated tag values (e.g., --tag=tag1,tag2,tag3)--priority <priorities> / --priorities <priorities> - Comma-separated priority values (e.g., --priority=P0,P1)--folder <folders> / --folders <folders> - Comma-separated folder paths (e.g., --folder=admin/users,project/integration)--query <query> / --queries <query> - Search query string (e.g., --query="my search query")--filter <filter> / --filters <filter> - Raw filter string (takes precedence over other filter parameters, e.g., --filter="tag = tag1,tag2 && priority = P0")--archive <folder> - Archive folder path; after the run, test reports are written as devassure-results-<session-id>.zip in this folder (relative paths are resolved from current directory)--filter/--filters is provided, all other filter parameters (--tag, --priority, --folder, --query) are ignoreddevassure run (same options apply)devassure archive-report - Archive report results for a test session into a zip file
--output-dir <dir> - (Required) Output directory for the archived report zip--session-id <sessionId> - Session ID to archive (either this or --last is required)--last - Use the last executed session ID from the databasedevassure-agent archive-results and writes devassure-results-<session-id>.zip into the output directorydevassure open-report - Open report server for a test session
--session-id <sessionId> - Session ID to open report for--last - Open report for the last executed session--archive <path> - Path to an archived zip file (e.g. from archive-report) to open; opens the report from the zip without using the database--archive, --session-id, or --last is requireddevassure summary - Print summary for a test session
--session-id <sessionId> - Session ID to summarize (either this or --last is required)--last - Use the last executed session ID from the database--json - Output summary as JSON (session_id, environment, scenarios, score, grouped_failures, passed_validations, duration_ms, duration_string)devassure stats - Show statistics about sessions, scenarios, and storage
devassure cleanup - Clean up old sessions
--retain-days <days> - Retain sessions from the last N days--retain-sessions <count> - Retain the last N sessionsdevassure version - Show version of the CLIdevassure help - Show help information--verbose - Enable verbose logging for all commandsProject files files are stored in:
~/.devassure/ (project-specific)# 1. Login
devassure login
# 2. Initialize project
devassure init
# 3. Run tests
devassure run-tests
# 4. View report for last session
devassure open-report --last
# Keep only sessions from last 7 days
devassure cleanup --retain-days 7
# Keep only the last 10 sessions
devassure cleanup --retain-sessions 10
# Run tests with specific tags
devassure run-tests --tag=smoke,regression
# Run tests with specific priority
devassure run-tests --priority=P0,P1
# Run tests in specific folders
devassure run-tests --folder=admin/users,project/integration
# Run tests with a search query
devassure run-tests --query="login flow"
# Combine multiple filter parameters
devassure run-tests --tag=smoke --priority=P0 --folder=admin/users
# Use raw filter string (takes precedence over other filter parameters)
devassure run-tests --filter="tag = tag1,tag2 && priority = P0"
# All parameters support plural forms
devassure run-tests --tags=smoke,regression --priorities=P0,P1 --folders=admin/users
# Run tests and archive reports to a folder (zip created after run completes)
devassure run-tests --archive=./reports
devassure run --archive=/tmp/archives
# Archive the last session's report to a directory
devassure archive-report --output-dir=./reports --last
# Archive a specific session's report
devassure archive-report --output-dir=./reports --session-id=<session-id>
# Open report from an archived zip file
devassure open-report --archive=./reports/devassure-results-<session-id>.zip
# Print summary for the last session
devassure summary --last
# Print summary for a specific session
devassure summary --session-id=<session-id>
# Output summary as JSON
devassure summary --last --json
For more information, visit DevAssure or run devassure help for command-specific help.
FAQs
DevAssure O2 Agent CLI
The npm package @devassure/cli receives a total of 687 weekly downloads. As such, @devassure/cli popularity was classified as not popular.
We found that @devassure/cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CEO Feross Aboukhadijeh joins 10 Minutes or Less, a podcast by Ali Rohde, to discuss the recent surge in open source supply chain attacks.

Research
/Security News
Campaign of 108 extensions harvests identities, steals sessions, and adds backdoors to browsers, all tied to the same C2 infrastructure.

Security News
OpenAI rotated macOS signing certificates after a malicious Axios package reached its CI pipeline in a broader software supply chain attack.