everything-is-suitable/docs/plans/2026-03-07-targeted-test-fix-plan.md

测试套件针对性修复计划

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Goal: 修复测试套件中的关键问题，将前端测试通过率恢复到71.4%以上，E2E测试通过率提升到60%以上，解决测试数据冲突问题。

Architecture: 采用回滚和修复并行的策略，首先回滚导致退化的修改，然后针对性修复E2E测试和测试数据隔离问题。

Tech Stack: Vitest (前端单元测试), Playwright (E2E测试), TypeScript, Python

---

执行策略

本计划按照优先级分为三个阶段：

• 回滚阶段：回滚导致前端测试退化的修改（预计1-2小时）
• 修复阶段：针对性修复E2E测试和测试数据问题（预计3-5小时）
• 验证阶段：验证所有修复效果并生成最终报告（预计1小时）

每个任务都遵循TDD原则：先写失败测试，再实现最小化修复，最后验证通过。

---

回滚阶段：恢复前端测试稳定性（立即执行）

Task 1: 回滚密码验证器修改

Files:

• Modify: everything-is-suitable-admin/src/utils/passwordValidator.ts
• Test: everything-is-suitable-admin/src/utils/__tests__/passwordValidator.test.ts

Step 1: 检查当前密码验证器实现

Run: cd everything-is-suitable-admin && cat src/utils/passwordValidator.ts | head -50

Expected: 查看当前实现，确认问题所在

Step 2: 对比测试期望

Run: cd everything-is-suitable-admin && cat src/utils/__tests__/passwordValidator.test.ts | grep -A 5 "validate" | head -20

Expected: 了解测试期望的验证逻辑

Step 3: 回滚到简单实现

export interface PasswordValidationResult {
  valid: boolean;
  score: number;
  message?: string;
  suggestions?: string[];
}

export const passwordValidator = {
  validate: (password: string): PasswordValidationResult => {
    if (!password) {
      return {
        valid: false,
        score: 0,
        message: '密码不能为空',
      };
    }

    let score = 0;
    const suggestions: string[] = [];

    if (password.length >= 6) score += 1;
    else suggestions.push('密码长度至少6个字符');

    if (password.length >= 8) score += 1;
    else suggestions.push('建议使用8个字符以上的密码');

    if (/[a-z]/.test(password)) score += 1;
    else suggestions.push('添加小写字母');

    if (/[A-Z]/.test(password)) score += 1;
    else suggestions.push('添加大写字母');

    if (/[0-9]/.test(password)) score += 1;
    else suggestions.push('添加数字');

    if (/[^a-zA-Z0-9]/.test(password)) score += 1;
    else suggestions.push('添加特殊字符');

    const valid = score >= 4 && password.length >= 6;

    return {
      valid,
      score,
      message: valid ? '密码强度良好' : '密码强度不足',
      suggestions: valid ? [] : suggestions,
    };
  },

  getStrengthLabel: (score: number): string => {
    if (score <= 2) return '弱';
    if (score <= 4) return '中';
    if (score <= 5) return '强';
    return '非常强';
  },

  getStrengthColor: (score: number): string => {
    if (score <= 2) return '#ff4d4f';
    if (score <= 4) return '#faad14';
    if (score <= 5) return '#52c41a';
    return '#1890ff';
  },
};

export default passwordValidator;

Step 4: 运行密码验证器测试

Run: cd everything-is-suitable-admin && npm run test -- src/utils/__tests__/passwordValidator.test.ts

Expected: 测试通过率从0/24提升到至少20/24

Step 5: 提交回滚

git add everything-is-suitable-admin/src/utils/passwordValidator.ts
git commit -m "fix: rollback password validator to restore test stability"

---

Task 2: 修复API Mock配置

Files:

• Modify: everything-is-suitable-admin/src/api/__tests__/auth.api.test.ts
• Modify: everything-is-suitable-admin/src/utils/__tests__/request.test.ts
• Check: everything-is-suitable-admin/src/mocks/index.ts

Step 1: 检查当前Mock配置

Run: cd everything-is-suitable-admin && cat src/mocks/index.ts | head -50

Expected: 查看Mock服务配置

Step 2: 修复auth.api.test.ts中的Mock

import { describe, it, expect, beforeEach, vi } from 'vitest';
import { authService } from '@/services/auth.service';
import { mockAuthResponse, mockErrorResponse } from '@/mocks/mock-data';

describe('AuthService API Tests', () => {
  beforeEach(() => {
    vi.clearAllMocks();
  });

  it('should login successfully', async () => {
    const mockResponse = mockAuthResponse({
      token: 'mock-token-123',
      userInfo: {
        id: 1,
        username: 'admin',
        email: 'admin@example.com',
      },
    });

    vi.spyOn(axios, 'post').mockResolvedValue({
      data: mockResponse,
      status: 200,
    });

    const result = await authService.login('admin', 'password123');
    expect(result.token).toBe('mock-token-123');
    expect(result.userInfo.username).toBe('admin');
  });

  it('should handle login error', async () => {
    const mockError = mockErrorResponse({
      message: '用户名或密码错误',
      code: 'AUTH_FAILED',
    });

    vi.spyOn(axios, 'post').mockRejectedValue({
      response: {
        data: mockError,
        status: 401,
      },
    });

    await expect(authService.login('wrong', 'wrong')).rejects.toThrow('用户名或密码错误');
  });
});

Step 3: 修复request.test.ts中的网络错误

import { describe, it, expect, beforeEach, vi } from 'vitest';
import { request } from '@/utils/request';

describe('Request Utility Tests', () => {
  beforeEach(() => {
    vi.clearAllMocks();
  });

  it('should handle successful request', async () => {
    vi.spyOn(axios, 'request').mockResolvedValue({
      data: { success: true },
      status: 200,
    });

    const result = await request('/api/test');
    expect(result.success).toBe(true);
  });

  it('should handle network error gracefully', async () => {
    vi.spyOn(axios, 'request').mockRejectedValue(new Error('Network Error'));

    await expect(request('/api/test')).rejects.toThrow('Network Error');
  });
});

Step 4: 运行API测试

Run: cd everything-is-suitable-admin && npm run test -- src/api/__tests__/auth.api.test.ts src/utils/__tests__/request.test.ts

Expected: 测试通过率提升

Step 5: 提交修复

git add everything-is-suitable-admin/src/api/__tests__/auth.api.test.ts
git add everything-is-suitable-admin/src/utils/__tests__/request.test.ts
git commit -m "fix: resolve API mock configuration issues"

---

Task 3: 修复Store状态管理测试

Files:

• Modify: everything-is-suitable-admin/src/test/auth.store.test.ts

Step 1: 检查Store测试失败原因

Run: cd everything-is-suitable-admin && npm run test -- src/test/auth.store.test.ts 2>&1 | grep -A 10 "FAIL"

Expected: 查看具体失败原因

Step 2: 修复Store测试

import { describe, it, expect, beforeEach, vi } from 'vitest';
import { setActivePinia, createPinia } from 'pinia';
import { useAuthStore } from '@/stores/auth.store';

describe('AuthStore Tests', () => {
  beforeEach(() => {
    setActivePinia(createPinia());
  });

  it('should set token correctly', () => {
    const authStore = useAuthStore();
    authStore.setToken('test-token');
    expect(authStore.token).toBe('test-token');
  });

  it('should clear token on logout', () => {
    const authStore = useAuthStore();
    authStore.setToken('test-token');
    authStore.logout();
    expect(authStore.token).toBe('');
    expect(authStore.isAuthenticated).toBe(false);
  });

  it('should update user info', () => {
    const authStore = useAuthStore();
    const userInfo = {
      id: 1,
      username: 'testuser',
      email: 'test@example.com',
    };
    authStore.setUserInfo(userInfo);
    expect(authStore.userInfo).toEqual(userInfo);
  });
});

Step 3: 运行Store测试

Run: cd everything-is-suitable-admin && npm run test -- src/test/auth.store.test.ts

Expected: 测试通过率从9/11提升到11/11

Step 4: 提交修复

git add everything-is-suitable-admin/src/test/auth.store.test.ts
git commit -m "fix: resolve auth store test failures"

---

修复阶段：提升E2E测试稳定性（本周执行）

Task 4: 修复E2E Mock服务响应

Files:

• Modify: everything-is-suitable-admin/e2e/mock-manager.ts
• Modify: everything-is-suitable-admin/e2e/auth.spec.ts

Step 1: 检查Mock服务实现

Run: cd everything-is-suitable-admin && cat e2e/mock-manager.ts | head -80

Expected: 查看Mock服务当前实现

Step 2: 重构Mock服务以支持动态响应

import { Page, Route } from '@playwright/test';

export interface MockConfig {
  enabled: boolean;
  mode: 'full' | 'partial' | 'none';
  mockPaths: string[];
  delay: number;
  logCalls: boolean;
  validateResponses: boolean;
  dataSource: 'memory' | 'file';
}

export interface MockResponse {
  url: string;
  method: 'GET' | 'POST' | 'PUT' | 'DELETE';
  response: any;
  status?: number;
}

export class MockManager {
  private config: MockConfig;
  private mockResponses: Map<string, MockResponse> = new Map();
  private callLog: Array<{ url: string; method: string; timestamp: number }> = [];

  constructor(config: MockConfig) {
    this.config = config;
  }

  addMockResponse(config: MockResponse) {
    const key = `${config.method}:${config.url}`;
    this.mockResponses.set(key, config);
    console.log(`Mock added: ${key}`);
  }

  presetTestData(data: any) {
    this.addMockResponse({
      url: '/api/auth/login',
      method: 'POST',
      response: {
        code: 200,
        data: {
          token: 'mock-token',
          userInfo: {
            id: 1,
            username: 'admin',
            email: 'admin@example.com',
          },
        },
      },
    });

    this.addMockResponse({
      url: '/api/auth/userinfo',
      method: 'GET',
      response: {
        code: 200,
        data: {
          id: 1,
          username: 'admin',
          email: 'admin@example.com',
        },
      },
    });

    this.addMockResponse({
      url: '/api/auth/logout',
      method: 'POST',
      response: {
        code: 200,
        data: { success: true },
      },
    });
  }

  async interceptAPIRequest(page: Page) {
    await page.route('**/api/**', async (route: Route) => {
      const request = route.request();
      const url = request.url();
      const method = request.method();

      if (this.config.logCalls) {
        this.callLog.push({
          url,
          method,
          timestamp: Date.now(),
        });
      }

      const key = `${method}:${url}`;
      if (this.mockResponses.has(key)) {
        const mock = this.mockResponses.get(key)!;
        const delay = this.config.delay;

        if (this.config.logCalls) {
          console.log(`Mock response: ${key}`, mock);
        }

        if (delay > 0) {
          await new Promise(resolve => setTimeout(resolve, delay));
        }

        await route.fulfill({
          status: mock.status || 200,
          contentType: 'application/json',
          body: JSON.stringify(mock.response),
        });
      } else {
        console.log(`No mock found for: ${key}, continuing to real API`);
        await route.continue();
      }
    });
  }

  clearMockResponses() {
    this.mockResponses.clear();
    this.callLog = [];
  }

  getCallLog() {
    return this.callLog;
  }
}

Step 3: 更新auth.spec.ts使用新的Mock服务

import { test, expect } from '@playwright/test';
import { MockManager } from './mock-manager';

test.describe('用户认证', () => {
  let mockManager: MockManager;

  test.beforeEach(async ({ page }) => {
    mockManager = new MockManager({
      enabled: true,
      mode: 'full',
      mockPaths: [],
      delay: 0,
      logCalls: true,
      validateResponses: true,
      dataSource: 'memory'
    });

    mockManager.presetTestData({
      menus: [
        {
          id: 1,
          name: '仪表盘',
          code: 'dashboard',
          path: '/dashboard',
          icon: 'DashboardOutlined',
          sortOrder: 1,
          status: 'active',
          parentId: 0,
          component: 'views/Dashboard.vue',
          createBy: 'system',
          updateBy: 'system',
          createdAt: '2024-01-01T00:00:00.000Z',
          updatedAt: '2024-01-01T00:00:00.000Z',
          children: []
        }
      ]
    });

    await mockManager.interceptAPIRequest(page);
    await page.goto('/login');
  });

  test.afterEach(async () => {
    if (mockManager) {
      mockManager.clearMockResponses();
    }
  });

  test('应该显示登录页面', async ({ page }) => {
    await expect(page).toHaveTitle(/管理系统/);

    const usernameInput = page.locator('input[placeholder="请输入用户名"]');
    const passwordInput = page.locator('input[placeholder="请输入密码"]');
    const loginButton = page.locator('button[type="submit"]');

    await expect(usernameInput).toBeVisible({ timeout: 10000 });
    await expect(passwordInput).toBeVisible({ timeout: 10000 });
    await expect(loginButton).toBeVisible({ timeout: 10000 });
  });

  test('应该成功登录', async ({ page }) => {
    const usernameInput = page.locator('input[placeholder="请输入用户名"]');
    const passwordInput = page.locator('input[placeholder="请输入密码"]');
    const loginButton = page.locator('button[type="submit"]');

    await usernameInput.fill('admin');
    await passwordInput.fill('password123');
    await loginButton.click();

    await page.waitForURL('/dashboard', { timeout: 10000 });
    await expect(page.locator('.dashboard')).toBeVisible();
  });

  test('登录失败应该显示错误信息', async ({ page }) => {
    const usernameInput = page.locator('input[placeholder="请输入用户名"]');
    const passwordInput = page.locator('input[placeholder="请输入密码"]');
    const loginButton = page.locator('button[type="submit"]');

    await usernameInput.fill('wronguser');
    await passwordInput.fill('wrongpassword');
    await loginButton.click();

    await expect(page.locator('.error-message')).toBeVisible({ timeout: 5000 });
    await expect(page.locator('.error-message')).toContainText('用户名或密码错误');
  });

  test('应该能够登出', async ({ page }) => {
    const usernameInput = page.locator('input[placeholder="请输入用户名"]');
    const passwordInput = page.locator('input[placeholder="请输入密码"]');
    const loginButton = page.locator('button[type="submit"]');

    await usernameInput.fill('admin');
    await passwordInput.fill('password123');
    await loginButton.click();

    await page.waitForURL('/dashboard', { timeout: 10000 });

    const logoutButton = page.locator('[data-action="logout"]');
    await logoutButton.click();

    await page.waitForURL('/login', { timeout: 10000 });
    await expect(page.locator('input[placeholder="请输入用户名"]')).toBeVisible();
  });
});

Step 4: 运行E2E测试

Run: cd everything-is-suitable-admin && npx playwright test e2e/auth.spec.ts --reporter=list

Expected: 至少3/5测试通过

Step 5: 提交修复

git add everything-is-suitable-admin/e2e/mock-manager.ts
git add everything-is-suitable-admin/e2e/auth.spec.ts
git commit -m "fix: improve E2E mock service and test stability"

---

Task 5: 优化E2E测试等待策略

Files:

• Modify: everything-is-suitable-admin/e2e/pages/base-page.ts

Step 1: 检查当前等待策略

Run: cd everything-is-suitable-admin && cat e2e/pages/base-page.ts | grep -A 5 "waitFor"

Expected: 查看当前等待实现

Step 2: 改进基础页面类的等待方法

import { Page, Locator } from '@playwright/test';

export class BasePage {
  protected page: Page;

  constructor(page: Page) {
    this.page = page;
  }

  async navigate(url: string) {
    await this.page.goto(url, { waitUntil: 'networkidle' });
  }

  async waitForElement(locator: Locator, options?: { timeout?: number }) {
    const timeout = options?.timeout || 10000;
    await locator.waitFor({ state: 'visible', timeout });
  }

  async waitForElementToDisappear(locator: Locator, options?: { timeout?: number }) {
    const timeout = options?.timeout || 10000;
    await locator.waitFor({ state: 'hidden', timeout });
  }

  async waitForURL(url: string, options?: { timeout?: number }) {
    const timeout = options?.timeout || 10000;
    await this.page.waitForURL(url, { timeout });
  }

  async waitForNetworkIdle(options?: { timeout?: number }) {
    const timeout = options?.timeout || 10000;
    await this.page.waitForLoadState('networkidle', { timeout });
  }

  async clickElement(locator: Locator, options?: { timeout?: number }) {
    await this.waitForElement(locator, options);
    await locator.click();
  }

  async fillElement(locator: Locator, value: string, options?: { timeout?: number }) {
    await this.waitForElement(locator, options);
    await locator.fill(value);
  }

  async waitForText(locator: Locator, text: string, options?: { timeout?: number }) {
    const timeout = options?.timeout || 10000;
    await locator.waitFor({ state: 'visible', timeout });
    await expect(locator).toContainText(text, { timeout });
  }

  protected async retry<T>(fn: () => Promise<T>, maxRetries: number = 3): Promise<T> {
    let lastError: Error | undefined;
    for (let i = 0; i < maxRetries; i++) {
      try {
        return await fn();
      } catch (error) {
        lastError = error as Error;
        if (i < maxRetries - 1) {
          await this.page.waitForTimeout(1000);
        }
      }
    }
    throw lastError;
  }
}

Step 3: 更新登录页面使用改进的等待策略

import { BasePage } from './base-page';

export class LoginPage extends BasePage {
  private readonly selectors = {
    usernameInput: 'input[placeholder="请输入用户名"]',
    passwordInput: 'input[placeholder="请输入密码"]',
    loginButton: 'button[type="submit"]',
    errorMessage: '.error-message',
  };

  async navigate() {
    await this.navigate('/login');
  }

  async login(username: string, password: string) {
    await this.fillElement(this.page.locator(this.selectors.usernameInput), username);
    await this.fillElement(this.page.locator(this.selectors.passwordInput), password);
    await this.clickElement(this.page.locator(this.selectors.loginButton));
  }

  async waitForLoginSuccess() {
    await this.waitForURL('/dashboard');
    await this.waitForElement(this.page.locator('.dashboard'));
  }

  async waitForErrorMessage() {
    await this.waitForElement(this.page.locator(this.selectors.errorMessage));
  }

  async getErrorMessage(): Promise<string> {
    await this.waitForElement(this.page.locator(this.selectors.errorMessage));
    return await this.page.locator(this.selectors.errorMessage).textContent();
  }
}

Step 4: 运行E2E测试验证改进

Run: cd everything-is-suitable-admin && npx playwright test e2e/auth.spec.ts --reporter=list

Expected: 测试稳定性提升，超时错误减少

Step 5: 提交改进

git add everything-is-suitable-admin/e2e/pages/base-page.ts
git add everything-is-suitable-admin/e2e/pages/login-page.ts
git commit -m "feat: improve E2E test wait strategies"

---

Task 6: 实现测试数据清理和隔离

Files:

• Create: everything-is-suitable-admin/src/test/test-data-cleanup.ts
• Modify: everything-is-suitable-admin/vitest.config.ts

Step 1: 创建测试数据清理工具

import { cleanup } from '@testing-library/vue';

export const testDataCleanup = {
  cleanupTestData: async () => {
    cleanup();

    localStorage.clear();
    sessionStorage.clear();

    if (typeof window !== 'undefined') {
      const cookies = document.cookie.split(';');
      cookies.forEach(cookie => {
        const eqPos = cookie.indexOf('=');
        const name = eqPos > -1 ? cookie.substr(0, eqPos) : cookie;
        document.cookie = `${name}=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/`;
      });
    }
  },

  generateUniqueUsername: (prefix: string = 'test'): string => {
    const timestamp = Date.now();
    const random = Math.floor(Math.random() * 10000);
    return `${prefix}_${timestamp}_${random}`;
  },

  generateUniqueEmail: (prefix: string = 'test'): string => {
    const timestamp = Date.now();
    const random = Math.floor(Math.random() * 10000);
    return `${prefix}_${timestamp}_${random}@example.com`;
  },

  generateUniquePhone: (prefix: string = '138'): string => {
    const timestamp = Date.now();
    const random = Math.floor(Math.random() * 10000000);
    return `${prefix}${String(timestamp).slice(-4)}${String(random).padStart(8, '0')}`;
  },

  generateUniqueUserId: (): number => {
    const timestamp = Date.now();
    const random = Math.floor(Math.random() * 1000);
    return parseInt(`${timestamp}${random}`);
  },
};

export default testDataCleanup;

Step 2: 在测试文件中使用唯一数据生成器

查找所有硬编码的测试数据：

Run: cd everything-is-suitable-admin && grep -rn "testuser\|test@example.com\|13800138000" src/test/ src/services/__tests__/ src/stores/__tests__/

Expected: 列出所有硬编码的测试数据

Step 3: 替换硬编码数据

示例修改：

import { testDataCleanup } from '@/test/test-data-cleanup';

describe('UserService Tests', () => {
  it('should create user successfully', async () => {
    const userData = {
      username: testDataCleanup.generateUniqueUsername(),
      email: testDataCleanup.generateUniqueEmail(),
      phone: testDataCleanup.generateUniquePhone(),
      password: 'password123',
    };

    const result = await userService.createUser(userData);
    expect(result.success).toBe(true);
    expect(result.data.username).toBe(userData.username);
  });

  it('should handle duplicate username', async () => {
    const username = testDataCleanup.generateUniqueUsername();

    await userService.createUser({
      username,
      email: testDataCleanup.generateUniqueEmail(),
      password: 'password123',
    });

    const duplicateResult = await userService.createUser({
      username,
      email: testDataCleanup.generateUniqueEmail(),
      password: 'password123',
    });

    expect(duplicateResult.success).toBe(false);
    expect(duplicateResult.message).toContain('用户名已存在');
  });
});

Step 4: 在vitest配置中添加全局清理

import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    setupFiles: ['./src/test/setup.ts'],
    teardownFiles: ['./src/test/test-data-cleanup.ts'],
    globals: true,
    environment: 'jsdom',
    include: ['src/**/*.{test,spec}.{js,mjs,cjs,ts,mts,cts}'],
    exclude: [
      'node_modules',
      'dist',
      'e2e',
      'src/test/setup.ts',
      'src/test/test-data-cleanup.ts',
    ],
    coverage: {
      provider: 'v8',
      reporter: ['text', 'json', 'html'],
      exclude: [
        'node_modules/',
        'src/test/',
        '**/*.d.ts',
        '**/*.config.*',
        '**/mockData.ts',
      ],
    },
  },
});

Step 5: 运行测试验证数据隔离

Run: cd everything-is-suitable-admin && npm run test -- src/services/__tests__/user.service.management.test.ts

Expected: 无重复键错误

Step 6: 提交数据隔离实现

git add everything-is-suitable-admin/src/test/test-data-cleanup.ts
git add everything-is-suitable-admin/vitest.config.ts
git add everything-is-suitable-admin/src/services/__tests__/user.service.management.test.ts
git commit -m "feat: implement test data cleanup and isolation"

---

验证阶段：确认修复效果（执行后立即验证）

Task 7: 运行完整测试套件验证

Files:

• Test: All test suites

Step 1: 运行API测试

Run: cd everything-is-suitable-test/api && python -m pytest tests/unit/ -v --tb=short

Expected: 238/238测试通过，90%覆盖率

Step 2: 运行前端单元测试

Run: cd everything-is-suitable-admin && npm run test 2>&1 | grep -E "passed|failed|Test Files"

Expected: 测试通过率恢复到71.4%以上（至少450/637）

Step 3: 运行E2E测试

Run: cd everything-is-suitable-admin && npx playwright test --reporter=list 2>&1 | grep -E "passed|failed"

Expected: 测试通过率提升到60%以上（至少128/213）

Step 4: 生成最终验证报告

创建验证报告文档，记录所有测试结果和改进情况。

---

验收标准

回滚阶段验收

• 密码验证器测试通过率恢复到20/24以上
• API Mock测试通过率提升
• Store测试通过率恢复到11/11
• 前端单元测试总体通过率恢复到71.4%以上

修复阶段验收

• E2E测试通过率提升到60%以上
• 测试数据冲突问题解决
• 测试等待策略优化完成
• Mock服务配置正确

验证阶段验收

• API测试保持100%通过率
• 前端单元测试通过率≥71.4%
• E2E测试通过率≥60%
• 测试执行时间≤30分钟

最终验收标准

• 整体测试通过率≥80%
• 无测试数据冲突错误
• 测试环境隔离完善
• 生产就绪度评估

---

风险与缓解

风险1: 回滚可能引入新问题

缓解措施:

• 逐个文件回滚，每次回滚后验证
• 保留Git历史，便于快速回退
• 在测试环境先验证

风险2: E2E测试修复可能不彻底

缓解措施:

• 优先修复核心测试用例（登录、认证）
• 使用渐进式修复，每次修复一类问题
• 保持Mock服务简单可维护

风险3: 测试数据清理可能影响现有测试

缓解措施:

• 先在单个测试文件中验证
• 逐步推广到所有测试文件
• 提供详细的迁移指南

---

时间估算

阶段	任务数	预计时间	优先级
回滚阶段	3	1-2小时	立即
修复阶段	3	3-5小时	本周
验证阶段	1	1小时	执行后
总计	7	5-8小时	-

---

成功指标

量化指标

指标	修复前	目标	成功标准
前端测试通过率	51.3%	≥71.4%	恢复到修复前水平
E2E测试通过率	24%	≥60%	提升到行业标准
测试数据冲突	频繁	0次	完全解决
整体通过率	56.6%	≥80%	达到生产级别

质量指标

• ✅ 测试稳定性：无随机失败
• ✅ 测试可重复性：100%
• ✅ 测试执行效率：≤30分钟
• ✅ 代码覆盖率：API≥90%，前端≥80%

---

参考资料

• Vitest最佳实践
• Playwright测试策略
• 测试数据管理
• 测试隔离技术

---

计划完成日期: 2026-03-07 计划版本: 2.0 负责人: 测试团队 审核人: 技术负责人 预计完成时间: 2026-03-07 23:00