fix(test): move misplaced budget override validity anchor tests to correct describe block - #6048
Merged
Merged
Conversation
impoiler
marked this pull request as ready for review
August 11, 2026 07:43
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe change adds test coverage for calendar-aligned budget override validity. The tests verify that monthly, weekly, daily, and yearly schedules anchor validity to the next period boundary. ChangesBudget override validation
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Aug 11, 2026
Contributor
Merge activity
|
akshaydeo
pushed a commit
that referenced
this pull request
Aug 13, 2026
…rrect describe block (#6048) ## Summary A test for calendar-aligned budget override validity was accidentally nested inside an unrelated `it` block in the `budgetSignature without ids` describe block, causing it to never actually run. This PR moves the test to the correct location within the `budget overrides` describe block. ## Changes - Removed the misplaced `it("anchors calendar-aligned validity to the current period boundary", ...)` block that was nested inside the `budgetSignature without ids` test, where it would never execute - Added the same test cases correctly at the top level of the `budget overrides` describe block, where they are properly registered and run ## Type of change - [x] Bug fix ## Affected areas - [x] UI (React) ## How to test ```sh cd ui pnpm i || npm i pnpm test || npm test ``` The previously dormant test cases for `getBudgetOverrideValidUntil` with monthly, weekly, daily, and yearly reset durations should now execute and pass. ## Breaking changes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [x] I added/updated tests where appropriate - [ ] I updated documentation where needed - [x] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable
akshaydeo
pushed a commit
that referenced
this pull request
Aug 13, 2026
…rrect describe block (#6048) ## Summary A test for calendar-aligned budget override validity was accidentally nested inside an unrelated `it` block in the `budgetSignature without ids` describe block, causing it to never actually run. This PR moves the test to the correct location within the `budget overrides` describe block. ## Changes - Removed the misplaced `it("anchors calendar-aligned validity to the current period boundary", ...)` block that was nested inside the `budgetSignature without ids` test, where it would never execute - Added the same test cases correctly at the top level of the `budget overrides` describe block, where they are properly registered and run ## Type of change - [x] Bug fix ## Affected areas - [x] UI (React) ## How to test ```sh cd ui pnpm i || npm i pnpm test || npm test ``` The previously dormant test cases for `getBudgetOverrideValidUntil` with monthly, weekly, daily, and yearly reset durations should now execute and pass. ## Breaking changes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [x] I added/updated tests where appropriate - [ ] I updated documentation where needed - [x] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable
18 tasks
akshaydeo
pushed a commit
that referenced
this pull request
Aug 14, 2026
…rrect describe block (#6048) ## Summary A test for calendar-aligned budget override validity was accidentally nested inside an unrelated `it` block in the `budgetSignature without ids` describe block, causing it to never actually run. This PR moves the test to the correct location within the `budget overrides` describe block. ## Changes - Removed the misplaced `it("anchors calendar-aligned validity to the current period boundary", ...)` block that was nested inside the `budgetSignature without ids` test, where it would never execute - Added the same test cases correctly at the top level of the `budget overrides` describe block, where they are properly registered and run ## Type of change - [x] Bug fix ## Affected areas - [x] UI (React) ## How to test ```sh cd ui pnpm i || npm i pnpm test || npm test ``` The previously dormant test cases for `getBudgetOverrideValidUntil` with monthly, weekly, daily, and yearly reset durations should now execute and pass. ## Breaking changes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [x] I added/updated tests where appropriate - [ ] I updated documentation where needed - [x] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable
akshaydeo
pushed a commit
that referenced
this pull request
Aug 19, 2026
…rrect describe block (#6048) ## Summary A test for calendar-aligned budget override validity was accidentally nested inside an unrelated `it` block in the `budgetSignature without ids` describe block, causing it to never actually run. This PR moves the test to the correct location within the `budget overrides` describe block. ## Changes - Removed the misplaced `it("anchors calendar-aligned validity to the current period boundary", ...)` block that was nested inside the `budgetSignature without ids` test, where it would never execute - Added the same test cases correctly at the top level of the `budget overrides` describe block, where they are properly registered and run ## Type of change - [x] Bug fix ## Affected areas - [x] UI (React) ## How to test ```sh cd ui pnpm i || npm i pnpm test || npm test ``` The previously dormant test cases for `getBudgetOverrideValidUntil` with monthly, weekly, daily, and yearly reset durations should now execute and pass. ## Breaking changes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [x] I added/updated tests where appropriate - [ ] I updated documentation where needed - [x] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
A test for calendar-aligned budget override validity was accidentally nested inside an unrelated
itblock in thebudgetSignature without idsdescribe block, causing it to never actually run. This PR moves the test to the correct location within thebudget overridesdescribe block.Changes
it("anchors calendar-aligned validity to the current period boundary", ...)block that was nested inside thebudgetSignature without idstest, where it would never executebudget overridesdescribe block, where they are properly registered and runType of change
Affected areas
How to test
The previously dormant test cases for
getBudgetOverrideValidUntilwith monthly, weekly, daily, and yearly reset durations should now execute and pass.Breaking changes
Related issues
Security considerations
None.
Checklist
docs/contributing/README.mdand followed the guidelines