feat: multiparty conference tests updated

Author: rsarika

AGENTS.md

@@ -32,27 +32,32 @@ If the developer's message contains multiple distinct task types (for example, "
 ### Task Types
 
 **A. Create New Widget**
+
 - Developer wants to build a completely new widget from scratch
 - **Route to:** [templates/new-widget/00-master.md](./ai-docs/templates/new-widget/00-master.md)
 - **Follow:** All 7 modules (pre-questions → validation)
 - **⚠️ MANDATORY FIRST STEP:** Collect design input (see below)
 
 **B. Fix Bug in Existing Widget**
+
 - Developer reports a bug or issue in existing code
 - **Route to:** [templates/existing-widget/bug-fix.md](./ai-docs/templates/existing-widget/bug-fix.md)
 - **Follow:** Bug fix workflow with root cause analysis
 
 **C. Add Feature to Existing Widget**
+
 - Developer wants to enhance existing widget with new functionality
 - **Route to:** [templates/existing-widget/feature-enhancement.md](./ai-docs/templates/existing-widget/feature-enhancement.md)
 - **Follow:** Feature addition workflow with backward compatibility
 
 **D. Generate/Update Documentation Only**
+
 - Developer needs documentation for existing code
 - **Route to:** [templates/documentation/create-agent-md.md](./ai-docs/templates/documentation/create-agent-md.md) and [templates/documentation/create-architecture-md.md](./ai-docs/templates/documentation/create-architecture-md.md)
 - **Follow:** Documentation templates (reusable for all packages)
 
 **E. Understanding Architecture**
+
 - Developer needs to understand how something works
 - **Read:** That scope's `ai-docs/AGENTS.md` (usage) and `ai-docs/ARCHITECTURE.md` (technical details); use [Package and widget ai-docs reference](#package-and-widget-ai-docs-reference) to find the path.
 - **Available for:** station-login, user-state, store, cc-components, cc-widgets, ui-logging, test-fixtures; for task package use per-widget ai-docs (CallControl, IncomingTask, OutdialCall, TaskList).
@@ -67,21 +72,21 @@ If the developer's message contains multiple distinct task types (for example, "
 
 ```typescript
 // ❌ WRONG - Circular dependencies
-import { Widget } from '@webex/cc-widgets';      // In widget package code
-import { Widget } from '@webex/cc-widget-name';  // In cc-components code
+import {Widget} from '@webex/cc-widgets'; // In widget package code
+import {Widget} from '@webex/cc-widget-name'; // In cc-components code
 ```
 
 **ALWAYS use this pattern:**
 
 ```typescript
 // ✅ CORRECT - Proper dependency flow
 // In widget code:
-import { Component } from '@webex/cc-components';
+import {Component} from '@webex/cc-components';
 import store from '@webex/cc-store';
-import { withMetrics } from '@webex/cc-ui-logging';
+import {withMetrics} from '@webex/cc-ui-logging';
 
 // In cc-widgets aggregator (ONLY):
-import { Widget } from '@webex/cc-widget-name';
+import {Widget} from '@webex/cc-widget-name';
 ```
 
 **Dependency Flow (One Direction Only):**
@@ -106,10 +111,12 @@ cc-widgets → widget packages → cc-components → store → SDK
 #### Required Input (ONE of these):
 
 1. **Figma Link/File**
+
    - Share Figma link or file
    - LLM will extract design tokens, components, interactions
 
 2. **Screenshot/Mockup**
+
    - Upload image of desired widget UI
    - LLM will analyze colors, layout, components, spacing
 
@@ -124,6 +131,7 @@ cc-widgets → widget packages → cc-components → store → SDK
 #### If Design Input Provided:
 
 **Analyze and document:**
+
 - **Colors:** Extract hex/RGB values or Momentum tokens
 - **Components:** Identify Momentum UI components to use
 - **Layout:** Grid, flex, spacing patterns (8px/0.5rem grid)
@@ -177,7 +185,9 @@ Before generating or changing any code, you MUST complete the **pre-step section
 **Before generating code, load appropriate context:**
 
 ### Always Read (Minimal Context)
+
 1. **Pattern documentation** - [patterns/](./ai-docs/patterns/) folder
+
    - [typescript-patterns.md](./ai-docs/patterns/typescript-patterns.md) - Type safety, naming conventions
    - [react-patterns.md](./ai-docs/patterns/react-patterns.md) - Component patterns, hooks
    - [mobx-patterns.md](./ai-docs/patterns/mobx-patterns.md) - State management with observer HOC
@@ -208,10 +218,23 @@ Before generating or changing any code, you MUST complete the **pre-step section
 ### Conditionally Read
 
 **If using SDK APIs:**
+
 - Scan: [contact-centre-sdk-apis/contact-center.json](./contact-centre-sdk-apis/contact-center.json)
 - Find available methods, events, types
 - Check method signatures before using
 
+**If modifying store:**
+
+- Read: `packages/contact-center/store/ai-docs/AGENTS.md`
+- Read: `packages/contact-center/store/ai-docs/ARCHITECTURE.md`
+
+**If creating/using components:**
+
+- Read: `packages/contact-center/cc-components/ai-docs/AGENTS.md`
+
+**If working with metrics/logging:**
+
+- Read: `packages/contact-center/ui-logging/ai-docs/AGENTS.md`
 ---
 
 ## Step 3: SDK API Consultation (Before Code Generation)
@@ -223,6 +246,7 @@ Before generating or changing any code, you MUST complete the **pre-step section
 #### 1. Identify Required SDK Functionality
 
 Based on widget requirements, list needed operations:
+
 - Making calls? → Search: "call", "dial", "telephony", "outdial"
 - Fetching agents? → Search: "agent", "buddy", "team"
 - Managing tasks? → Search: "task", "interaction", "contact"
@@ -233,13 +257,15 @@ Based on widget requirements, list needed operations:
 **File:** [contact-centre-sdk-apis/contact-center.json](./contact-centre-sdk-apis/contact-center.json)
 
 **Search Strategy:**
+
 - Use keyword search in JSON
 - Look for method names, descriptions
 - Check similar/related methods
 
 #### 3. Verify API Signature
 
 For each method found, confirm:
+
 - ✅ Method name (exact spelling)
 - ✅ Parameters (names, types, required vs optional)
 - ✅ Return type
@@ -319,6 +345,7 @@ SDK (Contact Center API)
 ```
 
 **Key Rules:**
+
 - Widget consumes SDK methods via the store (through a hook) — it NEVER calls the SDK directly
 - Component NEVER accesses store (receives props)
 - Always use `observer` HOC for widgets
@@ -335,6 +362,7 @@ SDK (Contact Center API)
 You must have already completed that template's pre-step section (Pre-Enhancement Questions, Pre-Fix Questions, or 01-pre-questions as applicable); if not, do that first.
 
 **During code generation:**
+
 1. Follow pattern documentation strictly
 2. Reference existing widgets for examples
 3. Use proper TypeScript types (no `any`)
@@ -440,6 +468,7 @@ yarn build
 ```
 
 **Common errors:**
+
 - Missing types → Add type definitions
 - Import errors → Check paths and exports
 - Circular dependencies → Refactor imports
@@ -458,46 +487,60 @@ yarn build
 ### Documentation to Consider
 
 **If new widget created:**
+
 - Generated via templates (AGENTS.md + ARCHITECTURE.md)
 
 **If widget modified:**
+
 - Update: `packages/contact-center/{widget-name}/ai-docs/AGENTS.md` (if API changed)
 - Update: `packages/contact-center/{widget-name}/ai-docs/ARCHITECTURE.md` (if architecture changed)
 - Add: New examples to AGENTS.md (if new use cases)
 - Update: Troubleshooting in ARCHITECTURE.md (if new issues discovered)
 
 **If store modified:**
+
 - Update: `packages/contact-center/store/ai-docs/AGENTS.md`
 - Update: `packages/contact-center/store/ai-docs/ARCHITECTURE.md`
 
 **If component library modified:**
+
 - Update: `packages/contact-center/cc-components/ai-docs/AGENTS.md`
 
 **If new pattern established:**
+
 - Update: Relevant pattern file in [patterns/](./ai-docs/patterns/)
 
 **If architecture changed:**
+
 - Update: Relevant architecture documentation as needed
 
+**If Playwright E2E framework/docs changed:**
+
+- Update: `playwright/ai-docs/AGENTS.md`
+- Update: `playwright/ai-docs/ARCHITECTURE.md`
+- Update relevant modules in: `ai-docs/templates/playwright/`
 ---
 
 ## Step 7: Validation & Review
 
 **Before marking task complete:**
 
 1. **Run validation checks**
+
    - Tests pass: `yarn test:unit`
    - Linting passes: `yarn test:styles`
    - Build succeeds: `yarn build`
 
 2. **Code quality checks**
+
    - Follows patterns
    - No layer violations
    - Error handling present
    - Types are correct
    - Code is precise and concise (no unnecessary complexity or dead code)
 
 3. **Documentation checks**
+
    - AGENTS.md updated if needed
    - ARCHITECTURE.md updated if needed
    - Examples work
@@ -540,16 +583,19 @@ ccWidgets/
 ## Common Questions to Ask
 
 **Before starting any work:**
+
 - "What component/widget are you working on?"
 - "Is this a new widget, bug fix, or enhancement?"
 - "Do you have design specifications (Figma, screenshots)?"
 
 **During code generation:**
+
 - "Should I add/update tests?"
 - "Do you want examples in documentation?"
 - "Should I update the sample apps?"
 
 **After code generation:**
+
 - "The code is complete. Should I update documentation?"
 - "Would you like to review before I mark this complete?"
 - "Should I check for any other impacted components?"
@@ -561,12 +607,14 @@ ccWidgets/
 **Location:** [contact-centre-sdk-apis/contact-center.json](./contact-centre-sdk-apis/contact-center.json)
 
 **Contents:**
+
 - All exposed SDK APIs (methods, events, types)
 - Method signatures and parameters
 - Event names and data structures
 - Links to SDK source code (next branch)
 
 **Usage:**
+
 - Scan JSON when using SDK methods
 - Search for API by name or functionality
 - Check parameter types and return values
@@ -579,6 +627,7 @@ ccWidgets/
 ## Success Criteria
 
 **Code generation/fix is successful when:**
+
 - ✅ Follows architecture pattern (Widget → Hook → Component → Store → SDK)
 - ✅ Uses patterns correctly (TypeScript, React, MobX, WC)
 - ✅ Includes proper error handling

ai-docs/patterns/testing-patterns.md

@@ -30,13 +30,22 @@ packages/contact-center/{package}/
         └── index.test.tsx
 
 playwright/
-├── tests/
+├── suites/                         # Test suite orchestration
+│   ├── digital-incoming-task-tests.spec.ts
+│   ├── station-login-user-state-tests.spec.ts
+│   ├── conference-tests1.spec.ts
+│   └── ... (other suites)
+├── tests/                          # Individual test implementations
 │   ├── station-login-test.spec.ts
 │   ├── user-state-test.spec.ts
-│   └── tasklist-test.spec.ts
+│   ├── tasklist-test.spec.ts
+│   ├── conference-set7-tests.spec.ts
+│   └── ... (other test factories)
 └── Utils/
     ├── stationLoginUtils.ts
-    └── userStateUtils.ts
+    ├── userStateUtils.ts
+    ├── conferenceUtils.ts          # Multi-agent coordination
+    └── ... (other utilities)
 ```
 
 ---
@@ -245,6 +254,83 @@ test.describe('Station Login Tests - Dial Number Mode', () => {
 });
 ```
 
+### Multi-Agent Testing Pattern
+
+```typescript
+// playwright/tests/multi-agent-feature-test.spec.ts
+import {test, expect} from '@playwright/test';
+import {TestManager} from '../test-manager';
+import {performMultiAgentOperation} from '../Utils/featureUtils';
+import {verifyCurrentState} from '../Utils/userStateUtils';
+import {USER_STATES} from '../constants';
+
+export default function createMultiAgentTests() {
+  return () => {
+    let testManager: TestManager;
+
+    test.beforeAll(async ({browser}, testInfo) => {
+      testManager = new TestManager(testInfo.project.name);
+      // Configure based on test requirements (2-4 agents)
+      await testManager.setup(browser, {
+        needsAgent1: true,
+        needsAgent2: true,
+        needsAgent3: true,  // Optional: for 3+ agent scenarios
+        needsAgent4: true,  // Optional: for 4 agent scenarios
+        needsCaller: true,
+        enableConsoleLogging: true,
+      });
+    });
+
+    test.afterAll(async () => {
+      await testManager.cleanup();
+    });
+
+    test('should perform multi-agent operation and verify all participants', async () => {
+      // Perform multi-agent operation
+      await performMultiAgentOperation(
+        testManager.agent1Page,
+        testManager.agent2Page,
+        testManager.agent3Page,
+        testManager.agent4Page,
+        testManager.callerPage,
+        testManager.projectName
+      );
+
+      // Verify states
+      await verifyCurrentState(testManager.agent1Page, USER_STATES.ENGAGED);
+      await verifyCurrentState(testManager.agent2Page, USER_STATES.ENGAGED);
+      await verifyCurrentState(testManager.agent3Page, USER_STATES.ENGAGED);
+    });
+
+    test('should handle participant state transitions', async () => {
+      // Setup multi-agent scenario
+      await performMultiAgentOperation(
+        testManager.agent1Page,
+        testManager.agent2Page,
+        testManager.agent3Page,
+        testManager.agent4Page,
+        testManager.callerPage,
+        testManager.projectName
+      );
+
+      // Perform state transition
+      await someStateTransitionOperation(testManager.agent3Page);
+
+      // Verify other agents remain in expected state
+      await verifyCurrentState(testManager.agent1Page, USER_STATES.ENGAGED);
+      await verifyCurrentState(testManager.agent2Page, USER_STATES.ENGAGED);
+    });
+  };
+}
+```
+
+**Key Points for Multi-Agent Tests:**
+- Use `needsAgent3` and `needsAgent4` configuration flags for 3-4 agent scenarios
+- Configure agent count based on test requirements (not all tests need 4 agents)
+- Create feature-specific utility modules for reusable multi-agent operations
+- Each agent has independent browser context and page
+- Adjust timeouts only when justified by actual operation requirements
+
 ---
 
 ## Playwright Utils Pattern
@@ -361,6 +447,10 @@ yarn run test:unit --coverage
 
 # Run specific E2E test
 npx playwright test tests/station-login-test.spec.ts
+
+# Run specific test set (project)
+yarn test:e2e --project=SET_1       # Digital incoming tasks
+yarn test:e2e --project=SET_7       # Multi-agent scenarios (4-agent)
 ```
 
 ---