← Back to home
Comparison · Infra & APIs

forestploter vs testdat

A side-by-side editorial comparison of forestploter and testdat — release velocity, themes, recent moves, and the top alternatives to consider.

forestploter vs testdat: at a glance

Featureforestplotertestdat
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesdata-visualization, clinical-trials, forest-plots, meta-analysisdata-validation, unit-testing, testthat, tidyselect
Last editorial update5h ago1h ago
WebsiteVisit →Visit →

What is forestploter?

A forest plot package that keeps handing users control of one more graphical detail.

forestploter draws forest plots where the layout is driven by the data frame itself, so text columns and confidence intervals sit in the same grid. The theme function has become the package's centre of gravity: it now controls graphical parameters for titles, legends, axis, arrow labels, footnotes, and reference lines, with multi-column and row-order legend controls added most recently. Two releases shipped nine minutes apart in April 2026 after a two-year gap, deprecating some theme parameters, removing inter-cell gaps, and improving tick breaks.

Read the full forestploter trajectory →

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.

Read the full testdat trajectory →

forestploter vs testdat: editorial side-by-side

F
forestploter
INFRA · APIS
0.0

A forest plot package that keeps handing users control of one more graphical detail.

◆ Current state

forestploter draws forest plots where the layout is driven by the data frame itself, so text columns and confidence intervals sit in the same grid. The theme function has become the package's centre of gravity: it now controls graphical parameters for titles, legends, axis, arrow labels, footnotes, and reference lines, with multi-column and row-order legend controls added most recently. Two releases shipped nine minutes apart in April 2026 after a two-year gap, deprecating some theme parameters, removing inter-cell gaps, and improving tick breaks.

◆ Where it's heading

The direction has been consistent for four years: whatever a user might want to restyle eventually becomes an argument. Point size stopped being transformed, cell height adjustment was removed as unwanted, legends gained size, column, and fill-order control, and vertical lines learned to extend the full plot height and to draw beneath the whiskers. The one structural move was 1.1.0, which let callers supply their own confidence-interval and summary drawing functions — turning a fixed renderer into an extensible one. Everything since has been the arguments that extensibility did not cover.

◆ Prediction

The latest release deprecates theme parameters rather than adding them, which suggests the next one consolidates the theme surface that has grown for four years rather than extending it further.

T
testdat
INFRA · APIS
0.0

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 forestploter 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 forestploter or testdat.

See all forestploter alternatives → · See all testdat alternatives →

Recent activity from forestploter and testdat

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agoforestploterTheme parameters deprecated; cell gaps removed, ticks improved
  2. 3mo agoforestploterMulti-column legends and full-height vertical lines
  3. 9mo agotestdatExpectations rebuilt on new_expectation() for testthat 3.3.0
  4. 9mo agotestdatexpect_base() errors on a missing variable instead of passing
  5. 2y agoforestploterFull graphical control over titles, legends, axis and footnotes
  6. 2y agoforestploterTick digit calculation improved; automatic cell height removed
  7. 2y agotestdatGrouped data frames ungrouped before testing
  8. 3y agoforestploterCustom CI and summary drawing functions; boxplots inside the plot
  9. 3y agoforestploterArbitrary grobs and math symbols can be placed in cells
  10. 3y agotestdatFailure messages name the failing variable; expect_depends() added
  11. 4y agotestdatTest data pipe lets expectations sit inline in a chain
  12. 4y agotestdatCRAN release moves variable selection to tidyselect

Frequently asked questions

What is the difference between forestploter and testdat?

They serve adjacent needs but don't currently overlap on shipped themes. forestploter 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 forestploter better than testdat?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forestploter 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 forestploter?

Top forestploter alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "forestploter alternatives" section above for the current picks, or visit /alternatives/forestploter 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.