whisper-money

Commit Graph

Author	SHA1	Message	Date
Víctor Falcón	1880333b1c	chore: upgrade Laravel 12 to 13 (#242 ) ## Summary - Upgrade `laravel/framework` from v12 to v13.1.1 and update all 52 dependencies to their latest versions - Bump `laravel/tinker` from v2 to v3.0 (required for Laravel 13 compatibility) - Address Laravel 13 breaking change: add `serializable_classes => false` to `config/cache.php` - Fix cached `Collection` in `routes/web.php` — converted to plain array via `->toArray()` for serialization safety ## Changes \| File \| What changed \| \|------\|-------------\| \| `composer.json` \| Bumped `php ^8.3`, `laravel/framework ^13.0`, `laravel/tinker ^3.0` \| \| `composer.lock` \| 52 packages updated, 1 removed (`symfony/polyfill-php83`) \| \| `config/cache.php` \| Added `serializable_classes => false` \| \| `routes/web.php` \| Cached query result uses `->toArray()`, fallback changed from `collect()` to `[]` \| ## Testing Full test suite passing: 919 tests, 3792 assertions, 0 failures	2026-03-25 12:56:33 +00:00
Víctor Falcón	93f1f82ac5	test: add performance test suite with query count ceilings (#148 ) ## Why ### Problem As new features are added, dashboard and settings pages have been accumulating extra database queries — risking N+1 regressions and degraded response times. There was no automated way to detect these regressions before they reach production. ## What ### Changes - New `Performance` test suite (`tests/Performance/`) with 25 tests that enforce query count ceilings on every page and API endpoint accessible from the sidebar - `PageQueryCountTest.php` — 15 tests covering Dashboard, Accounts, Transactions, Budgets, Cashflow, and all Settings pages, plus scaling tests that prove query count stays constant as data volume grows - `ApiQueryCountTest.php` — 10 tests covering all Dashboard and Cashflow analytics API endpoints, plus scaling tests - Separate CI job (`performance-tests`) that runs in parallel with `tests` and `linter`, and gates both `build-image` and `deploy` - Excluded from the main `tests` job to avoid running them twice (`--exclude-testsuite=Performance`) - Helper functions (`performanceSeedUser`, `countQueries`, `assertMaxQueries`) added to `tests/Pest.php` for reuse - `phpunit.xml` updated with the new `Performance` testsuite entry ### How it works Each test seeds a user with realistic data (3 accounts, 30 transactions, 15 balances, 5 categories, 3 labels, 1 budget) and asserts the endpoint executes at most N queries. Thresholds have a small buffer (~3 queries) above current counts — tight enough to catch N+1 regressions (which add dozens of queries) but loose enough to not break on minor legitimate changes. On failure, every executed SQL query is dumped for easy debugging. ### Run locally ```bash php artisan test --testsuite=Performance ``` ## Verification ### Tests All 25 performance tests pass. Existing Feature (633) and Unit (22) suites unaffected.	2026-02-24 10:47:51 +01:00

Author

SHA1

Message

Date

Víctor Falcón

1880333b1c

chore: upgrade Laravel 12 to 13 (#242 )

## Summary

- Upgrade `laravel/framework` from v12 to **v13.1.1** and update all 52
dependencies to their latest versions
- Bump `laravel/tinker` from v2 to **v3.0** (required for Laravel 13
compatibility)
- Address Laravel 13 breaking change: add `serializable_classes =>
false` to `config/cache.php`
- Fix cached `Collection` in `routes/web.php` — converted to plain array
via `->toArray()` for serialization safety

## Changes

| File | What changed |
|------|-------------|
| `composer.json` | Bumped `php ^8.3`, `laravel/framework ^13.0`,
`laravel/tinker ^3.0` |
| `composer.lock` | 52 packages updated, 1 removed
(`symfony/polyfill-php83`) |
| `config/cache.php` | Added `serializable_classes => false` |
| `routes/web.php` | Cached query result uses `->toArray()`, fallback
changed from `collect()` to `[]` |

## Testing

Full test suite passing: **919 tests, 3792 assertions, 0 failures**

2026-03-25 12:56:33 +00:00

Víctor Falcón

93f1f82ac5

test: add performance test suite with query count ceilings (#148 )

## Why

### Problem

As new features are added, dashboard and settings pages have been
accumulating extra database queries — risking N+1 regressions and
degraded response times. There was no automated way to detect these
regressions before they reach production.

## What

### Changes

- **New `Performance` test suite** (`tests/Performance/`) with 25 tests
that enforce query count ceilings on every page and API endpoint
accessible from the sidebar
- `PageQueryCountTest.php` — 15 tests covering Dashboard, Accounts,
Transactions, Budgets, Cashflow, and all Settings pages, plus scaling
tests that prove query count stays constant as data volume grows
- `ApiQueryCountTest.php` — 10 tests covering all Dashboard and Cashflow
analytics API endpoints, plus scaling tests
- **Separate CI job** (`performance-tests`) that runs in parallel with
`tests` and `linter`, and gates both `build-image` and `deploy`
- **Excluded from the main `tests` job** to avoid running them twice
(`--exclude-testsuite=Performance`)
- Helper functions (`performanceSeedUser`, `countQueries`,
`assertMaxQueries`) added to `tests/Pest.php` for reuse
- `phpunit.xml` updated with the new `Performance` testsuite entry

### How it works

Each test seeds a user with realistic data (3 accounts, 30 transactions,
15 balances, 5 categories, 3 labels, 1 budget) and asserts the endpoint
executes **at most N queries**. Thresholds have a small buffer (~3
queries) above current counts — tight enough to catch N+1 regressions
(which add dozens of queries) but loose enough to not break on minor
legitimate changes. On failure, every executed SQL query is dumped for
easy debugging.

### Run locally

```bash
php artisan test --testsuite=Performance
```

## Verification

### Tests

All 25 performance tests pass. Existing Feature (633) and Unit (22)
suites unaffected.

2026-02-24 10:47:51 +01:00

2 Commits