✅ Add server repo tests

[NatoBoram]

Summary by CodeRabbit

• New Features

  • Introduced new environment variables for Bitbucket Server project configuration to enhance automated testing and deployment.
  • Added unit tests for project management and repository-related API functionalities, improving test coverage.

• Bug Fixes

  • Renamed exports to enhance clarity in client references without altering functionality.

• Tests

  • Expanded testing suite for repository management, including creation, retrieval, and deletion tests.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Walkthrough

The pull request introduces several changes primarily focused on enhancing the configuration and testing capabilities related to Bitbucket Server. Two new environment variables, BITBUCKET_SERVER_TEST_PROJECT_KEY and BITBUCKET_SERVER_TEST_PROJECT_NAME, are added to the .env file and the GitHub Actions workflow. Additionally, there are modifications in the naming of exported client instances in multiple test files for clarity. New test cases are also introduced for project and repository management functionalities, improving test coverage for the Bitbucket Server API.

Changes

Files	Change Summary
.env, .github/workflows/node.js.yaml	Added environment variables: BITBUCKET_SERVER_TEST_PROJECT_KEY, BITBUCKET_SERVER_TEST_PROJECT_NAME.
tests/cloud/client.ts, tests/server/client.ts	Renamed exported constant from cloud to client in both files.
tests/cloud/repositories.test.ts	Updated import statement from cloud to client for the GET request test case.
tests/env.ts	Added exports for NODE_ENV, BITBUCKET_SERVER_TEST_PROJECT_KEY, and BITBUCKET_SERVER_TEST_PROJECT_NAME.
tests/server/projects.test.ts	Introduced unit tests for project management API with test cases for retrieving project data.
tests/server/repositories.test.ts	Added structured tests for repository-related API endpoints, including creation, retrieval, and deletion of repositories.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CI/CD Pipeline
    participant Bitbucket Server

    User->>CI/CD Pipeline: Trigger Workflow
    CI/CD Pipeline->>Bitbucket Server: Access Project Configuration
    Bitbucket Server-->>CI/CD Pipeline: Return Project Data
    CI/CD Pipeline->>User: Workflow Complete

Loading

Possibly related PRs

• ✅ Add server repo tests #3: The main PR and this retrieved PR both introduce the same environment variables, BITBUCKET_SERVER_TEST_PROJECT_KEY and BITBUCKET_SERVER_TEST_PROJECT_NAME, in the .env configuration file, indicating a direct connection in their changes.

---

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