Skip to content

fix(test): move misplaced budget override validity anchor tests to correct describe block - #6048

Merged
akshaydeo merged 1 commit into
devfrom
08-11-fix_fix_governance.test.ts_file
Aug 11, 2026
Merged

fix(test): move misplaced budget override validity anchor tests to correct describe block#6048
akshaydeo merged 1 commit into
devfrom
08-11-fix_fix_governance.test.ts_file

Conversation

@impoiler

Copy link
Copy Markdown
Contributor

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

  • Bug fix

Affected areas

  • UI (React)

How to test

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

  • No

Related issues

Security considerations

None.

Checklist

  • I read docs/contributing/README.md and followed the guidelines
  • I added/updated tests where appropriate
  • I updated documentation where needed
  • I verified builds succeed (Go and UI)
  • I verified the CI pipeline passes locally if applicable

@impoiler
impoiler marked this pull request as ready for review August 11, 2026 07:43
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 02fe09ca-f06c-4c94-96ab-415136b5fb54

📥 Commits

Reviewing files that changed from the base of the PR and between 0f8eea3 and f13571c.

📒 Files selected for processing (1)
  • ui/lib/utils/governance.test.ts

📝 Walkthrough

Summary by CodeRabbit

  • Tests
    • Added coverage for calendar-aligned budget override validity across monthly, weekly, daily, and yearly schedules.
    • Reorganized related test cases without changing application behavior.

Walkthrough

The 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.

Changes

Budget override validation

Layer / File(s) Summary
Calendar boundary validity tests
ui/lib/utils/governance.test.ts
Adds assertions for monthly, weekly, daily, and yearly reset durations. The existing test block was relocated without changing its assertions or behavior.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: akshaydeo, danpiths

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the test fix and the move of misplaced budget override validity tests.
Description check ✅ Passed The description explains the problem, changes, testing steps, affected area, and breaking-change status; optional sections are adequately addressed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 08-11-fix_fix_governance.test.ts_file

Comment @coderabbitai help to get the list of available commands.

@impoiler impoiler self-assigned this Aug 11, 2026

impoiler commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai
coderabbitai Bot requested review from akshaydeo and danpiths August 11, 2026 07:44

akshaydeo commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Merge activity

  • Aug 11, 8:40 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Aug 11, 8:40 AM UTC: @akshaydeo merged this pull request with Graphite.

@akshaydeo
akshaydeo merged commit 0d55aea into dev Aug 11, 2026
15 checks passed
@akshaydeo
akshaydeo deleted the 08-11-fix_fix_governance.test.ts_file branch August 11, 2026 08:40
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
@coderabbitai coderabbitai Bot mentioned this pull request Aug 13, 2026
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants