incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
Comparison · Infra & APIs
onemap vs testdat
A side-by-side editorial comparison of onemap and testdat — release velocity, themes, recent moves, and the top alternatives to consider.
onemap vs testdat: at a glance
What is onemap?
A genetic-mapping mainstay that now points new users toward MAPpoly at load time
OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.
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.
onemap vs testdat: editorial side-by-side
onemap
0.0INFRA · APIS
A genetic-mapping mainstay that now points new users toward MAPpoly at load time
◆ Current state
OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.
◆ Where it's heading
Versions 3.0.0 and 3.1.0 were driven by a benchmarking preprint on genotyping-by-sequencing best practice, and their content follows directly: marker filtering from two-point estimates, memory reduction after filtering, and optimisation of find_bins and map_avoid_unlinked. What has happened since is signposting rather than capability — a package that spent two releases integrating with MAPpoly now tells users about it every time it loads. The pre-3.0 tags are backfilled, with versions 2.3 through 2.7 sharing a single August 2021 timestamp, so their order carries no information.
◆ Prediction
The load-message announcement suggests attention is flowing toward the MAPpoly side of the toolchain; expect maintenance and compatibility releases here rather than new mapping algorithms.
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 onemap 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 onemap or testdat.
Warp
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
tealeaves
A leaf-temperature model that finished its job in 2020 and has stayed finished
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
See all onemap alternatives → · See all testdat alternatives →
Recent activity from onemap and testdat
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9mo agotestdatExpectations rebuilt on new_expectation() for testthat 3.3.0
- 9mo agotestdatexpect_base() errors on a missing variable instead of passing
- 1y agoonemapMAPpoly announcement added to README and load message
- 2y agotestdatGrouped data frames ungrouped before testing
- 3y agoonemapExports to VIEWpoly and QTLpoly; marker ordering and map summaries
- 3y agoonemapTwo-point marker filtering and memory reduction
- 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 ⚡
- 4y agoonemapPSOCK and FORK parallelization choice; vcfR as an import
- 5y agoonemaphmm=FALSE option for ordering algorithms
- 5y agoonemapMDSMap dependency removed
Frequently asked questions
What is the difference between onemap and testdat?
They serve adjacent needs but don't currently overlap on shipped themes. onemap and testdat are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is onemap better than testdat?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. onemap and testdat are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to onemap?
Top onemap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "onemap alternatives" section above for the current picks, or visit /alternatives/onemap 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.