Jump to content

Connect SuperML | Leeroopedia MCP: Equip your AI agents with best practices, code verification, and debugging knowledge. Powered by Leeroo — building Organizational Superintelligence. Contact us at founders@leeroo.com.

Implementation:ArroyoSystems Arroyo Golden Test Outputs

From Leeroopedia
Revision as of 14:26, 16 February 2026 by Admin (talk | contribs) (Auto-imported from implementations/ArroyoSystems_Arroyo_Golden_Test_Outputs.md)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Knowledge Sources
Domains Testing, SQL, TestData
Last Updated 2026-02-08 08:00 GMT

Overview

Golden output JSON files used by the Arroyo SQL smoke test harness to verify that pipeline execution produces correct results.

Description

The golden_outputs/ directory contains expected output files for the SQL integration smoke tests defined in smoke_tests.rs. Each file corresponds to a SQL test query file by name and contains the expected JSON-lines output. The test harness compares actual pipeline output against these files line by line (after sorting) or via Debezium CDC merge for updating queries.

Files

File Lines Description
cast_to_sink_type.json 7932 Expected output for type casting operations to sink-compatible types. Each line contains a JSON object with fields like timestamp, driver_id, event_type, and location.
debezium_pass_through.json 798 Expected Debezium CDC output with before/after objects and op codes (c/u/d). Tests passthrough of CDC records including order data with fields like id, customer_name, product_name, quantity, price, order_date, and status.
json_operators.json 7932 Expected output for JSON operator tests, same structure as cast_to_sink_type.
memory_table.json 7932 Expected output for in-memory table tests.
most_active_driver_last_hour.json 1557 Expected output for a sliding window aggregation query that finds the most active driver in the last hour. Contains count, driver_id, start, end, and row_number fields.
select_star.json 7932 Expected output for a simple SELECT * passthrough query.

Data Format

All files use JSON-lines format (one JSON object per line, no wrapping array). The smoke test harness reads each line as a serde_json::Value, sorts them by string representation, and compares pairwise. For Debezium-format outputs, the harness applies CDC operations (create, update, delete) to build final state before comparison.

Code Reference

Source Location

Related Pages

Page Connections

Double-click a node to navigate. Hold to expand connections.
Principle
Implementation
Heuristic
Environment