Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: simulator tests #515

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

gitsofaryan
Copy link
Contributor

@gitsofaryan gitsofaryan commented Mar 9, 2025

Fixes #508

Describe the changes you have made in this PR -

test

Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Summary by CodeRabbit

  • Chores
    • Introduced an automated workflow that runs simulator tests on pushes and pull requests to the main branch.
  • Tests
    • Refined the testing configuration to clearly specify which tests to run and which files and directories to exclude, ensuring more reliable and streamlined testing.

Copy link
Contributor

coderabbitai bot commented Mar 9, 2025

Walkthrough

This pull request introduces two primary changes. First, a new GitHub Actions workflow file named simulator-tests.yml is added to run simulator tests on pushes and pull requests to the main branch. Second, the Vite configuration (vite.config.ts) is updated with specific test configurations by adding properties to include and exclude designated test files and directories.

Changes

File(s) Change Summary
.github/workflows/simulator-tests.yml Added a GitHub Actions workflow that triggers on pushes/PRs to main, checks out the code, sets up Node.js v20, installs dependencies, and runs tests.
vite.config.ts Updated test configurations by adding include (to target ./src/simulator/spec/**/*.spec.js) and exclude (to omit node_modules, v0, v1, and dist).

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub Actions
    participant Repo as Repository
    participant Node as Node.js Setup
    participant Test as Test Runner

    Dev->>GH: Push/PR to main
    GH->>Repo: Checkout code (actions/checkout@v4)
    GH->>Node: Setup Node.js v20 (actions/setup-node@v4)
    Node-->>GH: Environment ready
    GH->>GH: Install dependencies (npm install)
    GH->>Test: Execute simulator tests (npm run test)
Loading

Poem

I'm a happy rabbit on a coding spree,
Hopping through workflows with glee.
New tests bloom like carrots so sweet,
With Node and Vite making my day complete.
Cheers to changes that make bugs retreat!
🥕🐇

✨ Finishing Touches
  • 📝 Generate Docstrings

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

Copy link

netlify bot commented Mar 9, 2025

Deploy Preview for circuitverse ready!

Name Link
🔨 Latest commit 5662471
🔍 Latest deploy log https://app.netlify.com/sites/circuitverse/deploys/67cd1f746c11e5000884dde2
😎 Deploy Preview https://deploy-preview-515--circuitverse.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 45
Accessibility: 72
Best Practices: 92
SEO: 80
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

@gitsofaryan
Copy link
Contributor Author

gitsofaryan commented Mar 9, 2025

@vedant-jain03 @niladrix719 PTAL!

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 (2)
.github/workflows/simulator-tests.yml (2)

26-31: Missing newline at end of file and potential performance improvements.

The file is missing a newline at the end, which is flagged by the static analysis tool. Also consider adding npm dependency caching to improve workflow performance.

      - name: Run Simulator Tests
        run: |
          npm run test
+

For improved performance, consider adding dependency caching:

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 20
+         cache: 'npm'
+
+      - name: Cache dependencies
+        uses: actions/cache@v3
+        with:
+          path: ~/.npm
+          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-node-
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 31-31: no new line character at the end of file

(new-line-at-end-of-file)


29-31: Consider adding test result reporting.

For better visibility into test results, consider implementing test report generation and uploading as workflow artifacts.

      - name: Run Simulator Tests
        run: |
          npm run test
+
+      - name: Upload Test Results
+        if: always()
+        uses: actions/upload-artifact@v3
+        with:
+          name: test-results
+          path: test-results/
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 31-31: no new line character at the end of file

(new-line-at-end-of-file)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2a9f309 and 5662471.

📒 Files selected for processing (2)
  • .github/workflows/simulator-tests.yml (1 hunks)
  • vite.config.ts (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/simulator-tests.yml

[error] 31-31: no new line character at the end of file

(new-line-at-end-of-file)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (2)
.github/workflows/simulator-tests.yml (1)

1-31: Well-structured GitHub Actions workflow for simulator tests.

The workflow is properly set up to run simulator tests on pushes and PRs to the main branch, with appropriate steps for checkout, Node.js setup, and test execution.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 31-31: no new line character at the end of file

(new-line-at-end-of-file)

vite.config.ts (1)

41-47:

✅ Verification successful

Good test configuration for simulator tests.

The include and exclude patterns are appropriately configured to target simulator test files while excluding irrelevant directories. This aligns well with the newly added GitHub Actions workflow.

To verify that the test configuration correctly identifies all test files, you can run:


🏁 Script executed:

#!/bin/bash
# Check if test files exist in the specified path
count=$(find ./src/simulator/spec -name "*.spec.js" | wc -l)
echo "Found $count test files matching the pattern"
find ./src/simulator/spec -name "*.spec.js" | head -n 5

Length of output: 429


Simulator Test Configuration Verified

The test configuration in vite.config.ts (lines 41–47) has been verified and works as expected. The verification script found 9 test files matching the pattern (e.g., bitConvertor.spec.js, combinationalAnalysis.spec.js, etc.), confirming that the include/exclude settings correctly target simulator tests while excluding irrelevant directories. This aligns perfectly with the newly added GitHub Actions workflow.

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.

Create Workflow for simulator tests using yml file
1 participant