Test: add unit tests for Clinic entity to check getters/setter and co…

[TatjanaTrajkovic]

…nstructor

Summary by CodeRabbit

• Tests
  • Added comprehensive test coverage for Clinic entity getters and setters, including validation of name, address, and phone number properties.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bd4c40fd-f3d6-4d30-bff2-5d03fc4b01fa

📥 Commits

Reviewing files that changed from the base of the PR and between e652c86 and 94ac1fb.

📒 Files selected for processing (1)

• src/test/java/org/example/vet1177/entities/ClinicTest.java

---

📝 Walkthrough

Walkthrough

A new JUnit 5 test class ClinicTest is added to verify the Clinic entity's constructor, getters, and setters. Two test methods validate that properties (name, address, phone number) are correctly set and retrieved through their respective accessor methods.

Changes

Cohort / File(s)	Summary
Clinic Test Suite src/test/java/org/example/vet1177/entities/ClinicTest.java	New test class with two test methods verifying Clinic constructor initialization and getter/setter functionality for name, address, and phone number properties.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related issues

• Test: Add Unit test for Clinic enity #158: Adds complementary JUnit tests for the Clinic entity's getter and setter methods, addressing the same test coverage objectives.

Possibly related PRs

• feat: initial setup with entities(User, Clinic) and config #3: Introduces the Clinic class that these tests directly exercise through constructor, getter, and setter verification.

Suggested labels

test

Suggested reviewers

• johanbriger
• lindaeskilsson

Poem

🐰 A clinic's tale now tested true,
With getters, setters shining new,
Each assertion hops with grace,
JUnit five runs at lightning pace!
The Clinic class, now proven sound,
Our testing warren's fertile ground. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding unit tests for the Clinic entity to verify getters, setters, and constructor functionality.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test/unit_tests_clinic_enitity

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[lindaeskilsson]

Looks good!