Skip to main content

​
Overview

The /test-workflows command runs RAPTOR’s comprehensive test suite to validate that all commands and user scenarios work correctly.
This command is a stub - it triggers the test suite execution but the full workflow testing implementation is still in development.

​
What It Tests

The test suite validates:
  1. Basic scan - Findings detection without exploit generation
  2. Full agentic workflow - Complete scan → exploit → patch pipeline
  3. Binary fuzzing - AFL++ integration and crash collection
  4. Manual crash validation - Crash analysis workflow
  5. Tool routing - Correct command execution paths

​
Usage

/test-workflows
This executes the test suite via: 
bash test/test_workflows.sh

​
Test Output

Each test produces one of three results:
  • ✓ PASS - Test completed successfully
  • ✗ FAIL - Test failed with errors
  • ⊘ SKIP - Test skipped (dependencies missing)

​
Summary Format

=== Test Results ===
Passed: 15
Failed: 0
Skipped: 2

Total: 17 tests
Status: ALL PASSED
Exit codes:
  • 0 - All tests passed
  • 1 - One or more tests failed

​
Use Cases

Validate Changes

Run after modifying RAPTOR code

Pre-Release Testing

Verify workflows before releases

Regression Detection

Catch breaking changes early

CI/CD Integration

Automate testing in pipelines

​
Duration

Typical test suite execution time: 2-3 minutes Individual test timings:
  • Basic scan: ~30 seconds
  • Agentic workflow: ~60 seconds
  • Binary fuzzing: ~45 seconds
  • Crash validation: ~20 seconds
  • Tool routing: ~10 seconds

​
Example Output

$ /test-workflows

Running RAPTOR test suite...

[1/5] Basic scan workflow... ✓ PASS (28s)
[2/5] Full agentic workflow... ✓ PASS (62s)
[3/5] Binary fuzzing... ✓ PASS (41s)
[4/5] Crash validation... ✓ PASS (19s)
[5/5] Tool routing... ✓ PASS (8s)

=== Test Results ===
Passed: 5
Failed: 0
Skipped: 0

Total: 5 tests
Status: ALL PASSED

Duration: 158 seconds

​
CI/CD Integration

Add to your continuous integration pipeline:
GitHub Actions
- name: Run RAPTOR tests
  run: |
    cd raptor
    bash test/test_workflows.sh
GitLab CI
test:
  script:
    - cd raptor
    - bash test/test_workflows.sh
  allow_failure: false

​
Troubleshooting

​
Tests Fail with Missing Tools

Ensure all dependencies are installed: 
# Check Semgrep
semgrep --version

# Check AFL++
afl-fuzz -h

# Check Python packages
pip install -r requirements.txt

​
Tests Skip Due to Permissions

Some tests require elevated permissions: 
# Run with appropriate permissions
sudo bash test/test_workflows.sh

​
Test Timeouts

Increase timeout limits for slow systems: 
export TEST_TIMEOUT=300  # 5 minutes per test
bash test/test_workflows.sh

​
See Also

Testing Guide

Comprehensive testing documentation

Contributing

How to add new tests

Build docs developers (and LLMs) love

Get started for freeTalk to us