Skip to content

calculator tests - #4

Merged
NamigGadir merged 1 commit into
mainfrom
tech/add_new_tests_divide
Jul 28, 2025
Merged

calculator tests#4
NamigGadir merged 1 commit into
mainfrom
tech/add_new_tests_divide

Conversation

@NamigGadir

@NamigGadir NamigGadir commented Jul 28, 2025

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

  • New Features

    • Added division functionality to the calculator.
  • Tests

    • Introduced a new test to verify correct results from the division feature.

@coderabbitai

coderabbitai Bot commented Jul 28, 2025

Copy link
Copy Markdown

Walkthrough

A new divide method was added to the Calculator class to perform integer division. Corresponding unit test coverage was introduced in the CalculatorTest class to verify the correctness of this new method.

Changes

Cohort / File(s) Change Summary
Calculator class update
app/src/main/java/com/coderabbit/app/calculator/Calculator.kt
Added a public divide(a: Int, b: Int): Int method to perform integer division.
Unit test addition
app/src/test/java/com/coderabbit/app/calculator/CalculatorTest.kt
Added a test method to assert that divide(4, 2) returns 2, verifying the new divide method works.

Sequence Diagram(s)

sequenceDiagram
    participant Test as CalculatorTest
    participant Calc as Calculator

    Test->>Calc: divide(4, 2)
    Calc-->>Test: 2
    Test->>Test: assertEquals(2, result)
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

  • test added #1: Introduced the initial Calculator class with an add method and its test; this PR extends the same class by adding the divide method and its test.

Poem

In the land of sums and math delight,
A rabbit hopped in, coding through the night.
Division arrived, crisp and true—
Four divided by two, the answer is two!
With tests in place, all bugs take flight,
Calculator’s joy shines ever so bright.
🥕➗

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch tech/add_new_tests_divide

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests 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.

@NamigGadir

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 28, 2025

Copy link
Copy Markdown
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f730892 and b20a5f4.

📒 Files selected for processing (2)
  • app/src/main/java/com/coderabbit/app/calculator/Calculator.kt (1 hunks)
  • app/src/test/java/com/coderabbit/app/calculator/CalculatorTest.kt (1 hunks)

Comment on lines +9 to +11
fun divide(a: Int, b: Int): Int {
return a/b
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue

Critical: Missing division by zero validation.

The divide method will throw an ArithmeticException when b is zero, which could crash the application. Add proper validation to handle this edge case.

Apply this diff to add division by zero validation:

 fun divide(a: Int, b: Int): Int {
+    if (b == 0) {
+        throw IllegalArgumentException("Division by zero is not allowed")
+    }
     return a/b
 }

Alternatively, consider returning a nullable result or using a Result wrapper:

fun divide(a: Int, b: Int): Int? {
    return if (b == 0) null else a / b
}
🤖 Prompt for AI Agents
In app/src/main/java/com/coderabbit/app/calculator/Calculator.kt around lines 9
to 11, the divide function lacks validation for division by zero, which can
cause an ArithmeticException and crash the app. Add a check to verify if the
divisor b is zero before performing the division. If b is zero, either throw a
custom exception, return null, or use a Result wrapper to safely handle this
edge case and prevent runtime crashes.

Comment on lines +21 to +25
@Test
fun `test divide function equals`() {
val calculator = Calculator()
assertEquals(calculator.divide(4,2) ,2)
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Test structure looks good, but coverage is incomplete.

The basic divide test follows the established pattern and correctly validates the happy path. However, comprehensive testing for division requires additional edge cases.

Add these additional test cases for comprehensive coverage:

@Test
fun `test divide by zero throws exception`() {
    val calculator = Calculator()
    assertThrows(IllegalArgumentException::class.java) {
        calculator.divide(4, 0)
    }
}

@Test
fun `test divide negative numbers`() {
    val calculator = Calculator()
    assertEquals(calculator.divide(-4, 2), -2)
    assertEquals(calculator.divide(4, -2), -2)
    assertEquals(calculator.divide(-4, -2), 2)
}

@Test
fun `test integer division truncation`() {
    val calculator = Calculator()
    assertEquals(calculator.divide(5, 2), 2) // 5/2 = 2.5 → 2
    assertEquals(calculator.divide(1, 2), 0) // 1/2 = 0.5 → 0
}

Note: You'll also need to add this import for assertThrows:

import org.junit.Assert.assertThrows
🤖 Prompt for AI Agents
In app/src/test/java/com/coderabbit/app/calculator/CalculatorTest.kt around
lines 21 to 25, the existing divide function test only covers the basic case. To
improve coverage, add tests for division by zero that assert an
IllegalArgumentException is thrown, tests for dividing negative numbers with
expected signed results, and tests for integer division truncation verifying
correct floor behavior. Also, add the import statement for assertThrows from
org.junit.Assert to support exception testing.

@NamigGadir

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 28, 2025

Copy link
Copy Markdown
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@NamigGadir
NamigGadir merged commit 0068cae into main Jul 28, 2025
2 checks passed
This was referenced Jul 28, 2025
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.

1 participant