Add database fixture utilities for Playwright tests with before-hook and inline setup patterns

[Copilot]

Enables pre-registering or mocking IndexedDB and Chrome Storage data in Playwright tests to verify behavior against specific data scenarios.

Implementation

Core utilities (test/emulator/db-fixtures.js):

• setupDatabase(worker, profiles) - Pre-populate IndexedDB with profile data
• setupStorage(worker, syncData, localData) - Configure Chrome Storage
• getProfilesFromDatabase(worker) / queryProfiles(worker, prefix) - Verify database state
• setupTestFixture(worker, options) / cleanupTestFixture(worker) - Combined operations

Test examples:

• db-practical.spec.js - Real-world usage patterns
• db-fixtures.example.spec.js - Comprehensive examples with inline documentation

Documentation:

• DATABASE_TESTING_GUIDE.md - Japanese guide
• README_DATABASE_TESTING.md - English reference

Usage

Before-hook pattern for shared test data:

test.beforeEach(async ({ context }) => {
  [worker] = context.serviceWorkers();
  await setupTestFixture(worker, {
    profiles: [
      { profilePath: '[COMPLEX];000001', name: 'base', aws_account_id: '111122223333' },
      { profilePath: 'base;000002', name: 'dev', aws_account_id: '444455556666', role_name: 'developer' }
    ],
    syncData: { configStorageArea: 'sync' },
    localData: { profilesTableUpdated: 2000 }
  });
});

test('should filter roles correctly', async ({ expect }) => {
  const roles = await queryProfiles(worker, 'base;');
  expect(roles).toHaveLength(1);
  expect(roles[0].role_name).toBe('developer');
});

Inline pattern for test-specific scenarios:

test('handles empty database', async ({ expect }) => {
  await setupDatabase(worker, []);
  const profiles = await getProfilesFromDatabase(worker);
  expect(profiles).toHaveLength(0);
});

Original prompt

playwrightのテストにおいて、データベースのデータをbeforeで事前登録するかmockして、データ内容に応じた正しい結果が得られるかtestするための方法を考えて

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.