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

Development: Add different execution modes for local playwright setup #10064

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

SimonEntholzer
Copy link
Contributor

@SimonEntholzer SimonEntholzer commented Dec 22, 2024

Checklist

General

Motivation and Context

With the simplified playwright setup, the user should be able to run all to run all tests.

Description

Adds another script, to be able to run either all tests, or run Playwright in UI mode. Also extends the README explaining the two options.

Steps for Testing

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.







Review Progress

Code Review

  • Code Review 1
  • Code Review 2

Manual Tests

  • Test 1
  • Test 2

Summary by CodeRabbit

  • New Features

    • Introduced a new script to launch Playwright in UI mode (startPlaywrightUI.sh).
    • Enhanced README with detailed instructions for running tests, including distinctions between all tests and UI mode.
  • Bug Fixes

    • Updated the functionality of startPlaywright.sh to run all Playwright tests instead of launching the UI.
  • Documentation

    • Improved clarity and organization of the Playwright README file.

Copy link

coderabbitai bot commented Dec 22, 2024

Walkthrough

This pull request focuses on improving the Playwright testing setup and documentation. The changes include updating the README.md file with more detailed and clear instructions for running Playwright tests, modifying the startPlaywright.sh script to run tests instead of opening UI mode, and introducing a new startPlaywrightUI.sh script specifically for launching Playwright in UI mode. These modifications aim to provide more precise guidance for developers working with Playwright testing in the project.

Changes

File Change Summary
supporting_scripts/playwright/README.md - Restructured section titles for better readability
- Expanded instructions for running tests
- Added code block syntax for setup commands
- Clarified test execution details
supporting_scripts/playwright/startPlaywright.sh - Changed from UI mode launch to running all Playwright tests
- Modified echo message and command execution
supporting_scripts/playwright/startPlaywrightUI.sh - New script added
- Sets up error handling
- Determines Artemis directory path
- Installs Playwright dependencies
- Launches Playwright in UI mode

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Script as startPlaywrightUI.sh
    participant Npm as NPM
    participant Playwright as Playwright UI

    Dev->>Script: Execute script
    Script->>Npm: npm install
    Npm-->>Script: Dependencies installed
    Script->>Npm: npm run playwright:setup-local
    Npm-->>Script: Local setup complete
    Script->>Playwright: Open Playwright UI
    Playwright-->>Dev: Playwright UI launched
Loading

Possibly related PRs

Suggested Labels

tests, ready for review, documentation, small, docker

Suggested Reviewers

  • muradium
  • coolchock
  • BBesrour
  • az108

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. (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 or @coderabbitai title 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

@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: 1

🧹 Nitpick comments (1)
supporting_scripts/playwright/startPlaywright.sh (1)

15-16: Consider adding error handling for the test command.

While the script uses set -e for general error handling, consider adding specific error handling for the test command to provide better feedback on test failures.

 echo "Run all playwright tests"
-npm run playwright:test
+if ! npm run playwright:test; then
+    echo "Playwright tests failed. Check the test output above for details."
+    exit 1
+fi
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 73c6285 and 2f3c4fb.

📒 Files selected for processing (3)
  • supporting_scripts/playwright/README.md (1 hunks)
  • supporting_scripts/playwright/startPlaywright.sh (1 hunks)
  • supporting_scripts/playwright/startPlaywrightUI.sh (1 hunks)
🔇 Additional comments (2)
supporting_scripts/playwright/README.md (2)

19-23: LGTM! Improved code block formatting.

The addition of proper code block formatting for the setupUsers.sh command improves readability and follows Markdown best practices.


26-41: LGTM! Clear and well-structured documentation.

The documentation improvements effectively:

  • Separate and explain different execution modes
  • Provide clear distinctions between UI mode and headless testing
  • Include helpful details about features available in each mode

Comment on lines +1 to +16
#!/bin/sh

set -e

artemis_path="$(readlink -f "$(dirname $0)/../..")"

echo "Installing Playwright and dependencies"

cd "$artemis_path/src/test/playwright"

npm install

npm run playwright:setup-local || true

echo "Start Playwright in UI mode"
npm run playwright:open
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider reducing code duplication with a common setup script.

There's significant code duplication between startPlaywright.sh and startPlaywrightUI.sh. Consider extracting common setup logic into a shared script.

Create a new file setupPlaywright.sh:

#!/bin/sh

set -e

artemis_path="$(readlink -f "$(dirname $0)/../..")"
cd "$artemis_path/src/test/playwright"

# Check if playwright is already installed
if [ ! -d "node_modules" ]; then
    echo "Installing Playwright and dependencies"
    npm install
    npm run playwright:setup-local || true
fi

Then modify both scripts to source this common setup:

 #!/bin/sh
 
 set -e
 
-artemis_path="$(readlink -f "$(dirname $0)/../..")"
-
-echo "Installing Playwright and dependencies"
-
-cd "$artemis_path/src/test/playwright"
-
-npm install
-
-npm run playwright:setup-local || true
+source "$(dirname $0)/setupPlaywright.sh"
 
 echo "Start Playwright in UI mode"
 npm run playwright:open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready For Review
Development

Successfully merging this pull request may close these issues.

1 participant