Scriptless Execution
TestRail steps written in natural language run directly by the DevAssure O2 agent — zero script maintenance code overhead required.
New in DevAssure O2: Scriptless Flutter Web Testing + TestRail Integration·
Your team plans and tracks tests in TestRail.
DevAssure closes the execution gap — fetch cases, run them in a real browser, and sync results back automatically.
Fetches manual test cases securely via TestRail API.
Filters runtime queue based on specified section, labels, priority, or case IDs.
DevAssure O2 executes natural language steps directly inside isolated browsers.
Constructs real-time pass/fail logs, computes execution scores, and handles error context.
Creates an authenticated TestRail run to stream results, defects, and video captures back.
DevAssure interfaces seamlessly with TestRail as a pluggable execution provider — extending your manual test catalog into lightning-fast, AI-driven automation cycles.
TestRail steps written in natural language run directly by the DevAssure O2 agent — zero script maintenance code overhead required.
End-to-end user validations run natively against Chromium, Chrome, or Edge engines with highly configurable headless/headed execution modes.
Fetch production cases, execute live user logic, then post results, pass/fail scores, log detailed defects, and attach session videos back to TestRail.
Push test run status updates, full context bug attachments, and complete video screen records down to your workspace dashboard automatically with simple terminal args.
Create Run Automatically
--create-run=trueInstructs the runner to dynamically instantiate an isolated, named TestRun execution profile directly inside your TestRail dashboard upon initialization.
Existing Run Targeting
--run-id=1234Appends passing or failing test parameters, structural logs, and telemetry directly to an established, pre-configured run template inside TestRail.
Dynamic Title Insertion
--run-name='Name'Applies explicit custom naming rules to dynamic test runs. Supports fallback strategies that inherit native localized repository timestamps if left unassigned.
Video Attachment Policies
--attach-videosPipes physical system mp4 artifacts across the network. Configurable to transmit records on complete suite files, only failure conditions, or completely skip.
Pass localized command vectors directly to focus your test agent execution workflows based on specific test cases, suite variations, or organizational labels.
--project-id=<id>Specifies the unique tracking index assigned to your global project environment.
--suite-id=<id>Targets a distinct structured functional testing module suite within the dashboard data layout.
--section-id=<id>Filters down to isolated component clusters, specific testing criteria folders, or subsets.
--run-id=<id>Forces updates to target an explicit active pipeline template instead of spinning up new profiles.
--case-ids=<id1,id2>Passes a strict comma-delimited list of specific criteria keys to restrict runner loop activity.
--milestone-id=<id>Binds resulting execution metrics to a core product sprint target, milestone cycle, or release vector.
Everything you need to know about DevAssure, PR testing, and CI integration.
Yes. After you configure TestRail as a provider, DevAssure fetches cases from your TestRail project via the API and executes them in a real browser. You can filter by project, suite, section, labels, priority, or case IDs from the CLI or VSCE.
Yes, when you enable post results (`--post-results` in the CLI or `devassure.testrail.postResults` in VSCE). DevAssure creates or updates a TestRail test run and records outcomes for each executed case.
Yes. Use devassure add-token for authentication, then devassure run --provider testrail with your filters and --post-results. Combine with --archive and devassure summary for pipeline reporting.
Run devassure add-provider-config and choose testrail in the CLI, or use **DevAssure: Add Provider Config** in VSCE. Credentials are stored in an encrypted testrail.enc.json file in your secrets directory—not in plain text in the repo.
Yes. With --log-defects (requires --post-results), the agent can log defects linked to failing cases. With --attach-videos set to on-failure or always, session recordings can be attached to TestRail results when results are posted.
No. For cases you run from TestRail through DevAssure, steps can be written in natural language in TestRail and executed by the AI agent—reducing the need for brittle UI scripts for those flows. DevAssure O2 remains complementary for change-aware testing on pull requests