Add Code Execution and Test Running to Traycer

[jaycangel]

Feature Request: Add Code Execution and Test Running to Traycer

Summary
Traycer currently performs extensive scanning and verification but never actually runs the code. Without execution, Traycer misses critical issues like library incompatibilities, runtime errors, and configuration problems.

Problem
I’ve spent hours building a test site only to discover that Traycer’s verification steps alone aren’t enough—because the code is never executed, many issues slip through undetected. This makes it difficult to rely on Traycer for realistic validation of applications. Even when using multiple models (Traycer, Claude, Copilot, Gemini), the same limitation persisted.

Proposed Solution

• Add functionality for Traycer to run the code it analyzes.
• Provide an option to write and execute unit tests automatically during the verification process.
• Include configurable runtime environments or sandboxing to ensure safe execution.

Benefits

• Detects real-world runtime and compatibility issues early.
• Improves developer trust and speeds up debugging.
• Aligns Traycer’s behavior with how applications are actually used in production.

Additional Context
This feature would make Traycer significantly more robust and useful for developers working on complex projects where static verification is not enough.

[hdkshingala]

Thank you for the excellent suggestion, @jaycangel.

Running terminal commands to execute the application or test cases is a necessary step for end-to-end verification. We have it on our immediate agenda and will add support for it in the coming weeks.