rollback

Author: seancoding-day

webqa_agent/llm/prompt.py

@@ -83,44 +83,13 @@ class LLMPrompt:
     - All plans must reflect actual context in screenshot.
     - Always output strict **valid JSON**. No comments or markdown.
 
-    ## Navigation Strategy Guidelines (CRITICAL)
-
-    ### Action Selection Priority for Navigation
-    When planning navigation actions, follow this STRICT priority order:
-
-    1. **GoToPage (HIGHEST RELIABILITY - PREFERRED)**
-       - Use when: Target URL is known or can be determined
-       - Best for: Returning to original tabs/pages, switching between known pages, going to homepage
-       - Reliability: 100% - Direct URL manipulation, no UI dependency
-       - Example: Returning to original tab with known URL
-
-    2. **GoBack (HIGH RELIABILITY)**  
-       - Use when: Browser history navigation is appropriate
-       - Best for: Sequential backward navigation
-       - Reliability: 95% - Browser-native functionality
-       - Example: Returning to previous form after submission
-
-    3. **Tap/Click (LOWER RELIABILITY - USE WITH CAUTION)**
-       - Use when: Target URL is unknown AND element interaction is required
-       - Best for: Discovering new pages, triggering dynamic content
-       - Reliability: 60-80% - Depends on element state, page load, icon behavior
-       - Example: Clicking unexplored menu items
-
-    ### Critical Decision Rule
-    **IF you know the target URL → ALWAYS use GoToPage over Tap**
-    - This includes: returning to original tab, going to homepage, switching between tabs
-    - Rationale: URL navigation is deterministic, UI element clicks are probabilistic
-
     ## Actions
 
     Each action includes `type` and `param`, optionally with `locate`.
 
         Each action has a
-        - type: 'Tap', tap the located element [USE ONLY WHEN URL UNKNOWN]
+        - type: 'Tap', tap the located element
         * {{ locate: {{ id: string }}, param: null }}
-        * WARNING: Less reliable for navigation - UI elements may fail or behave inconsistently
-        * Use ONLY when: target URL is unknown AND you need to discover new pages
-        * Do NOT use for: returning to known pages, switching tabs when URLs are available
         - type: 'Hover', move mouse over to the located element
         * {{ locate: {{ id: string }}, param: null }}
         - type: 'Input', replace the value in the input field
@@ -147,12 +116,9 @@ class LLMPrompt:
         - type: 'GetNewPage', get the new page
         * {{ param: null }}
         * use this action when the instruction is a "get new page" statement or "open in new tab" or "open in new window".
-        - type: 'GoToPage', navigate directly to a specific URL [PREFERRED FOR RELIABLE NAVIGATION]
+        - type: 'GoToPage', navigate directly to a specific URL
         * {{ param: {{ url: string }} }}
-        * CRITICAL: This is the MOST RELIABLE navigation method - use whenever target URL is known
-        * PREFERRED for: returning to original tab/page, switching between known pages, going to homepage
-        * AVOID clicking UI elements (logos, icons) for navigation when URL is available
-        * Example: To return to original tab, use GoToPage with the original URL instead of clicking browser tabs or page icons
+        * use this action when you need to navigate to a specific web page URL, useful for returning to homepage or navigating to known pages.
         - type: 'GoBack', navigate back to the previous page
         * {{ param: null }}
         * use this action when you need to go back to the previous page in the browser history, similar to clicking the browser's back button.
@@ -446,41 +412,6 @@ class LLMPrompt:
         }
         ```
 
-        #### Example 8: Return to Original Tab/Page (CRITICAL PATTERN)
-        "Return to the original tab/page where we started"
-        ```json
-        {
-          "actions": [
-            {
-              "type": "GoToPage",
-              "thought": "Using GoToPage for guaranteed navigation back to original URL. This is more reliable than clicking UI elements which may fail or behave unpredictably.",
-              "param": {"url": "https://original-site.com/original-page"},
-              "locate": null
-            }
-          ],
-          "taskWillBeAccomplished": true,
-          "furtherPlan": null,
-          "error": null
-        }
-        ```
-
-        #### Counter-Example: What NOT to do for Navigation
-        "Return to the original tab"
-        ```json
-        // ❌ WRONG - Unreliable approach
-        {
-          "actions": [
-            {
-              "type": "Tap",
-              "thought": "Click the site logo to return",
-              "param": null,
-              "locate": {"id": "1"}
-            }
-          ],
-          "error": "This approach is unreliable - UI elements may not achieve intended navigation"
-        }
-        ```
-
         #### Example of what NOT to do
         - If the action's `locate` is null and element is **not in the screenshot**, don't continue planning. Instead:
         ```json

webqa_agent/testers/case_gen/prompts/agent_prompts.py

@@ -89,53 +89,6 @@ def get_execute_system_prompt(case: dict) -> str:
 - **Single Tool Call**: Execute only ONE `execute_ui_action` or `execute_ui_assertion` per instruction
 - **Error Handling**: If any action in the sequence fails, stop and report the error - do not attempt subsequent actions
 
-## Navigation Reliability Guidelines (CRITICAL)
-
-### Navigation Action Selection Priority
-When executing navigation-related actions, follow these reliability guidelines:
-
-**1. Prefer URL-based Navigation (HIGHEST RELIABILITY - 100%)**
-- When returning to known pages, switching tabs, or navigating to specific URLs
-- Use direct URL navigation instead of clicking UI elements when URL is available
-- Example actions: "Return to homepage", "Go back to original page", "Switch to previous tab"
-- Implementation: Always request URL-based navigation when target URL is known
-
-**2. Browser History Navigation (HIGH RELIABILITY - 95%)**
-- For sequential backward navigation through browser history
-- Use browser back functionality for natural user flow
-- Example actions: "Go back to previous page", "Navigate to previous form"
-
-**3. UI Element Navigation (LOWER RELIABILITY - 60-80%)**
-- Use ONLY when target URL is unknown AND discovery is required
-- Warning: UI elements (logos, icons, menu items) may fail or behave inconsistently
-- Example actions: "Click unknown menu item", "Explore new section"
-
-### Critical Navigation Decision Rules
-- **Known URL Available**: ALWAYS prefer URL-based over UI element clicking
-- **Returning to Original Tab**: Use URL navigation instead of clicking tab or logo
-- **Homepage Navigation**: Use direct URL instead of clicking logo
-- **Error Recovery**: If UI navigation fails, attempt URL-based fallback
-
-### Navigation Error Handling
-**Navigation Failure Patterns**:
-- UI elements may not respond (disabled, hidden, non-functional)
-- Logo clicks may not navigate to expected pages
-- Tab switching via UI may fail in complex applications
-- Menu items may lead to unexpected destinations
-
-**Navigation Recovery Strategy**:
-1. Detect navigation failure through page URL verification
-2. Identify target URL from context or previous navigation
-3. Attempt direct URL-based navigation as fallback
-4. Report navigation method and success/failure for analysis
-
-### Navigation Success Validation
-After any navigation action, verify:
-- Current URL matches expected destination
-- Page content confirms successful navigation
-- No error messages or unexpected redirects occurred
-- Navigation state is stable for subsequent actions
-
 ## Test Execution Hierarchy (Priority Order)
 
 ### 1. Single Action Imperative (HIGHEST PRIORITY)

webqa_agent/testers/case_gen/prompts/planning_prompts.py

@@ -170,55 +170,7 @@ def get_shared_test_design_standards(language: str = 'zh-CN') -> str:
 - **Minimize Navigation**: Prefer testing multiple features on the same page before navigating away
 - **Logical Flow**: Follow realistic user navigation patterns and business workflows
 - **State Preservation**: Consider page state changes and user context throughout navigation
-- **Business Journey**: Align navigation with typical business user journeys and workflows
-
-### Navigation Method Selection (CRITICAL)
-**PRIORITY**: When generating navigation steps, follow this reliability hierarchy:
-
-**1. URL-Based Navigation (HIGHEST RELIABILITY - 100%)**
-- **Preferred Actions**: Use "Go to [URL]" or "Navigate to [page]" when target URL is known
-- **Use Cases**: Returning to original tab, going to homepage, switching between specific pages
-- **Examples**: "Go to homepage URL", "Return to original test page", "Navigate to product catalog"
-- **Rationale**: Direct URL manipulation is deterministic and never fails due to UI element issues
-
-**2. Browser History Navigation (HIGH RELIABILITY - 95%)**
-- **Preferred Actions**: Use "Go back to previous page" for sequential navigation
-- **Use Cases**: Returning to previous forms, navigating backward through user flow
-- **Examples**: "Go back to search results", "Return to previous form page"
-
-**3. UI Element Navigation (LOWER RELIABILITY - 60-80%)**
-- **Caution Required**: Use ONLY when target URL is unknown AND discovery is required
-- **Risk Factors**: UI elements (logos, icons, menu items) may fail or behave inconsistently
-- **Use Cases**: Exploring unknown menu items, discovering new functionality
-- **Examples**: "Click unknown navigation link", "Explore new menu section"
-
-### Navigation Action Guidelines for Step Generation
-When generating navigation-related test steps:
-
-1. **Check URL Availability**: If target destination URL is known or can be determined, ALWAYS prefer URL-based navigation
-2. **Avoid Risky UI Clicks**: Don't use "Click logo to return home" - use "Go to homepage URL" instead
-3. **Document Navigation Method**: Include reason for navigation method choice in step description
-4. **Provide Fallbacks**: If UI navigation fails, suggest URL-based alternatives
-
-### Enhanced Navigation Examples
-```json
-// ✅ PREFERRED - URL-based navigation
-{{"action": "Go to homepage URL to restart the test flow"}}
-{{"action": "Navigate to https://example.com/products to test catalog"}}
-{{"action": "Return to original test page URL"}}
-
-// ✅ ACCEPTABLE - Browser history navigation  
-{{"action": "Go back to previous search results page"}}
-{{"action": "Use browser back to return to form"}}
-
-// ⚠️ USE WITH CAUTION - UI element navigation
-{{"action": "Click 'Products' menu item to explore catalog"}} 
-// Note: Only when URL is unknown or discovery is the goal
-
-// ❌ AVOID - Risky UI navigation when URL is known
-{{"action": "Click logo to return to homepage"}} 
-// Should be: {{"action": "Go to homepage URL"}}
-```"""
+- **Business Journey**: Align navigation with typical business user journeys and workflows"""
 
 
 def get_test_case_planning_system_prompt(
@@ -1457,36 +1409,4 @@ def get_dynamic_step_generation_prompt() -> str:
 - **Mixed Elements**: Evaluate primary elements affecting objective
 - **Insufficient Context**: Document uncertainty, use conservative approach
 
-### Navigation Element Classification
-
-**DECISION ALGORITHM - Apply in this exact order:**
-
-1. Check for `href` attribute → If present, element IS navigable
-2. Check for `target="_blank"` or `target="_new"` → If present, MUST test with click action
-3. Check for `onclick` or `data-toggle` → If present, requires interaction testing
-4. Check for `download` attribute → If present, requires download verification
-
-**CRITICAL RULES:**
-
-✅ **ALWAYS TEST these elements:**
-- ANY element with `target="_blank"` → Opens new tab, MUST verify navigation
-- Dropdown items with `href` → Are navigation links, NOT decorative
-- Elements with both `href` and `target` → Priority test candidates
-- Modal/popup triggers (`data-toggle="modal"`) → Require interaction verification
-
-❌ **NEVER SKIP these as "passive":**
-- Menu items with `target="_blank"` → These are active navigation elements
-- Links with `rel="noopener"` or `rel="noreferrer"` → Security attributes indicate real links
-- Dropdown options with URLs → These navigate to new pages/tabs
-
-**ATTRIBUTE REFERENCE:**
-- `target="_blank"`: Opens new browser tab - requires click test to verify behavior
-- `href="#"` vs `href="https://..."`: First is page anchor, second is external navigation
-- `download`: Triggers file download - verify download initiates correctly
-- `rel="noopener noreferrer"`: Security for new tab links - confirms real navigation intent
-
-**EXAMPLES:**
-✅ CORRECT: "Model Arena" with `href="/arena" target="_blank"` → Generate: "Click 'Model Arena' to verify new tab navigation"
-❌ WRONG: "Model Arena" with `target="_blank"` → Skip as "persistent UI indicator"
-
 Remember: Quality over quantity. Generate only the most valuable steps that properly handle UI state transitions and element lifecycles."""