HOW RQ WORKS

Every Execution Becomes Engineering Evidence

RQ continuously captures source code metadata and runtime execution, correlating both into an execution knowledge base that grows with every commit and application execution.

SYSTEM OVERVIEW

Continuous Collection. Continuous Correlation.

RQ continuously observes both your source code and application runtime. Together they form a reusable execution knowledge base.

Source Code Analysis Git Repository Any Git Provider RQ Repository Scan Commit Analysis Symbol Extraction Method Metadata Application Runtime J Java .NET .NET Py Python RQ RQ Tracers Capture runtime events RQ Regressq Platform Execution Knowledge Base Source Metadata Runtime Events Commit Intelligence Source Metadata Runtime Events Regression Impact Analysis Identify what changes impact what matters. Execution Traceability Trace every execution to code, commits, tests and APIs. Release Readiness Know with confidence what's safe to release. Continuous Intelligence Secure & Private Scalable & Extensible Technology Agnostic
STEP 1

Capture Engineering Signals

Source Code Analysis

The RQ Agent continuously scans your Git repository, extracting commits, files, symbols, methods and metadata required for future correlation.

Runtime Observation

Lightweight RQ Tracers observe real application execution, recording methods, APIs and automated tests with minimal changes to source code.

STEP 2

Correlate Runtime With Source Code

Source code metadata and runtime observations are correlated to build relationships between commits, methods, APIs and automated tests.

Commits

Source revisions become traceable.

Methods

Runtime execution identifies executed methods.

Tests

Historical executions are preserved.

STEP 3

Build An Execution Knowledge Base

Each execution contributes additional relationships to the execution knowledge base, enabling future code changes to be analyzed using historical execution data.

COMMIT CHANGED FUNCTIONS TEST EXECUTION TRACE REGRESSION CANDIDATES feature/payment-refactor commit 91a2b7c 6 OF 9 CHANGED 3 files touched PaymentService.cs C# · src/services/payment CreatePayment() ValidateCard() CompleteOrder() OrderService.cs C# · src/services/orders CreateOrder() SubmitOrder() ValidateOrder() CartValidator.cs C# · src/services/cart ValidateCart() ValidateCoupon() CalculateDiscount() TC_1 Payment Test CreatePayment() ValidateCard() CompleteOrder() 2 of 3 traced functions changed TC_2 Order Test CreateOrder() SubmitOrder() ValidateOrder() Matched 1 of 3 traced functions TC_3 Cart Test ValidateCart() ValidateCoupon() CalculateDiscount() Matched 2 of 3 traced functions TC_4 CheckoutFlow Test CreatePayment() CreateOrder() Matched CreatePayment(), CreateOrder() TC_5 Order Status Test CompleteOrder() ValidateOrder() No changed functions matched TC_1 PAYMENT TEST AT RISK 2 of 2 traced functions changed TC_2 ORDER TEST AT RISK Matched 1 changed methods TC_3 CART TEST AT RISK Matched 2 changed methods TC_4 CHECKOUTFLOW TEST AT RISK Matched 3 changed methods TC_5 ORDERSTATUS TEST SAFE No changed methods matched Changed method Historical method Matched during historical execution Observed but unchanged 6 Changed Methods 5 Observed Tests 4 / 5 Regression Candidates 180 Historical Executions HIGH Trace Confidence
WHAT THIS ENABLES

Practical Applications Of The Execution Knowledge Base

Regression Impact Analysis

Identify candidate regression tests using historical execution.

Execution Traceability

Navigate between commits, methods and tests.

Release Readiness

Assess release readiness using historical execution data.

See The Platform In Action

Explore how the execution knowledge base is used to analyze code changes, trace execution and understand application behavior.

Product Tour →