Fix complex complex test failures

[hackerwins]

What this PR does / why we need it:

Fix complex complex test failures

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Additional documentation:

Checklist:

• Added relevant tests or not required
• Addressed and resolved all CodeRabbit review comments
• Didn't break anything

Summary by CodeRabbit

• Chores
  • Streamlined internal configurations to improve consistency and build process reliability.
• Tests
  • Expanded testing scenarios and refined backend configuration parameters to bolster comprehensive validation.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change updates the CI workflow YAML file, adds a new Makefile target for running complex tests, and modifies test initialization in a Go test file. The CI workflow configuration now formats branch and path specifications consistently and expands the path filters for complex tests, including a dedicated step for setting up Go. The Makefile gains a new target, test-complex, which handles complex test execution with cache cleaning. The test file update adjusts configuration parameters for the backend initialization, replacing webhook cache settings with wait interval and timeout parameters.

Changes

File(s)	Summary
.github/workflows/ci.yml	Reformatted branch definitions and path filters (switching from single to double quotes); expanded the filter in the ci-target-check job to include test/complex/**; and updated the complex-test job to include a new Go setup step with uniform formatting.
Makefile	Introduced a new target test-complex to run complex tests, which cleans the test cache and executes tests with specific tags, without impacting existing targets.
test/complex/main_test.go	Modified configuration for backend.New within TestMain. Added parameters: AuthWebhookMaxWaitInterval, AuthWebhookMinWaitInterval, and AuthWebhookRequestTimeout; removed AuthWebhookCacheTTL and AuthWebhookCacheSize; reordered parameters for clarity.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant GitHub as GitHub Actions
    participant CI as CI Workflow
    participant TestJob as Complex Test Job
    participant GoEnv as Go Environment

    Dev->>GitHub: Push commit with changes
    GitHub->>CI: Trigger CI workflow
    CI->>CI: Execute ci-target-check (filtering changes including test/complex/**)
    CI->>TestJob: Run complex-test job if applicable
    TestJob->>GoEnv: Setup Go environment (new step)
    TestJob->>TestJob: Execute complex tests via Makefile target
    TestJob-->>CI: Return test results

Loading

Possibly related PRs

• Reduce CI test time by optimizing task execution #988: Similar modifications were conducted in the CI workflow configuration focused on job renaming and path adjustments, which align closely with the changes in this PR.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ccf25f0 and 28e9888.

📒 Files selected for processing (3)

• .github/workflows/ci.yml (5 hunks)
• Makefile (1 hunks)
• test/complex/main_test.go (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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>, please review it.
  • 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 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 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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. (Beta)
• @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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 38.54%. Comparing base (ccf25f0) to head (28e9888).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1148   +/-   ##
=======================================
  Coverage   38.54%   38.54%           
=======================================
  Files         165      165           
  Lines       25247    25247           
=======================================
  Hits         9731     9731           
  Misses      14698    14698           
  Partials      818      818           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.