feat: add Reachability Center and Why Drawer components with tests
- Implemented ReachabilityCenterComponent for displaying asset reachability status with summary and filtering options. - Added ReachabilityWhyDrawerComponent to show detailed reachability evidence and call paths. - Created unit tests for both components to ensure functionality and correctness. - Updated accessibility test results for the new components.
This commit is contained in:
@@ -1,17 +1,25 @@
|
||||
import { defineConfig } from '@playwright/test';
|
||||
|
||||
const port = process.env.PLAYWRIGHT_PORT
|
||||
? Number.parseInt(process.env.PLAYWRIGHT_PORT, 10)
|
||||
: 4400;
|
||||
|
||||
export default defineConfig({
|
||||
testDir: 'tests/e2e',
|
||||
timeout: 30_000,
|
||||
retries: process.env.CI ? 1 : 0,
|
||||
use: {
|
||||
baseURL: process.env.PLAYWRIGHT_BASE_URL ?? `http://127.0.0.1:${port}`,
|
||||
trace: 'retain-on-failure',
|
||||
},
|
||||
import { defineConfig } from '@playwright/test';
|
||||
|
||||
// Prefer the same offline-friendly Chromium resolution as Karma/unit tests.
|
||||
// Falls back to Playwright-managed installs when not available.
|
||||
// eslint-disable-next-line @typescript-eslint/no-var-requires
|
||||
const { resolveChromeBinary } = require('./scripts/chrome-path');
|
||||
|
||||
const port = process.env.PLAYWRIGHT_PORT
|
||||
? Number.parseInt(process.env.PLAYWRIGHT_PORT, 10)
|
||||
: 4400;
|
||||
|
||||
const chromiumExecutable = resolveChromeBinary(__dirname) as string | null;
|
||||
|
||||
export default defineConfig({
|
||||
testDir: 'tests/e2e',
|
||||
timeout: 30_000,
|
||||
retries: process.env.CI ? 1 : 0,
|
||||
use: {
|
||||
baseURL: process.env.PLAYWRIGHT_BASE_URL ?? `http://127.0.0.1:${port}`,
|
||||
trace: 'retain-on-failure',
|
||||
...(chromiumExecutable ? { launchOptions: { executablePath: chromiumExecutable } } : {}),
|
||||
},
|
||||
webServer: {
|
||||
command: 'npm run serve:test',
|
||||
reuseExistingServer: !process.env.CI,
|
||||
|
||||
Reference in New Issue
Block a user