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

Add test for class-generator scripts #2285

Merged
merged 1 commit into from
Jan 19, 2025
Merged

Add test for class-generator scripts #2285

merged 1 commit into from
Jan 19, 2025

Conversation

myakove
Copy link
Collaborator

@myakove myakove commented Jan 18, 2025

Summary by CodeRabbit

  • Tests

    • Added a new test function to verify generated files retrieval
    • Updated test configuration to run all tests in the class_generator/ directory
  • Refactor

    • Updated type hints in functions using built-in type annotations
    • Modified help text capitalization for command-line options

Copy link

coderabbitai bot commented Jan 18, 2025

Walkthrough

The pull request introduces changes across three files: a new test function in test_scripts.py, type hint updates in tools.py, and a simplified test command configuration in tox.toml. The modifications focus on improving type annotations, consolidating test execution, and adding a new test function to verify file generation. The changes aim to enhance code clarity and streamline testing processes without altering core functionality.

Changes

File Change Summary
class_generator/scripts/tests/test_scripts.py Added new test function test_get_generated_files() to validate generated files by checking for specific dictionary keys
class_generator/scripts/tools.py Updated type hints from Dict and List to dict and list
Modified help text capitalization for --list-generated_file option
tox.toml Replaced multiple specific test commands with a single command to run tests in the class_generator/ directory

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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.

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.

@rh-bot-1
Copy link

Report bugs in Issues

The following are automatically added:

  • Add reviewers from OWNER file (in the root of the repository) under reviewers section.
  • Set PR size label.
  • New issue is created for the PR. (Closed when PR is merged/closed)
  • Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

  • To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
  • To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
  • To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
    verified label removed on each new commit push.
  • To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.
    • Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
    • Cherry-pick will be started when PR is merged
  • To build and push container image command /build-and-push-container in the PR (tag will be the PR number).
    • You can add extra args to the Podman build command
      • Example: /build-and-push-container --build-arg OPENSHIFT_PYTHON_WRAPPER_COMMIT=<commit_hash>
  • To add a label by comment use /<label name>, to remove, use /<label name> cancel
  • To assign reviewers based on OWNERS file use /assign-reviewers
  • To check if PR can be merged use /check-can-merge
  • to assign reviewer to PR use /assign-reviewer @<reviewer>
Supported /retest check runs
  • /retest tox: Retest tox
  • /retest python-module-install: Retest python-module-install
  • /retest all: Retest all
Supported labels
  • hold
  • verified
  • wip
  • lgtm

@myakove
Copy link
Collaborator Author

myakove commented Jan 18, 2025

/verified

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: 0

🔭 Outside diff range comments (1)
class_generator/scripts/tools.py (1)

Line range hint 61-71: Improve error handling in generate_resource.

The current error handling silently continues on any exception. Consider logging the error or handling specific exceptions.

 def generate_resource(kinds: list[str], yes: bool) -> None:
     for _kind in kinds:
         _generate = "y" if yes else click.prompt(f"Do you want to generate {_kind} resource? (y/n) ")
 
         if _generate.lower() == "y":
             try:
                 class_generator(kind=_kind, called_from_cli=False)
-            except Exception:
+            except Exception as exc:
+                click.echo(f"Failed to generate {_kind}: {exc}", err=True)
                 continue
🧹 Nitpick comments (2)
class_generator/scripts/tests/test_scripts.py (1)

4-7: Add docstring and enhance test coverage.

Good use of type hints and safe dictionary access. However, consider these improvements:

  1. Add a docstring explaining the test's purpose
  2. Add assertions to verify the structure and content of the values in the dictionary
 def test_get_generated_files():
+    """
+    Test that get_generated_files returns a dictionary with expected keys
+    and proper file paths for each category.
+    """
     _files: dict[str, dict[str, str]] = get_generated_files()
     for _key in ("with_end_comment", "without_end_comment", "not_generated"):
         assert _files.get(_key), f"{_key} is missing in generated files"
+        # Verify each category contains valid file paths
+        assert isinstance(_files[_key], dict), f"{_key} value is not a dictionary"
+        for kind, path in _files[_key].items():
+            assert isinstance(kind, str), f"Invalid kind type in {_key}"
+            assert isinstance(path, str), f"Invalid path type in {_key}"
+            assert path.endswith(".py"), f"Invalid file extension in {_key}: {path}"
class_generator/scripts/tools.py (1)

20-22: Add type hints for dictionary values.

The type hints for the dictionaries are good, but consider being more specific about the value types.

-    resources_with_end_comment: dict[str, str] = {}
-    resources_without_end_comment: dict[str, str] = {}
-    resources_not_generated: dict[str, str] = {}
+    ResourceDict = dict[str, str]  # Type alias for better readability
+    resources_with_end_comment: ResourceDict = {}
+    resources_without_end_comment: ResourceDict = {}
+    resources_not_generated: ResourceDict = {}
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b9877b3 and 28d68c2.

📒 Files selected for processing (3)
  • class_generator/scripts/tests/test_scripts.py (1 hunks)
  • class_generator/scripts/tools.py (6 hunks)
  • tox.toml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: tox
  • GitHub Check: python-module-install
🔇 Additional comments (1)
tox.toml (1)

30-30: LGTM! Good simplification of test commands.

The change to run all tests in the class_generator/ directory is a good improvement that:

  • Reduces maintenance by avoiding explicit file listing
  • Automatically includes new test files
  • Follows common pytest test discovery practices

class_generator/scripts/tools.py Show resolved Hide resolved
@myakove myakove merged commit e5328ad into main Jan 19, 2025
6 checks passed
@myakove myakove deleted the classg-scripts-test branch January 19, 2025 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants