tealeaves
A leaf-temperature model that finished its job in 2020 and has stayed finished
Comparison · Infra & APIs
DNSControl vs testdat
A side-by-side editorial comparison of DNSControl and testdat — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl vs testdat: at a glance
What is DNSControl?
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
What is testdat?
Unit testing for datasets, built on testthat and now bending to its next release.
testdat applies the testthat idiom to data rather than code: expectations that assert properties of a data frame, run as a suite, with results exportable to Excel. Recent releases have been about correctness and upstream compatibility. Expectations are now constructed via new_expectation() ahead of testthat 3.3.0, and expect_base() errors on a missing variable instead of silently passing.
DNSControl vs testdat: editorial side-by-side
DNSControl
5.0INFRA · APIS
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
◆ Current state
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
◆ Where it's heading
The v5 arc has run its course in public: rc1 laid out the dnsv2.RDATA refactor, rc3 finished converting every provider to it, rc4 completed the move to the Codeberg-hosted miekg/dns, and rc8 declared feature completeness. What is left is per-provider correctness on record types that only a handful of users exercise, which is why the maintainer is publishing a list of which providers most need testing rather than shipping.
◆ Prediction
Expect one or two more release candidates of provider fixes before the 25 August date, with the risk concentrated in providers nobody volunteers to test - the notes already flag PACKETFRAME as unmaintained and EXOSCALE as not supporting PTR.
testdat
0.0INFRA · APIS
Unit testing for datasets, built on testthat and now bending to its next release.
◆ Current state
testdat applies the testthat idiom to data rather than code: expectations that assert properties of a data frame, run as a suite, with results exportable to Excel. Recent releases have been about correctness and upstream compatibility. Expectations are now constructed via new_expectation() ahead of testthat 3.3.0, and expect_base() errors on a missing variable instead of silently passing.
◆ Where it's heading
The package reached its shape early and has spent the years since sanding it. The design decisions worth noting are all in the past: the move to tidyselect at 0.3.0, the test data pipe at 0.4.0, and the failure messages at 0.4.1 that name which variable failed rather than just reporting a count. Since then activity is sparse and reactive, tracking testthat and R-devel. The two 0.4.3 and 0.4.4 tags arriving ninety minutes apart on the same day is the signature of a release caught by an upstream deadline.
◆ Prediction
The immediate work is finishing the testthat 3.3.0 adaptation. Beyond that the notes give no evidence of new expectation families; the package looks maintained rather than developed.
Alternatives to DNSControl and testdat
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 DNSControl or testdat.
Infisical
A credential platform assembled two or three pull requests at a time, never a headline
SigNoz
Search without knowing the field — SigNoz keeps lowering the cost of not knowing your schema
nmfspalette
A NOAA Fisheries colour palette that ships when the branding guide changes
onemap
A genetic-mapping mainstay that now points new users toward MAPpoly at load time
logbin
Relative-risk regression that converges where glm fails, under an unreadable tag order
See all DNSControl alternatives → · See all testdat alternatives →
Recent activity from DNSControl and testdat
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoDNSControlDNSControl v5 rc9 sets a 25 August ship date, bugfixes only
- 7d agoDNSControlDNSControl v5 rc8 declared feature complete
- 16d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
- 18d agoDNSControlDNSControl v5 rc3 finishes converting every provider
- 27d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
- 29d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
- 9mo agotestdatExpectations rebuilt on new_expectation() for testthat 3.3.0
- 9mo agotestdatexpect_base() errors on a missing variable instead of passing
- 2y agotestdatGrouped data frames ungrouped before testing
- 3y agotestdatFailure messages name the failing variable; expect_depends() added
- 4y agotestdatTest data pipe lets expectations sit inline in a chain
- 4y agotestdatCRAN release moves variable selection to tidyselect ⚡
Frequently asked questions
What is the difference between DNSControl and testdat?
They serve adjacent needs but don't currently overlap on shipped themes. DNSControl is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 DNSControl better than testdat?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DNSControl is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 DNSControl?
Top DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.
What are the best alternatives to testdat?
Top testdat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "testdat alternatives" section above for the current picks, or visit /alternatives/testdat for the full list with editorial commentary on each.