Skip to content

edge-cases-test-matrix.md

Latest commit

 

History

History
59 lines (43 loc) · 2.41 KB

edge-cases-test-matrix.md

File metadata and controls

59 lines (43 loc) · 2.41 KB
Raw

FolderView Plus Edge Cases and Test Matrix

This matrix is the minimum validation target before release packaging.

Known Edge Cases

  • Docker runtime long folder names can push the chevron into the Version column if app width reflow/gap guards regress.
  • Nested parent folders can hide direct members if direct-row recovery drifts from runtime membership state.
  • Mobile compact settings controls can pick up browser/theme button chrome (iPhone Safari) and render ghost box artifacts.
  • Mobile folder action sheet can clip at viewport edges on iPhone if safe-area bounds are not enforced.
  • Refresh/resize/font-load bursts can trigger width recalculation thrash if reflow debounce contracts regress.

Runtime Surfaces

Surface Required checks
Docker tab Long-name row, short-name row, dropdown alignment, Version gap, nested parent expand/collapse
VMs tab Nested expand/collapse parity, status rendering, compact viewport behavior
Dashboard widgets Nested folder expansion and quick-action visibility without overflow clipping
Settings basic/advanced Mobile compact row controls, folder action sheet bounds, no ghost boxes

Browser Matrix

Platform Browser Required
Desktop Chrome (latest) Yes
Desktop Firefox (latest) Yes
Desktop Safari/WebKit Yes
Mobile iPhone Safari Yes
Mobile Android Chrome Yes

Deterministic Browser Fixtures

The required fixture suite loads the shipped Docker runtime, settings chrome, folder editor, import, privacy, and request modules against stable local HTML and API fixtures. It does not require a running Unraid server, so UI regressions fail consistently on pull requests and release builds.

Run the default Chromium pass locally:

npm ci --ignore-scripts
npx playwright install chromium
npm run test:browser-fixtures

Run the same suite across every required desktop engine:

FVPLUS_FIXTURE_BROWSERS=chromium,firefox,webkit npm run test:browser-fixtures

JSON results and failure screenshots are written to tmp/fixture-browser-artifacts/.

Verification Checklist

  1. Run node --test tests/*.mjs.
  2. Run npm run test:browser-fixtures.
  3. Run bash scripts/release_guard.sh.
  4. Run bash scripts/install_smoke.sh.
  5. Run bash scripts/browser_smoke.sh with runtime URLs configured.
  6. Manually confirm iPhone settings rows and the folder action sheet are artifact-free.