mirror of
https://github.com/zebrajr/react.git
synced 2025-12-06 12:20:20 +01:00
<!-- Thanks for submitting a pull request! We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory. Before submitting a pull request, please make sure the following is done: 1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`. 2. Run `yarn` in the repository root. 3. If you've fixed a bug or added code that should be tested, add tests! 4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development. 5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`. 6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect". 7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`). 8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files. 9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`). 10. If you haven't already, complete the CLA. Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html --> ## Summary Updated the UI of the React compiler playground. The config, Input, and Output panels will now span the viewport width when "Show Internals" is not toggled on. When "Show Internals" is toggled on, the old vertical accordion tabs are still used. Going to add support for the "Applied Configs" tabs underneath the "Config Overrides" tab next. <!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? --> ## How did you test this change? https://github.com/user-attachments/assets/b8eab028-f58c-4cb9-a8b2-0f098f2cc262 <!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. How exactly did you verify that your PR solves the issue you wanted to solve? If you leave this empty, your PR will very likely be closed. -->
94 lines
2.8 KiB
JavaScript
94 lines
2.8 KiB
JavaScript
/**
|
|
* Copyright (c) Meta Platforms, Inc. and affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*/
|
|
|
|
import {defineConfig, devices} from '@playwright/test';
|
|
import path from 'path';
|
|
|
|
// Use process.env.PORT by default and fallback to port 3000
|
|
const PORT = process.env.PORT || 3000;
|
|
|
|
// Set webServer.url and use.baseURL with the location of the WebServer respecting the correct set port
|
|
const baseURL = `http://localhost:${PORT}`;
|
|
|
|
// Reference: https://playwright.dev/docs/test-configuration
|
|
export default defineConfig({
|
|
// Timeout per test
|
|
timeout: 30 * 1000,
|
|
// Run all tests in parallel.
|
|
fullyParallel: true,
|
|
// Test directory
|
|
testDir: path.join(__dirname, '__tests__/e2e'),
|
|
// If a test fails, retry it additional 2 times
|
|
retries: 3,
|
|
// Artifacts folder where screenshots, videos, and traces are stored.
|
|
outputDir: 'test-results/',
|
|
// Note: we only use text snapshots, so its safe to omit the host environment name
|
|
snapshotPathTemplate: '{testDir}/__snapshots__/{testFilePath}/{arg}{ext}',
|
|
|
|
// Run your local dev server before starting the tests:
|
|
// https://playwright.dev/docs/test-advanced#launching-a-development-web-server-during-the-tests
|
|
webServer: {
|
|
command: 'yarn dev',
|
|
url: baseURL,
|
|
timeout: 300 * 1000,
|
|
reuseExistingServer: !process.env.CI,
|
|
},
|
|
|
|
// 'github' for GitHub Actions CI to generate annotations, plus a concise 'dot'
|
|
// default 'list' when running locally
|
|
reporter: process.env.CI ? 'github' : 'list',
|
|
|
|
use: {
|
|
// Use baseURL so to make navigations relative.
|
|
// More information: https://playwright.dev/docs/api/class-testoptions#test-options-base-url
|
|
baseURL,
|
|
|
|
// Retry a test if its failing with enabled tracing. This allows you to analyze the DOM, console logs, network traffic etc.
|
|
// More information: https://playwright.dev/docs/trace-viewer
|
|
trace: 'retry-with-trace',
|
|
|
|
// All available context options: https://playwright.dev/docs/api/class-browser#browser-new-context
|
|
// contextOptions: {
|
|
// ignoreHTTPSErrors: true,
|
|
// },
|
|
viewport: {width: 1920, height: 1080},
|
|
},
|
|
|
|
projects: [
|
|
{
|
|
name: 'chromium',
|
|
use: {
|
|
...devices['Desktop Chrome'],
|
|
viewport: {width: 1920, height: 1080},
|
|
},
|
|
},
|
|
// {
|
|
// name: 'Desktop Firefox',
|
|
// use: {
|
|
// ...devices['Desktop Firefox'],
|
|
// },
|
|
// },
|
|
// {
|
|
// name: 'Desktop Safari',
|
|
// use: {
|
|
// ...devices['Desktop Safari'],
|
|
// },
|
|
// },
|
|
// Test against mobile viewports.
|
|
// {
|
|
// name: "Mobile Chrome",
|
|
// use: {
|
|
// ...devices["Pixel 5"],
|
|
// },
|
|
// },
|
|
// {
|
|
// name: "Mobile Safari",
|
|
// use: devices["iPhone 12"],
|
|
// },
|
|
],
|
|
});
|