[WIP] Increase unit test coverage for db module

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>✨ [Feature] Increase unit test coverage</issue_title>
<issue_description>The target repository is goravel/framework</issue_description>

<agent_instructions>Create a PR for Task 1.1 that is in goravel/goravel#43 (comment)</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@hwbrzzl Thanks, this's continuous work, feel free to do this, you can run the `go test -cover` command to check the test coverage. @hwbrzzl Thanks for the job. Yes, there is [a tests folder](https://github.com/goravel/framework/tree/master/tests) to test the db module, all db drivers are tested there. The database folder cannot be tested with a real db driver actually, can only add test cases with mock. @hwbrzzl ## 📊 Coverage Analysis & Implementation Plan

Current Status: 69.40% overall coverage (13,578 of 19,563 lines covered)
Target: 85-90% overall coverage
Source: Latest commit on master branch (29a6104)

This plan is organized by priority based on current coverage levels and potential impact. I'll implement these incrementally, starting with the lowest coverage modules for maximum impact.</comment_new>
<comment_new>@hwbrzzl

🔴 Priority 1: Low Coverage Modules (<50%)

Task 1.1: Route Module (22.69% → 70%)

• Current: 81/357 lines covered, 274 missed
• Focus areas:
  • Route registration and matching logic
  • Middleware handling
  • Parameter binding and validation
  • Route grouping functionality
• Estimated impact: +6% overall coverage

Task 1.2: Crypt Module (34.02% → 70%)

• Current: 33/97 lines covered, 53 missed
• Focus areas:
  • Encryption/decryption methods
  • Key generation and rotation
  • Error handling for invalid inputs
• Estimated impact: +0.3% overall coverage

Task 1.3: Mail Module (42.26% → 70%)

• Current: 393/930 lines covered, 499 missed
• Focus areas:
  • Email sending with different drivers
  • Attachment handling
  • Template rendering
  • Queue integration
• Estimated impact: +2.5% overall coverage

Task 1.4: Filesystem Module (43.65% → 70%)

• Current: 141/323 lines covered, 156 missed
• Focus areas:
  • File operations (read, write, delete)
  • Directory management
  • Different storage drivers (local, S3, etc.)
  • Error handling for permissions
• Estimated impact: +0.8% overall coverage

Task 1.5: Hash Module (43.88% → 70%)

• Current: 61/139 lines covered, 73 missed
• Focus areas:
  • Password hashing algorithms
  • Hash verification
  • Configuration options
• Estimated impact: +0.5% overall coverage

Priority 1 Total Expected Gain: ~10% overall coverage</comment_new>
<comment_new>@hwbrzzl

🟡 Priority 2: Medium Coverage Modules (50-70%)

Task 2.1: Console Module (54.83% → 75%)

• Current: 948/1729 lines covered, 743 missed
• Focus areas: Command registration, execution, input/output handling, custom commands
• Estimated impact: +3.5% overall coverage

Task 2.2: Event Module (53.52% → 75%)

• Current: 114/213 lines covered, 93 missed
• Focus areas: Event dispatching, listener registration, queued listeners
• Estimated impact: +0.5% overall coverage

Task 2.3: Cache Module (56.05% → 75%)

• Current: 176/314 lines covered, 126 missed
• Focus areas: Different cache drivers, cache tagging, TTL handling
• Estimated impact: +0.6% overall coverage

Task 2.4: Grpc Module (56.73% → 75%)

• Current: 177/312 lines covered, 127 missed
• Focus areas: gRPC server setup, service registration, request/response handling
• Estimated impact: +0.6% overall coverage

Task 2.5: Queue Module (63.25% → 80%)

• Current: 573/906 lines covered, 304 missed
• Focus areas: Job dispatching, failed job handling, different queue drivers
• Estimated impact: +1.5% overall coverage

Task 2.6: Auth Module (67.06% → 80%)

• Current: 338/504 lines covered, 149 missed
• Focus areas: Authentication guards, user providers, token management
• Estimated impact: +0.8% overall coverage

Task 2.7: Config Module (68.00% → 85%)

• Current: 51/75 lines covered, 21 missed
• Focus areas: Configuration loading, environment-specific configs, caching
• Estimated impact: +0.2% overall coverage

Task 2.8: Foundation Module (68.91% → 80%)

• Current: 1474/2139 lines covered, 601 missed
• Focus areas: Application bootstrapping, service provider registration, container bindings
• Estimated impact: +2.5% overall coverage

Task 2.9: Session Module (69.59% → 80%)

• Current: 286/411 lines covered, 110 missed
• Focus areas: Session drivers, session lifecycle, flash data h...

• Fixes ✨ [Feature] Increase unit test coverage goravel#43

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.