Skip to content

CI: Enabled server unit tests on TBD#39539

Merged
yatinappsmith merged 1 commit intoreleasefrom
ci/enable-server-tests
Mar 4, 2025
Merged

CI: Enabled server unit tests on TBD#39539
yatinappsmith merged 1 commit intoreleasefrom
ci/enable-server-tests

Conversation

@yatinappsmith
Copy link
Contributor

@yatinappsmith yatinappsmith commented Mar 4, 2025

Description

Enabled server unit tests on TBD

Fixes #Issue Number

Automation

/ok-to-test tags=""

🔍 Cypress test results

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Tests

    • Integrated server-side tests into our build process to further validate critical functionalities and ensure a smoother, more reliable experience.
  • Chores

    • Updated the build and deployment workflows to enforce thorough pre-release validations, leading to more stable and robust releases for our users.

@yatinappsmith yatinappsmith requested a review from sharat87 as a code owner March 4, 2025 05:14
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 4, 2025

Walkthrough

The pull request introduces a fully defined server-unit-tests job in the CI workflow, which was previously commented out. The new job now depends on the successful execution of the build-docker-image job. Additionally, both the ci-test-result and package-master jobs have been updated to include the server-unit-tests job as a dependency, and their conditional logic has been expanded to consider its outcome.

Changes

File Change Summary
.github/workflows/test-build-docker-image.yml Added a fully defined server-unit-tests job with dependencies on build-docker-image; updated ci-test-result and package-master jobs to depend on server-unit-tests and expanded conditional checks.

Sequence Diagram(s)

sequenceDiagram
    participant BD as Build Docker Image
    participant SU as Server Unit Tests
    participant CTR as CI Test Result
    participant PM as Package Master

    BD->>SU: Complete build triggers unit tests
    SU->>CTR: Send test results for CI evaluation
    SU->>PM: Notify packaging process
Loading

Possibly related PRs

Suggested labels

CI, ok-to-test

Suggested reviewers

  • sharat87
  • mohanarpit
  • abhvsn
  • trishaanand

Poem

In our CI, a new step shines bright,
Server tests now join the flight.
Jobs aligned with clear intent,
Dependencies and checks are well-spent.
Code in flow, precise and tight –
A refined pipeline, a coder's delight!
🚀 Cheers to progress in every byte!


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

Copy link
Collaborator

@btsgh btsgh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Server unit tests are re-enabled.

@yatinappsmith yatinappsmith merged commit 2a5a654 into release Mar 4, 2025
15 of 17 checks passed
@yatinappsmith yatinappsmith deleted the ci/enable-server-tests branch March 4, 2025 05:16
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/test-build-docker-image.yml (1)

125-134: Ensure Consistent Input Types for Server Unit Tests Job

The new server-unit-tests job is well integrated into the workflow by depending on build-docker-image and conditionally running based on branch and event type. However, static analysis indicates that the inputs skip-tests and is-pg-build are expected as strings (per the reusable workflow definition in server-build.yml), but boolean values are being provided. To avoid any type mismatches at runtime, please update them so that their values are explicitly quoted. For example:

-      skip-tests: false
-      is-pg-build: ${{ github.ref == 'refs/heads/pg' }}
+      skip-tests: "false"
+      is-pg-build: "${{ github.ref == 'refs/heads/pg' }}"
🧰 Tools
🪛 actionlint (1.7.4)

133-133: input "skip-tests" is typed as string by reusable workflow "./.github/workflows/server-build.yml". bool value cannot be assigned

(expression)


134-134: input "is-pg-build" is typed as string by reusable workflow "./.github/workflows/server-build.yml". bool value cannot be assigned

(expression)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4f596df and dfb81a0.

📒 Files selected for processing (1)
  • .github/workflows/test-build-docker-image.yml (5 hunks)
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/test-build-docker-image.yml

133-133: input "skip-tests" is typed as string by reusable workflow "./.github/workflows/server-build.yml". bool value cannot be assigned

(expression)


134-134: input "is-pg-build" is typed as string by reusable workflow "./.github/workflows/server-build.yml". bool value cannot be assigned

(expression)

🔇 Additional comments (2)
.github/workflows/test-build-docker-image.yml (2)

282-293: Enhance Test Outcome Reporting in UI Matrix Step

The conditional logic in the "Return status for ui-matrix" step now factors in the outcome of the server unit tests. This ensures that if the server unit tests are skipped or fail, the overall status properly reflects that, which is an improvement in CI feedback. Please verify that the intended behavior of failing on skipped or failed server tests aligns with the overall test strategy.


397-398: Update Package-Master Job Dependencies

The package-master job now depends on server-unit-tests in addition to ci-test and client-unit-tests. This update ensures that the image packaging only proceeds after all relevant tests pass, meeting the PR objective to incorporate server unit tests into the CI pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants