test: replace log.New() with testlog.Logger in psp_executor tests

[VolodymyrBg]

Description

This PR replaces the standard logger (log.New()) with testlog.Logger in the op-defender/psp_executor/api_test.go test file. This change improves test output handling by:

• Only showing logs when tests fail or when running with -v flag
• Including test context in log output
• Properly handling log levels

The change addresses multiple TODO comments in the codebase regarding logger replacement in test files.

Tests

The changes were made directly to test files, specifically:

• Updated logger initialization in TestHTTPServerHasCorrectRoute
• Updated logger initialization in TestDefenderInitialization
• Updated logger initialization in TestHandlePostMockFetch
• Updated logger initialization in TestGetNonceSafe
• Updated logger initialization in TestCheckPauseStatus

All existing tests continue to pass with the new logger implementation.

Additional context

This change is part of a larger effort to standardize test logging across the codebase using testlog. The testlog package is specifically designed for test environments and provides better control over log output during test execution.

Metadata

• Fixes TODO comments regarding logger replacement in test files
• Improves test output clarity and debugging experience

[coderabbitai]

Walkthrough

This pull request updates the logger initialization in the test functions within the file op-defender/psp_executor/api_test.go. The original logger created with log.New() is replaced with testlog.Logger(t, log.LvlInfo), ensuring the tests now utilize the new logging framework. Additionally, outdated TODO comments regarding logger replacement have been removed, while the actual test logic remains unchanged.

Changes

File	Change Summary
op-defender/.../api_test.go	Replaced logger initialization in multiple test functions from log.New() to testlog.Logger(t, log.LvlInfo); removed related TODO comments.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69cecce and a5dc74d.

📒 Files selected for processing (1)

• op-defender/psp_executor/api_test.go (6 hunks)

🔇 Additional comments (2)

op-defender/psp_executor/api_test.go (2)

20-20: LGTM!

The import of the testlog package is correctly added to support the new logging framework.

---

62-62: LGTM! Consistent logger initialization across test functions.

The logger initialization has been standardized across all test functions using testlog.Logger(t, log.LvlInfo). This change aligns with the PR objectives to improve test output visibility and control.

Benefits of this change:

• Logs are only displayed when tests fail or when running with -v flag
• Test context is included in log output
• Log levels are managed more effectively

Also applies to: 120-120, 145-145, 668-668, 853-853

✨ 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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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.

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.