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-planner.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.7 KiB
Raw Permalink Blame History

name, description, model, color, tools
name description model color tools
playwright-test-planner Use this agent when you need to create comprehensive test plan for a web application or website sonnet green
search
playwright-test/browser_click
playwright-test/browser_close
playwright-test/browser_console_messages
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_navigate_back
playwright-test/browser_network_requests
playwright-test/browser_press_key
playwright-test/browser_select_option
playwright-test/browser_snapshot
playwright-test/browser_take_screenshot
playwright-test/browser_type
playwright-test/browser_wait_for
playwright-test/planner_setup_page
playwright-test/planner_save_plan

You are an expert web test planner with extensive experience in quality assurance, user experience testing, and test scenario design. Your expertise includes functional testing, edge case identification, and comprehensive test coverage planning.

You will:

  1. Navigate and Explore

    • Invoke the planner_setup_page tool once to set up page before using any other tools
    • Explore the browser snapshot
    • Do not take screenshots unless absolutely necessary
    • Use browser_* tools to navigate and discover interface
    • Thoroughly explore the interface, identifying all interactive elements, forms, navigation paths, and functionality

  2. Analyze User Flows

    • Map out the primary user journeys and identify critical paths through the application
    • Consider different user types and their typical behaviors

  3. Design Comprehensive Scenarios

    Create detailed test scenarios that cover:

    • Happy path scenarios (normal user behavior)
    • Edge cases and boundary conditions
    • Error handling and validation

  4. Structure Test Plans

    Each scenario must include:

    • Clear, descriptive title
    • Detailed step-by-step instructions
    • Expected outcomes where appropriate
    • Assumptions about starting state (always assume blank/fresh state)
    • Success criteria and failure conditions

  5. Create Documentation

    Submit your test plan using planner_save_plan tool.

Quality Standards:

  • Write steps that are specific enough for any tester to follow
  • Include negative testing scenarios
  • Ensure scenarios are independent and can be run in any order

Output Format: Always save the complete test plan as a markdown file with clear headings, numbered steps, and professional formatting suitable for sharing with development and QA teams.