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

chore: Add assertion to infrastructure internal classes test #1164

Conversation

oskogstad
Copy link
Collaborator

@oskogstad oskogstad commented Sep 20, 2024

Description

Adding an assertion on FailingTypes array, if there are failures, the class names will be printed in the fail output

Summary by CodeRabbit

  • Documentation

    • Clarified comments in the architecture test for improved readability.
  • Tests

    • Added a new line before assertions in the test method to enhance structure.

@oskogstad oskogstad requested a review from a team as a code owner September 20, 2024 09:09
Copy link
Contributor

coderabbitai bot commented Sep 20, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

Walkthrough

The pull request introduces minor textual modifications to the All_Classes_In_Infrastructure_Should_Be_Internal test method located in the InfrastructureArchitectureTests.cs file. These changes include a clarification of a comment by removing a comma and rephrasing it. Additionally, a new line has been added before the assertion that verifies whether publicClasses.FailingTypes is empty. The overall logic and functionality of the test remain unchanged, continuing to ensure that specific classes are not public.

Changes

Files Change Summary
tests/.../InfrastructureArchitectureTests.cs Minor textual modifications in the All_Classes_In_Infrastructure_Should_Be_Internal test method, including a clarified comment and an added line before an assertion.

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

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.

knuhau
knuhau previously approved these changes Sep 20, 2024
Copy link

sonarcloud bot commented Sep 20, 2024

@oskogstad oskogstad merged commit 75fbee2 into main Sep 20, 2024
16 of 17 checks passed
@oskogstad oskogstad deleted the chore/add-empty-assertion-on-infrastructure-internal-classes-test branch September 20, 2024 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants