How to aggregate test results across teams with Temporal Nexus
Blog post from Temporal
Temporal’s Release Engineering team created a shared report format and a Nexus Operation to bring evidence from cloud validation, nightly integration tests, and long-running Workflow tests into one reporting service while letting test owners retain their implementations and interpret results. Test Workflows submit protobuf-based reports through existing Temporal connections, and the platform validates and stores them for engineers to review through a separate API and terminal client. Nexus avoids requiring producers to know the reporting service’s deployment details or obtain separate credentials, while access is restricted to explicitly allowed Namespaces in the same Cloud Account. Reports identify their source and run, include individual test results, and use verdicts such as pass, warn, fail, and skipped; a failed test can still have a successfully completed reporting operation because ingestion status and test outcome are distinct. The team uses a source-and-business-ID key to make repeated submissions return the same record, though newer or older payloads can replace existing results without timestamp checks, and synchronous database work must meet a short request deadline. A temporary producer helped validate the integration before involving other teams, and the resulting reports support release decisions without automatically determining whether a release is ready.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.