[tests] Basic unit test coverage for Torch.Component

[diogenes]

Adding some simple tests for Torch.Component, aiming fixing the issue #393.

Summary by CodeRabbit

• Tests
  • Added comprehensive tests for UI components and helper functions, including input fields, labels, error messages, and flash messages, to ensure correct rendering and behavior.

[coderabbitai[bot]]

Walkthrough

A new test module, Torch.ComponentTest, has been added to the codebase. This module contains a comprehensive suite of tests for various UI components and helper functions defined in the Torch.Component module. The tests utilize ExUnit and Phoenix LiveView testing utilities to verify the correct rendering and behavior of form inputs, labels, error messages, and flash messages. Additionally, the tests cover error translation functions, ensuring they handle different input scenarios as expected.

Changes

File(s)	Change Summary
test/torch/component_test.exs	Added a new test module with multiple test cases for UI components and helper functions in Torch.Component.

Sequence Diagram(s)

sequenceDiagram
    participant TestCase
    participant Torch.Component
    participant Phoenix.LiveView
    participant RenderedHTML

    TestCase->>Torch.Component: Call component function (e.g., torch_input/1)
    Torch.Component->>Phoenix.LiveView: Render component with given assigns
    Phoenix.LiveView->>RenderedHTML: Generate HTML output
    TestCase->>RenderedHTML: Assert expected HTML structure and content

sequenceDiagram
    participant TestCase
    participant Torch.Component

    TestCase->>Torch.Component: Call translate_error/1 or translate_errors/2
    Torch.Component-->>TestCase: Return translated error message(s)
    TestCase->>TestCase: Assert expected translation output

[!TIP]

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
• @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.

[diogenes]

@cpjolicoeur Does this approach make sense for issue #393 ?

[cpjolicoeur]

@diogenes I think this is probably the right direction. As long as we are testing the edges of each component, and ensuring the inputs appear in the outputs, this shoudl work