DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Comparison · Infra & APIs
Merge vs testthat
A side-by-side editorial comparison of Merge and testthat — release velocity, themes, recent moves, and the top alternatives to consider.
Merge vs testthat: at a glance
| Feature | Merge | testthat |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | unified api, agent handler, mcp connectors, ai gateway | testing, coding-agents, opentelemetry, deprecations |
| Last editorial update | 11h ago | 6d ago |
| Website | — | Visit → |
What is Merge?
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
What is testthat?
testthat now ships a reporter built for the coding agent running the tests.
testthat is at 3.3.2, which added LlmReporter(), a reporter designed for LLM coding agents and used automatically inside Claude Code, Cursor and Gemini CLI, with AGENT=1 to opt any other agent in. The same release emits OpenTelemetry traces when tracing is enabled. It follows 3.3.0, a large lifecycle release that required R 4.1, made local_mock() and with_mock() defunct, and rewrote every expect_ failure message to state what was expected, what arrived and how they differ.
Merge vs testthat: editorial side-by-side
Merge
6.3INFRA · APIS
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
◆ Current state
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
◆ Where it's heading
The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.
◆ Prediction
Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.
testthat
0.0INFRA · APIS
testthat now ships a reporter built for the coding agent running the tests.
◆ Current state
testthat is at 3.3.2, which added LlmReporter(), a reporter designed for LLM coding agents and used automatically inside Claude Code, Cursor and Gemini CLI, with AGENT=1 to opt any other agent in. The same release emits OpenTelemetry traces when tracing is enabled. It follows 3.3.0, a large lifecycle release that required R 4.1, made local_mock() and with_mock() defunct, and rewrote every expect_ failure message to state what was expected, what arrived and how they differ.
◆ Where it's heading
Both threads point the same way: making test output legible to something other than a human reading a console. The 3.3.0 message rewrite made failures self-describing, and LlmReporter() plus OpenTelemetry take that to machine consumers — an agent parsing results and a tracing backend collecting them. The deprecation clean-out running underneath is the usual cost of getting there.
◆ Prediction
With a reporter now shipped for coding agents and tracing behind optional packages, the next release most likely refines that reporter's output format rather than adding another consumer.
Alternatives to Merge and testthat
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Merge or testthat.
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox
NetBox adds a cooling data model — the first new infrastructure domain since power
See all Merge alternatives → · See all testthat alternatives →
Recent activity from Merge and testthat
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 19d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 26d agoMergeLink setup flow becomes configurable per integration
- 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 1mo agoMergeGateway breakout page for the week already covered by Week 2
- 1mo agoMergeUnified breakout page for the week already covered by Week 3
- 7mo agotestthattestthat 3.3.2 ⚡
- 8mo agotestthatFixes shinytest2 screenshot snapshots on CI
- 9mo agotestthatAll failure messages rewritten; local_mock() now defunct
- 1y agotestthatFixes expect_no_error() and skip() outside a test
- 1y agotestthatexpect_s7_class() and new failure-testing expectations
- 2y agotestthatR-devel format fix and a more reliable offline check
Frequently asked questions
What is the difference between Merge and testthat?
They serve adjacent needs but don't currently overlap on shipped themes. Merge is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Merge better than testthat?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.
What are the best alternatives to testthat?
Top testthat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "testthat alternatives" section above for the current picks, or visit /alternatives/testthat for the full list with editorial commentary on each.