feat : depend on test containers to run integrationtest

[rajadilipkolli]

Summary by CodeRabbit

• New Features

  • Added a new configuration for launching a Java application in VS Code.

• Improvements

  • Updated PostgreSQL container version for better performance and stability.

• Chores

  • Removed Redis startup via Docker Compose in GitHub workflows to streamline the build process.
  • Enhanced test application with Redis container configuration for improved testing capabilities.

[coderabbitai]

Walkthrough

The recent updates enhance the testing environment by refining Redis setup and configurations. Redis startup via Docker Compose has been replaced with Testcontainers integration in the Java test application. VS Code now includes a new launch configuration for the Spring Boot application, and the PostgreSQL container version has been updated for testing reliability.

Changes

File Path	Change Summary
.github/workflows/boot-jpa-hibernate2ndlevelcache-sample.yml	Removed Redis startup via Docker Compose; retained build and analyze step.
.vscode/launch.json	Added a new configuration for launching "Spring Boot-TestApplication".
jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/TestApplication.java	Added imports for file handling, service connection, and container configuration; introduced redisContainer() method for Redis container setup.
jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/common/ContainersConfig.java	Updated PostgreSQL container version from "16.2-alpine" to "16.3-alpine".
boot-ultimate-redis/src/test/java/com/example/ultimateredis/TestUltimateRedisApplication.java	Corrected variable name from redisContiner to redisContainer; ensured correct type declaration for GenericContainer.

In code we trust, with changes bright,
Redis now in containers, a delight.
PostgreSQL updated, fresh and new,
Spring Boot app launches with a cue.
In this realm of bits and bytes,
Our journey continues, scaling heights.
🐇✨

---

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

• 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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

[coderabbitai]

Actionable comments posted: 1

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7935367 and 1c68847.

Files selected for processing (4)

• .github/workflows/boot-jpa-hibernate2ndlevelcache-sample.yml (1 hunks)
• .vscode/launch.json (1 hunks)
• jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/TestApplication.java (1 hunks)
• jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/common/ContainersConfig.java (1 hunks)

Files skipped from review due to trivial changes (2)

• .github/workflows/boot-jpa-hibernate2ndlevelcache-sample.yml
• .vscode/launch.json

Additional comments not posted (2)

jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/common/ContainersConfig.java (1)

9-9: Update to PostgreSQL version "16.3-alpine" approved.

Verification successful

---

Update to PostgreSQL version "16.3-alpine" approved. Please manually verify the compatibility of the new PostgreSQL version with the existing application to ensure there are no unforeseen issues.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify compatibility of PostgreSQL version "16.3-alpine" with the application.

# Test: Check for any specific version dependencies in the application configuration.
rg --type java 'PostgreSQLContainer' --context 5

Length of output: 54648

jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/TestApplication.java (1)

4-14: Imports for file handling and container management are appropriate.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1c68847 and 1d95d7d.

Files selected for processing (2)

• boot-ultimate-redis/src/test/java/com/example/ultimateredis/TestUltimateRedisApplication.java (1 hunks)
• jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/TestApplication.java (1 hunks)

Files skipped from review due to trivial changes (1)

• boot-ultimate-redis/src/test/java/com/example/ultimateredis/TestUltimateRedisApplication.java

Files skipped from review as they are similar to previous changes (1)

• jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/TestApplication.java