🧪 [testing improvement] Add unit tests for isSupportedConnectionDsn

[seonghobae]

🎯 What:
The isSupportedConnectionDsn utility function in frontend/src/App.tsx lacked unit tests, creating a gap in testing for connection DSN validation. This PR exports the function and adds comprehensive unit tests to ensure its logic is robust.

📊 Coverage:
The added test suite in App.coverage.test.tsx covers the following scenarios:

• Supported protocols: Verifies postgres://, postgresql://, and snowflake:// return true.
• Unsupported protocols: Verifies mysql:// and http:// return false.
• Malformed/invalid inputs: Verifies strings that throw an error in the URL constructor (e.g., not-a-url, empty strings) are properly caught and return false.
• Missing hostname: Verifies valid URLs missing a hostname (e.g., postgres:///) return false.

✨ Result:
Test coverage for DSN validation is now fully implemented. The test suite ran successfully (202 tests passed across the frontend module), ensuring correct parsing and error handling for connection strings without regressions.

---

PR created automatically by Jules for task 13091436170224548167 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1f24c82-315e-4301-a001-14b74f1418de

📥 Commits

Reviewing files that changed from the base of the PR and between 72afe6d and bf82654.

📒 Files selected for processing (2)

• frontend/src/App.coverage.test.tsx
• frontend/src/App.tsx

---

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