← Back to home
Comparison · Infra & APIs

discretetests vs portfoliobacktest

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

Shared themes:r-package

discretetests vs portfoliobacktest: at a glance

Featurediscretetestsportfoliobacktest
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesstatistical-testing, exact-tests, nonparametric, r-packagequantitative-finance, backtesting, portfolio-optimization, r-package
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is discretetests?

Four years of releases land in four minutes as the changelog gets backfilled to GitHub

DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.

Read the full discretetests trajectory →

What is portfoliobacktest?

Four dormant years end with a test fix, not a feature

portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.

Read the full portfoliobacktest trajectory →

discretetests vs portfoliobacktest: editorial side-by-side

D
discretetests
INFRA · APIS
0.0

Four years of releases land in four minutes as the changelog gets backfilled to GitHub

◆ Current state

DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.

◆ Where it's heading

Read by version rather than by timestamp, the package grew from binomial, Fisher, McNemar and Poisson tests into rank-based and resampling territory: Wilcoxon signed rank and rank sum, Mann-Whitney U, a conditional homogeneity test, then sign tests and a general permutation test with several built-in statistics. Alongside that the result class was extended to hold ragged observation lists and computational detail, the print output was rewritten on cli, and the old dot-separated function names were made defunct.

◆ Prediction

The permutation test with pluggable statistics is the most open-ended addition here, and adding further built-in statistics to it is the cheapest way to extend the package from where it now stands.

P
portfoliobacktest
INFRA · APIS
0.0

Four dormant years end with a test fix, not a feature

◆ Current state

portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.

◆ Where it's heading

The development work is behind it. The 2019 to 2022 releases built the substance — parallel execution, resampling that works beyond stock data and beyond daily bars, transaction-cost-aware designs through w_current, and a switch from compounded to uncompounded returns in the Sharpe and annualized return calculations. Since then the package has moved only when a dependency forced it, and even then only far enough to keep the tests green.

◆ Prediction

Nothing in the entries suggests planned work; the next release is most likely triggered by another dependency change, on the same four-year-gap pattern.

Alternatives to discretetests and portfoliobacktest

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 discretetests or portfoliobacktest.

See all discretetests alternatives → · See all portfoliobacktest alternatives →

Recent activity from discretetests and portfoliobacktest

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

  1. 2mo agodiscretetestsSign tests and a pluggable permutation test
  2. 2mo agodiscretetestsInput observation names carried through results
  3. 2mo agodiscretetestsWilcoxon, Mann-Whitney and homogeneity tests join the package
  4. 2mo agodiscretetestsmacOS compilation fix
  5. 3mo agoportfoliobacktestTests fixed for a PerformanceAnalytics breaking change
  6. 4y agoportfoliobacktestSharpe ratio charts and reworked weight outputs
  7. 4y agoportfoliobacktestUncompounded return metrics and transaction-cost-aware designs
  8. 5y agoportfoliobacktestResampling generalised beyond daily stock data
  9. 6y agoportfoliobacktestCRAN example fixes and vignette references
  10. 6y agoportfoliobacktestDrawdown, cumulative return and stacked bar charts

Frequently asked questions

What is the difference between discretetests and portfoliobacktest?

Both compete on the same themes — r-package — within Infra & APIs. discretetests and portfoliobacktest 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 discretetests better than portfoliobacktest?

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

Top discretetests alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "discretetests alternatives" section above for the current picks, or visit /alternatives/discretetests for the full list with editorial commentary on each.

What are the best alternatives to portfoliobacktest?

Top portfoliobacktest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "portfoliobacktest alternatives" section above for the current picks, or visit /alternatives/portfoliobacktest for the full list with editorial commentary on each.