ag/gymflow
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases 1 Wiki Activity

Playwright re-established. 54 test cases generated.

Browse Source
This commit is contained in:
AG
2025-11-30 14:35:47 +02:00
parent 683f80dfea
commit eef65251d7
63 changed files with 5752 additions and 157 deletions
Download Patch File Download Diff File Expand all files Collapse all files

53
.gemini/commands/playwright.generator.toml
View File

@@ -1,41 +1,8 @@
description = "Use this agent when you need to create automated browser tests using Playwright"
description = "Create automated browser tests using Playwright."
prompt = """
---
name: playwright-test-generator
description: 'Use this agent when you need to create automated browser tests
using Playwright Examples: <example>Context: User wants to generate a test for
the test plan item. <test-suite><!-- Verbatim name of the test spec group w/o
ordinal like "Multiplication tests" --></test-suite> <test-name><!-- Name of
the test case without the ordinal like "should add two numbers"
--></test-name> <test-file><!-- Name of the file to save the test into, like
tests/multiplication/should-add-two-numbers.spec.ts --></test-file>
<seed-file><!-- Seed file path from test plan --></seed-file> <body><!-- Test
case content including steps and expectations --></body></example>'
---
tools:
- search
- playwright-test/browser_click
- playwright-test/browser_drag
- playwright-test/browser_evaluate
- playwright-test/browser_file_upload
- playwright-test/browser_handle_dialog
- playwright-test/browser_hover
- playwright-test/browser_navigate
- playwright-test/browser_press_key
- playwright-test/browser_select_option
- playwright-test/browser_snapshot
- playwright-test/browser_type
- playwright-test/browser_verify_element_visible
- playwright-test/browser_verify_list_visible
- playwright-test/browser_verify_text_visible
- playwright-test/browser_verify_value
- playwright-test/browser_wait_for
- playwright-test/generator_read_log
- playwright-test/generator_setup_page
- playwright-test/generator_write_test
description: Create automated browser tests using Playwright.
---
## User Input
@@ -46,18 +13,25 @@ $ARGUMENTS
You **MUST** consider the user input before proceeding (if not empty).
## Helpful tools
- Any 'playwright-test' MCP tool
## Outline
The text the user typed after `/playwright.generator` in the triggering message points to test plan. Assume you always have it available in this conversation even if `{{args}}` appears literally below. Do not ask the user to repeat it unless triggering message contains `/playwright.generator` command and no other text.
You are a Playwright Test Generator, an expert in browser automation and end-to-end testing.
Your specialty is creating robust, reliable Playwright tests that accurately simulate user interactions and validate
application behavior.
# For each test you generate
- Obtain the test plan with all the steps and verification specification
- Run the `playwright-test/generator_setup_page` tool to set up page for the scenario
- Run the `generator_setup_page` tool to set up page for the scenario
- For each step and verification in the scenario, do the following:
- Use Playwright tool to manually execute it in real-time.
- Use the step description as the intent for each Playwright tool call.
- Retrieve generator log via `playwright-test/generator_read_log`
- Immediately after reading the test log, invoke `playwright-test/generator_write_test` with the generated source code
- Retrieve generator log via `generator_read_log`
- Immediately after reading the test log, invoke `generator_write_test` with the generated source code
- File should contain single test
- File name must be fs-friendly scenario name
- Test must be placed in a describe matching the top-level test plan item
@@ -98,7 +72,4 @@ application behavior.
```
</example-generation>
## Context
{{args}}
"""