Skip to content

test: simplify test-project's docker compose command and add Window's version#1452

Merged
asyncapi-bot merged 4 commits into
asyncapi:masterfrom
nightknighto:docker-test-project
Mar 31, 2025
Merged

test: simplify test-project's docker compose command and add Window's version#1452
asyncapi-bot merged 4 commits into
asyncapi:masterfrom
nightknighto:docker-test-project

Conversation

@nightknighto

@nightknighto nightknighto commented Mar 28, 2025

Copy link
Copy Markdown
Contributor

Description

Simplifies the docker compose command documented in the test-project README inside generator test.

  • Replaces the first part of the command with force-recreate flag
  • Removes unneeded remove-orphans flag
  • Remove the above flag from the github workflow as well
  • Adds Window's version of the command

Related issue(s)

Part of #1425

Summary by CodeRabbit

  • Chores

    • Streamlined the automated testing process by simplifying container management during test runs.
  • Documentation

    • Updated and clarified test instructions with separate, platform-specific commands for Linux/MacOS and Windows to enhance usability.

@coderabbitai

coderabbitai Bot commented Mar 28, 2025

Copy link
Copy Markdown

Walkthrough

The pull request updates the GitHub Actions test workflow and the associated documentation. In the workflow file, the Docker Compose command has been modified to remove the --remove-orphans flag, simplifying the test execution. The README in the test project now provides distinct command instructions for Linux/MacOS and Windows environments.

Changes

File Change Summary
.github/workflows/pr-testing-with-test-project.yml Modified the Docker Compose command by removing the --remove-orphans flag, retaining --abort-on-container-exit and --force-recreate.
apps/.../README.md Revised test instructions by replacing a single Docker Compose command with separate commands for Linux/MacOS and Windows.

Possibly related issues

Possibly related PRs

Suggested labels

ready-to-merge

Suggested reviewers

  • Florence-Njeri
  • asyncapi-bot-eve
  • derberg
  • jonaslagoni

Poem

I hopped through lines of code with cheer,
Removing flags to keep our tests clear.
Linux or Windows, each instruction sings,
Docker commands dancing with simpler strings.
A rabbit’s delight as clarity springs – let the changes cheer!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 plan to trigger planning for file edits and PR creation.
  • @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.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

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 (4)
.github/workflows/pr-testing-with-test-project.yml (2)

40-40: Actionable: Review Checkout Pinning
The checkout step on line 40 is explicitly pinned to a commit (f43a0e5ff2bd294095638e18286ca9a3d1956744). While this increases reproducibility, consider updating to a tagged release in the future for improved clarity and maintainability.


60-62: Clarify Docker Compose Command Changes
The updated "Run test" step (line 61) removes the --remove-orphans flag and now uses:

NODE_IMAGE_TAG=${{ matrix.node }} docker compose up --abort-on-container-exit --force-recreate

Please verify that the removal of --remove-orphans does not result in unintended orphan container behavior during test execution. Additionally, note that the command uses docker compose (without hyphen), which is the Docker Compose V2 syntax; ensure that this is intentional and consistent with your environment.

apps/generator/test/test-project/README.md (2)

6-6: Correct Operating System Branding
The command description for Linux/macOS on line 6 currently uses "Linux/MacOS". For accuracy and brand consistency, please change "MacOS" to "macOS".

Proposed diff:

-Linux/MacOS: `NODE_IMAGE_TAG=18 docker-compose up --abort-on-container-exit --force-recreate`.
+Linux/macOS: `NODE_IMAGE_TAG=18 docker-compose up --abort-on-container-exit --force-recreate`.
🧰 Tools
🪛 LanguageTool

[grammar] ~6-~6: The operating system from Apple is written “macOS”.
Context: ...e and run the following command: Linux/MacOS: `NODE_IMAGE_TAG=18 docker-compose up -...

(MAC_OS)


8-8: Enhance Windows Command Formatting
The Windows command on line 8 is given as:

set NODE_IMAGE_TAG=18&& docker-compose up --abort-on-container-exit --force-recreate

It is common practice to include a space before and after the && operator for better readability and to avoid potential issues. Consider updating it to:

set NODE_IMAGE_TAG=18 && docker-compose up --abort-on-container-exit --force-recreate

Proposed diff:

-set NODE_IMAGE_TAG=18&& docker-compose up --abort-on-container-exit --force-recreate
+set NODE_IMAGE_TAG=18 && docker-compose up --abort-on-container-exit --force-recreate
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 591741f and cc58976.

📒 Files selected for processing (2)
  • .github/workflows/pr-testing-with-test-project.yml (2 hunks)
  • apps/generator/test/test-project/README.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
apps/generator/test/test-project/README.md

[grammar] ~6-~6: The operating system from Apple is written “macOS”.
Context: ...e and run the following command: Linux/MacOS: `NODE_IMAGE_TAG=18 docker-compose up -...

(MAC_OS)

🔇 Additional comments (1)
apps/generator/test/test-project/README.md (1)

4-4: Improve Instruction Clarity
The introductory instruction on line 4 clearly instructs users to run tests via Docker Compose rather than npm test. This provides improved guidance, especially for environments that rely on containerized testing.

@nightknighto

Copy link
Copy Markdown
Contributor Author

In set NODE_IMAGE_TAG=18&& docker-compose up --abort-on-container-exit --force-recreate, the no space before the && is intentional. Otherwise, the set command on Windows will take the space as part of the value: 18 .

@derberg derberg changed the title docs: simplify test-project's docker compose command and add Window's version test: simplify test-project's docker compose command and add Window's version Mar 31, 2025
@changeset-bot

changeset-bot Bot commented Mar 31, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 60e1c0e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@sonarqubecloud

Copy link
Copy Markdown

@derberg

derberg commented Mar 31, 2025

Copy link
Copy Markdown
Member

/rtm

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants