|
| 1 | +# Gemini CLI Prompt for ChromeDriver Bug Triage |
| 2 | + |
| 3 | +Your task is to triage a ChromeDriver bug report using this pre-configured bug reproduction template. The goal is to confirm the bug's presence by writing a test that is expected to fail. |
| 4 | + |
| 5 | +**Bug to Triage:** `crbug.com/<BUG_ID>` (Please provide the actual bug ID in your prompt) |
| 6 | + |
| 7 | +**Workflow:** |
| 8 | + |
| 9 | +1. **Analyze the Bug Report:** |
| 10 | + * Thoroughly read the bug description, summary, and all comments on `crbug.com/<BUG_ID>` to understand the issue. |
| 11 | + * Identify the operating system, programming language, and any other technologies required to reproduce the bug. |
| 12 | + |
| 13 | +2. **Select and Configure the Environment:** |
| 14 | + * Choose the most relevant template from this repository that matches the bug's environment (e.g., `macos-selenium-mochajs`, `ubuntu-selenium-java`, etc.). |
| 15 | + * Navigate into the chosen template directory. |
| 16 | + * If necessary, modify the corresponding GitHub Actions workflow file in `.github/workflows/` to set up the precise environment. This may include: |
| 17 | + * Installing specific browser versions. |
| 18 | + * Setting up custom dependencies (e.g., via `npm`, `mvn`, `gem`, or `pip`). |
| 19 | + * Configuring environment variables. |
| 20 | + |
| 21 | +3. **Write a Failing Test:** |
| 22 | + * Modify the test file (e.g., `test.js`, `RegressionTest.java`) to add a new test case that reproduces the bug. |
| 23 | + * **Crucially, the test must be written to fail if the bug exists.** The assertion in the test should check for the correct behavior, which will fail if the bug is present. |
| 24 | + * The new test code must be thoroughly commented, explaining the reproduction steps, what the test is doing, and why it is expected to fail. Justify the `expected` value in the assertion using details from the bug description and, if relevant, the WebDriver specification. |
| 25 | + |
| 26 | +4. **Verify the Reproduction:** |
| 27 | + * Run the test suite to confirm that the new test fails as expected. A failing test successfully reproduces the bug. |
0 commit comments