54% of software defects in production are caused by human error during testing. 54% of software defects in production are caused by human error during testing. If you are a QA Engineer or a Full Stack Developer, you know the pain of Web UI Testing. You spend days writing Selenium or Playwright scripts, targeting specific div IDs and XPath selectors. Then, a frontend developer changes a CSS class, and your entire test suite turns red. Web UI Testing Traditional RPA (Robotic Process Automation) is brittle. It breaks when the UI changes. It’s strictly rule-based. In this engineering guide, based on research from Fujitsu’s Social Infrastructure Division, we are going to build a "Next-Gen" Testing Pipeline. We will move away from brittle scripts and move toward Autonomous AI Agents. "Next-Gen" Testing Pipeline Autonomous AI Agents We will combine Combinatorial Parameter Generation (to ensure we test every edge case) with AI Agents (using tools like browser-use) that "see" the website like a human, making your tests immune to UI changes. Combinatorial Parameter Generation AI Agents The Architecture: The Agentic Test Loop We are building a system that doesn't just "click coordinates"; it understands intent. intent The Pipeline: The Pipeline: Source Analysis: Extract parameters from the code/specifications.
Combinatorial Engine: Generate the minimum set of test cases to cover all logic paths.
The Agent: An LLM-driven browser controller that executes the test.
The Judge: An AI validator that checks if the output matches the expectation. Source Analysis: Extract parameters from the code/specifications. Source Analysis: Combinatorial Engine: Generate the minimum set of test cases to cover all logic paths. Combinatorial Engine: The Agent: An LLM-driven browser controller that executes the test. The Agent: The Judge: An AI validator that checks if the output matches the expectation. The Judge: Phase 1: The Combinatorial Engine (Smart Pattern Generation) A common mistake in testing is testing everything (too slow) or testing randomly (misses bugs). The research suggests analyzing source code to generate an Exhaustive Parameter Table. everything randomly Exhaustive Parameter Table We need to cover the "All-Pairs" (pairwise) combinations of settings to catch interaction bugs. **The Logic:
\ If you have 3 settings: Theme: [Dark, Light]
Notifications: [Email, SMS, Push]
Role: [Admin, User] Theme: [Dark, Light] Theme: Notifications: [Email, SMS, Push] Notifications: Role: [Admin, User] Role: Testing every combination = 2×3×2=122×3×2=12 tests.Pairwise testing can reduce this to ~6 tests while catching 90%+ of defects. **Python Implementation:
\ We can use the allpairspy library to generate this matrix automatically. from allpairspy import AllPairs

# Parameters extracted from the Web UI Source Code
parameters = [
    ["Dark", "Light"],
    ["Email", "SMS", "Push"],
    ["Admin", "User"]
]

print("PAIRWISE TEST CASES:")
for i, pairs in enumerate(AllPairs(parameters)):
    print(f"Case {i}: Theme={pairs[0]}, Notify={pairs[1]}, Role={pairs[2]}")

# Output:
# Case 0: Theme=Dark, Notify=Email, Role=Admin
# Case 1: Theme=Light, Notify=SMS, Role=Admin
# ... (Optimized list) from allpairspy import AllPairs

# Parameters extracted from the Web UI Source Code
parameters = [
    ["Dark", "Light"],
    ["Email", "SMS", "Push"],
    ["Admin", "User"]
]

print("PAIRWISE TEST CASES:")
for i, pairs in enumerate(AllPairs(parameters)):
    print(f"Case {i}: Theme={pairs[0]}, Notify={pairs[1]}, Role={pairs[2]}")

# Output:
# Case 0: Theme=Dark, Notify=Email, Role=Admin
# Case 1: Theme=Light, Notify=SMS, Role=Admin
# ... (Optimized list) Phase 2: The AI Agent (Without Selenium) This is the game-changer. Instead of writing driver.find_element(By.ID, "submit-btn").click(), we give an AI agent a high-level instruction. The research highlights the use of "Browser Use," an emerging class of AI agents that control headless browsers. "Browser Use," Why this works: Why this works: If the "Submit" button changes from <button id="btn-submit"> to <div class="clickable-submit">, Selenium fails.
The AI Agent sees a visual element labeled "Submit" and clicks it, regardless of the underlying HTML. If the "Submit" button changes from <button id="btn-submit"> to <div class="clickable-submit">, Selenium fails. The AI Agent sees a visual element labeled "Submit" and clicks it, regardless of the underlying HTML. The Implementation We will use Python with a library like langchain and playwright (simulating the browser-use concept) to build an agent that accepts the parameters from Phase 1. from langchain.chat_models import ChatOpenAI
from browser_use import Agent
import asyncio

async def run_ai_test(theme, notify, role):
    # 1. Construct the Natural Language Instruction
    instruction = f"""
    Go to 'http://localhost:3000/settings'.
    Log in as a '{role}'.
    Change the Theme to '{theme}'.
    Set Notifications to '{notify}'.
    Click 'Save'.
    Verify that the 'Success' toast message appears.
    """

    # 2. Initialize the Agent
    agent = Agent(
        task=instruction,
        llm=ChatOpenAI(model="gpt-4-vision-preview"),
    )

    # 3. Execute
    history = await agent.run()
    
    # 4. Return result
    return history.is_successful()

# Run a test case from Phase 1
asyncio.run(run_ai_test("Dark", "SMS", "Admin")) from langchain.chat_models import ChatOpenAI
from browser_use import Agent
import asyncio

async def run_ai_test(theme, notify, role):
    # 1. Construct the Natural Language Instruction
    instruction = f"""
    Go to 'http://localhost:3000/settings'.
    Log in as a '{role}'.
    Change the Theme to '{theme}'.
    Set Notifications to '{notify}'.
    Click 'Save'.
    Verify that the 'Success' toast message appears.
    """

    # 2. Initialize the Agent
    agent = Agent(
        task=instruction,
        llm=ChatOpenAI(model="gpt-4-vision-preview"),
    )

    # 3. Execute
    history = await agent.run()
    
    # 4. Return result
    return history.is_successful()

# Run a test case from Phase 1
asyncio.run(run_ai_test("Dark", "SMS", "Admin")) Phase 3: The "Past Failure" Feedback Loop (RAG) The paper notes that 54% of defects are human error—often repeating past mistakes. To fix this, we inject "Past Failure Knowledge" into the Agent. 54% of defects are human error We create a lightweight RAG (Retrieval-Augmented Generation) system. Before generating the test plan, the system checks a vector database of previous bug reports. RAG (Retrieval-Augmented Generation) The Workflow: The Workflow: Ingest: Index old Jira tickets/Bug reports into a Vector DB.
Retrieve: When testing the "Settings Page," retrieve bugs related to "Settings."
Inject: Add a constraint to the Agent's prompt. Ingest: Index old Jira tickets/Bug reports into a Vector DB. Ingest: Retrieve: When testing the "Settings Page," retrieve bugs related to "Settings." Retrieve: Inject: Add a constraint to the Agent's prompt. Inject: Modified Prompt Logic: Modified Prompt Logic: # Retrieved Context: "Bug #402: Saving settings fails when username contains emoji."

enhanced_instruction = f"""
{base_instruction}

IMPORTANT:
Based on past failure #402, please also test changing the username to 'User😊' 
before saving to ensure the app does not crash.
""" # Retrieved Context: "Bug #402: Saving settings fails when username contains emoji."

enhanced_instruction = f"""
{base_instruction}

IMPORTANT:
Based on past failure #402, please also test changing the username to 'User😊' 
before saving to ensure the app does not crash.
""" The ROI: Why Switch? The research indicates massive efficiency gains from this approach. Night/Weekend Testing: Unlike humans, AI Agents don't need sleep. You can run 10,000 permutations overnight.
Cost Reduction: The study projects a 0.5 man-month reduction per project cycle.
Zero Maintenance: When the UI changes, you don't rewrite scripts. The AI adapts. Night/Weekend Testing: Unlike humans, AI Agents don't need sleep. You can run 10,000 permutations overnight. Night/Weekend Testing: Cost Reduction: The study projects a 0.5 man-month reduction per project cycle. Cost Reduction: 0.5 man-month reduction Zero Maintenance: When the UI changes, you don't rewrite scripts. The AI adapts. Zero Maintenance: Security & Ethics Warning While powerful, AI Agents executing web actions carry risks: Data Leakage: Be careful sending proprietary specs or PII to public LLMs (OpenAI/Anthropic). Use Azure OpenAI or local models (Llama 3) for enterprise data.
Runaway Agents: Always implement a "Human-in-the-Loop" or a hard timeout to prevent the agent from clicking "Delete Database" if it gets confused. Data Leakage: Be careful sending proprietary specs or PII to public LLMs (OpenAI/Anthropic). Use Azure OpenAI or local models (Llama 3) for enterprise data. Data Leakage: Runaway Agents: Always implement a "Human-in-the-Loop" or a hard timeout to prevent the agent from clicking "Delete Database" if it gets confused. Runaway Agents: Conclusion The days of writing brittle XPath selectors are numbered. By combining Combinatorial Logic (to determine what to test) with AI Agents (to determine how to test), we can build a testing pipeline that heals itself. Combinatorial Logic what AI Agents how **Your Next Step:
\ Don't rewrite your Selenium suite yet. Start by picking one flaky test flow. Replace it with a browser-use agent and see if it survives the next UI update.

This story contains AI-generated text. The author has used AI either for research, to generate outlines, or write the text itself. 

Fujitsu

Building a Self-Healing Web Tester with AI Agents and Combinatorial Logic

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

3 Proven Strategies to Boost RAG Accuracy Beyond the Baseline

The Brain Built for Control—and the Obsession Required to Break It

A Builder’s Guide to Modern Data Platforms

Demystifying Agentic Test Automation for QA Teams

Beep Beep Bop Bop: How to Deploy Multiple AI Agents Using Local LLMs

How Will Software Engineers Lose Their Jobs Within the Next 5 Years?

3 Proven Strategies to Boost RAG Accuracy Beyond the Baseline

The Brain Built for Control—and the Obsession Required to Break It

A Builder’s Guide to Modern Data Platforms

Demystifying Agentic Test Automation for QA Teams

Beep Beep Bop Bop: How to Deploy Multiple AI Agents Using Local LLMs

How Will Software Engineers Lose Their Jobs Within the Next 5 Years?

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps