Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update tests #24

Closed
wants to merge 3 commits into from
Closed

fix: update tests #24

wants to merge 3 commits into from

Conversation

bmazzarol
Copy link
Owner

@bmazzarol bmazzarol commented Feb 2, 2025

Summary by CodeRabbit

  • Chores

    • Upgraded several dependency packages to their latest versions, enhancing performance, stability, and security.
    • Removed the FluentAssertions package reference from the project.
    • Adjusted build configuration for improved test execution.
  • Tests

    • Standardized test validations to use the built-in framework for consistent results.
    • Updated assertions across various test methods to utilize standard Xunit assertions instead of FluentAssertions.

@bmazzarol bmazzarol added the enhancement New feature or request label Feb 2, 2025
@bmazzarol bmazzarol self-assigned this Feb 2, 2025
Copy link

coderabbitai bot commented Feb 2, 2025

Warning

Rate limit exceeded

@bmazzarol has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 48 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 5f7e350 and 37d807b.

📒 Files selected for processing (1)
  • Tuxedo.Tests/Tuxedo.Tests.csproj (1 hunks)

Walkthrough

This pull request updates dependency versions and standardizes test assertions. In the source generator project, package references are upgraded. Meanwhile, multiple test files have been refactored to replace FluentAssertions with standard Xunit assertions, including adjustments to error message verifications. The test project file is updated to include several dependency version bumps, package removals, and the addition of a new using directive. One test file also updates a method’s access modifier from private to internal.

Changes

File(s) Change Summary
Tuxedo.SourceGenerator/…csproj Updated package references: Meziantou.Analyzer (2.0.177 → 2.0.186), Roslynator.Analyzers (4.12.9 → 4.12.11), SonarAnalyzer.CSharp (9.32.0.97167 → 10.6.0.109712), Microsoft.CodeAnalysis.CSharp (4.11.0 → 4.12.0).
Tuxedo.Tests/Tuxedo.Tests.csproj Set <OutputType> to Exe; updated dependency versions for Microsoft.NET.Test.Sdk (17.11.1 → 17.12.0), Verify.XunitVerify.XunitV3 (28.7.0 → 28.9.0), xunitxunit.v3 (2.9.2 → 1.0.1), xunit.runner.visualstudio (2.8.2 → 3.0.1); removed FluentAssertions and added a <Using Include="Xunit" /> directive; updated Microsoft.CodeAnalysis.CSharp.
Tuxedo.Tests/{AnalyserTests, BoolRefinementsTests, CustomAccessModifierTests, CustomTypeRefinementTests, DateOnlyExample, GuidStringTests, NonEmptyListTests, OddNumberExample, SafeRangeExample, SingletonTypeExample}.cs Replaced FluentAssertions with standard Xunit assertions; adjusted diagnostic and error verifications.
Tuxedo.Tests/PasswordStringExample.cs Replaced FluentAssertions with Xunit assertions and changed the access modifier for IsValidPassword from private to internal.

Poem

I'm a little rabbit hopping through the code,
Leaving behind old asserts on a winding road.
Upgraded packages and tests so neat,
With Xunit now making each check complete.
I nibble on changes with a happy, twitching smile—
Software gardens bloom in every style!
🥕🐇


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

github-actions bot commented Feb 2, 2025

Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 37d807b.

♻️ This comment has been updated with latest results.

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 2, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 73e865a and 5f7e350.

📒 Files selected for processing (2)
  • Tuxedo.Tests/AnalyserTests.cs (2 hunks)
  • Tuxedo.Tests/Tuxedo.Tests.csproj (1 hunks)
🧰 Additional context used
🪛 GitHub Actions: CI Build
Tuxedo.Tests/Tuxedo.Tests.csproj

[warning] 1-1: Package 'Microsoft.CodeAnalysis.CSharp.Workspaces 1.0.1' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net8.0'. This package may not be fully compatible with your project.


[warning] 1-1: Package 'Microsoft.CodeAnalysis.Workspaces.Common 1.0.1' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net8.0'. This package may not be fully compatible with your project.


[warning] 1-1: Package 'Microsoft.Composition 1.0.27' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net8.0'. This package may not be fully compatible with your project.


[error] 1-1: Version conflict detected for xunit.extensibility.core. Install/reference xunit.extensibility.core 2.9.3 directly to project Tuxedo.Tests to resolve this issue.


[error] 1-1: Tuxedo.Tests -> Verify.Xunit 28.9.0 -> xunit.extensibility.execution 2.9.3 -> xunit.extensibility.core (= 2.9.3).


[error] 1-1: Tuxedo.Tests -> xunit 2.9.2 -> xunit.core 2.9.2 -> xunit.extensibility.core (= 2.9.2).

🔇 Additional comments (4)
Tuxedo.Tests/AnalyserTests.cs (2)

163-164: LGTM! Clean transition to standard Xunit assertions.

The changes correctly replace FluentAssertions with standard Xunit assertions while maintaining the same verification logic.


232-236: LGTM! Clean transition to standard Xunit assertions.

The changes correctly replace FluentAssertions with standard Xunit assertions while maintaining the same verification logic.

Tuxedo.Tests/Tuxedo.Tests.csproj (2)

31-33: LGTM! Good addition of global using directive.

The addition of the global using directive for Xunit aligns well with the removal of FluentAssertions and standardization of test assertions.


23-23: Verify compatibility with .NET 8.

The pipeline shows warnings about package compatibility with .NET 8.0.

Run the following script to check for newer versions that might be more compatible:

Tuxedo.Tests/Tuxedo.Tests.csproj Show resolved Hide resolved
Copy link

sonarqubecloud bot commented Feb 2, 2025

@bmazzarol
Copy link
Owner Author

Not building atm

@bmazzarol bmazzarol closed this Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant