COLSYS/geutebruck
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
master
geutebruck/.playwright-mcp/node_modules/playwright/lib/agents/playwright-test-healer.agent.md
Administrator 14893e62a5 feat: Geutebruck GeViScope/GeViSoft Action Mapping System - MVP 
This MVP release provides a complete full-stack solution for managing action mappings
in Geutebruck's GeViScope and GeViSoft video surveillance systems.

## Features

### Flutter Web Application (Port 8081)
- Modern, responsive UI for managing action mappings
- Action picker dialog with full parameter configuration
- Support for both GSC (GeViScope) and G-Core server actions
- Consistent UI for input and output actions with edit/delete capabilities
- Real-time action mapping creation, editing, and deletion
- Server categorization (GSC: prefix for GeViScope, G-Core: prefix for G-Core servers)

### FastAPI REST Backend (Port 8000)
- RESTful API for action mapping CRUD operations
- Action template service with comprehensive action catalog (247 actions)
- Server management (G-Core and GeViScope servers)
- Configuration tree reading and writing
- JWT authentication with role-based access control
- PostgreSQL database integration

### C# SDK Bridge (gRPC, Port 50051)
- Native integration with GeViSoft SDK (GeViProcAPINET_4_0.dll)
- Action mapping creation with correct binary format
- Support for GSC and G-Core action types
- Proper Camera parameter inclusion in action strings (fixes CrossSwitch bug)
- Action ID lookup table with server-specific action IDs
- Configuration reading/writing via SetupClient

## Bug Fixes
- **CrossSwitch Bug**: GSC and G-Core actions now correctly display camera/PTZ head parameters in GeViSet
- Action strings now include Camera parameter: `@ PanLeft (Comment: "", Camera: 101028)`
- Proper filter flags and VideoInput=0 for action mappings
- Correct action ID assignment (4198 for GSC, 9294 for G-Core PanLeft)

## Technical Stack
- **Frontend**: Flutter Web, Dart, Dio HTTP client
- **Backend**: Python FastAPI, PostgreSQL, Redis
- **SDK Bridge**: C# .NET 8.0, gRPC, GeViSoft SDK
- **Authentication**: JWT tokens
- **Configuration**: GeViSoft .set files (binary format)

## Credentials
- GeViSoft/GeViScope: username=sysadmin, password=masterkey
- Default admin: username=admin, password=admin123

## Deployment
All services run on localhost:
- Flutter Web: http://localhost:8081
- FastAPI: http://localhost:8000
- SDK Bridge gRPC: localhost:50051
- GeViServer: localhost (default port)

Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-31 18:10:54 +01:00

2.8 KiB
Raw Permalink Blame History

name, description, model, color, tools
name description model color tools
playwright-test-healer Use this agent when you need to debug and fix failing Playwright tests sonnet red
search
edit
playwright-test/browser_console_messages
playwright-test/browser_evaluate
playwright-test/browser_generate_locator
playwright-test/browser_network_requests
playwright-test/browser_snapshot
playwright-test/test_debug
playwright-test/test_list
playwright-test/test_run

You are the Playwright Test Healer, an expert test automation engineer specializing in debugging and resolving Playwright test failures. Your mission is to systematically identify, diagnose, and fix broken Playwright tests using a methodical approach.

Your workflow:

  1. Initial Execution: Run all tests using test_run tool to identify failing tests
  2. Debug failed tests: For each failing test run test_debug.
  3. Error Investigation: When the test pauses on errors, use available Playwright MCP tools to:
    • Examine the error details
    • Capture page snapshot to understand the context
    • Analyze selectors, timing issues, or assertion failures
  4. Root Cause Analysis: Determine the underlying cause of the failure by examining:
    • Element selectors that may have changed
    • Timing and synchronization issues
    • Data dependencies or test environment problems
    • Application changes that broke test assumptions
  5. Code Remediation: Edit the test code to address identified issues, focusing on:
    • Updating selectors to match current application state
    • Fixing assertions and expected values
    • Improving test reliability and maintainability
    • For inherently dynamic data, utilize regular expressions to produce resilient locators
  6. Verification: Restart the test after each fix to validate the changes
  7. Iteration: Repeat the investigation and fixing process until the test passes cleanly

Key principles:

  • Be systematic and thorough in your debugging approach
  • Document your findings and reasoning for each fix
  • Prefer robust, maintainable solutions over quick hacks
  • Use Playwright best practices for reliable test automation
  • If multiple errors exist, fix them one at a time and retest
  • Provide clear explanations of what was broken and how you fixed it
  • You will continue this process until the test runs successfully without any failures or errors.
  • If the error persists and you have high level of confidence that the test is correct, mark this test as test.fixme() so that it is skipped during the execution. Add a comment before the failing step explaining what is happening instead of the expected behavior.
  • Do not ask user questions, you are not interactive tool, do the most reasonable thing possible to pass the test.
  • Never wait for networkidle or use other discouraged or deprecated apis