github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #5964] Refactor test execution to use lage task runner #6239

New Issue
Closed
opened 2026-02-28 21:25:41 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:25:41 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/actualbudget/actual/pull/5964

State: closed
Merged: Yes

This PR refactors the test execution infrastructure to use lage, a task runner for JavaScript monorepos.

It significantly improves the local dev-experience as well as makes them more performant by utilising local cache.

Additionally - this change makes the test output actually readable in CI/CD.

Screenshot 2025-10-19 at 21 29 07

Changes

  • Added: Configuration for lage task orchestration with support for , , and tasks
  • Updated: Modified test scripts to use lage instead of yarn workspaces foreach
    • yarn test → lage test --verbose
    • yarn test:debug → lage test --verbose --no-cache
  • Updated: Added documentation about lage and updated testing examples

Benefits

  • Parallel execution: Tests run in parallel across workspaces for faster feedback
  • Smart caching: Caches test results to skip unchanged packages (can be disabled with --no-cache)
  • Dependency awareness: Understands workspace dependencies and execution order
  • Better CI performance: Potential for faster CI runs with caching

Backward Compatibility

All existing yarn workspace <package> test commands continue to work as before. The lage integration is additive and doesn't break existing workflows.

**Original Pull Request:** https://github.com/actualbudget/actual/pull/5964 **State:** closed **Merged:** Yes --- This PR refactors the test execution infrastructure to use [lage](https://microsoft.github.io/lage/), a task runner for JavaScript monorepos. It significantly improves the local dev-experience as well as makes them more performant by utilising local cache. Additionally - this change makes the test output actually readable in CI/CD. <img width="539" height="283" alt="Screenshot 2025-10-19 at 21 29 07" src="https://github.com/user-attachments/assets/95a1b621-c4b4-41bf-bddc-8c5911d3f858" /> ## Changes - **Added**: Configuration for lage task orchestration with support for , , and tasks - **Updated**: Modified test scripts to use lage instead of `yarn workspaces foreach` - `yarn test` → `lage test --verbose` - `yarn test:debug` → `lage test --verbose --no-cache` - **Updated**: Added documentation about lage and updated testing examples ## Benefits - **Parallel execution**: Tests run in parallel across workspaces for faster feedback - **Smart caching**: Caches test results to skip unchanged packages (can be disabled with `--no-cache`) - **Dependency awareness**: Understands workspace dependencies and execution order - **Better CI performance**: Potential for faster CI runs with caching ## Backward Compatibility All existing `yarn workspace <package> test` commands continue to work as before. The lage integration is additive and doesn't break existing workflows.
GiteaMirror added the pull-request label 2026-02-28 21:25:41 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#6239
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?