Skip to content

Run Reporting tests in CI - #343

Merged
Yuri05 merged 1 commit into
developfrom
enable-reporting-tests
Jul 16, 2026
Merged

Run Reporting tests in CI#343
Yuri05 merged 1 commit into
developfrom
enable-reporting-tests

Conversation

@rwmcintosh

Copy link
Copy Markdown
Member

Fixes #342

The --filter TestCategory!=Reporting exclusion (in build-and-test.yml and build-nightly_13.0.yml) was added in #287 when reporting used MiKTeX/LaTeX, which isn't installed on the CI runners. #325 replaced reporting with Markdown + QuestPDF (pure .NET, no external dependency), so the [Category("Reporting")] tests can now run headlessly.

Dropped the filter from both workflows so the reporting tests run in CI. This also serves as the runtime verification that QuestPDF/Markdown reporting works on the .NET 10 line — if any reporting test fails here, that's a real gap to fix.

🤖 Generated with Claude Code

The TestCategory!=Reporting filter was added when reporting needed MiKTeX/LaTeX
(unavailable on CI runners). #325 replaced that with Markdown + QuestPDF, which
has no external dependency, so the reporting tests can run headlessly. Drop the
filter from build-and-test and the nightly.

Fixes #342
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@rwmcintosh, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 53b7cf5c-af65-48e3-89e3-765b841e8db1

📥 Commits

Reviewing files that changed from the base of the PR and between 511dd0e and 2039159.

📒 Files selected for processing (2)
  • .github/workflows/build-and-test.yml
  • .github/workflows/build-nightly_13.0.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch enable-reporting-tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@rwmcintosh
rwmcintosh requested a review from Yuri05 July 16, 2026 17:23
@rwmcintosh rwmcintosh self-assigned this Jul 16, 2026
@Yuri05

Yuri05 commented Jul 16, 2026

Copy link
Copy Markdown
Member

nice!

@Yuri05
Yuri05 merged commit 0026c77 into develop Jul 16, 2026
2 checks passed
@Yuri05
Yuri05 deleted the enable-reporting-tests branch July 16, 2026 17:32
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.

Re-enable Reporting tests in CI (no longer need MiKTeX after QuestPDF migration)

2 participants