mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-19 13:36:48 +00:00
Maurice
055c3ae5c7
The pictures picked up five faults that the run could not see, because a passing step only proves the click landed. The ring vanished on the lightbox: the accent is nearly black and so is the overlay. It now measures the surface behind it and puts a white hairline outside itself and the number only where the contrast is too low, so every other picture keeps the single line it had. The number fell outside the picture whenever the target was wider than the frame, which is every full-width row: the frame is known before the ring is drawn, so the number moves inside far enough to clear the edge. The satellite imagery was a grey rectangle although every tile came back 200. Leaflet fades a tile in over 200 ms and takes the progress from `+new Date()`, and the browser's clock is pinned to the picture day, so the opacity it writes on every frame is always 0. A stylesheet on Leaflet's own `leaflet-tile-loaded` outranks that inline style. The satellite guide also waits for decoded tiles now instead of for a tile element to exist. The uploaded files looked like nothing anyone would upload. A PDF is drawn with an issuer band, a reference, a table of fields and a footer, and the two photographs are gone: a drawn photograph reads as clip art at any size, so the trip carries a map screenshot with a pin and a booking confirmation in a browser window, which are graphics in reality too. In the panel, a step picture was covered into a 16:10 box and lost its sides; contained everywhere now, the hero and the result in 16:9. Beside that: the place guide gained the drag-and-drop route to a day as its fourth step, in all 23 languages, and `e2e/help/README.md` now holds the whole visual contract, the traps that cost this round (the pinned clock, prettier against the client sources, a killed run holding its ports) and how to find out which pictures a change forces to be retaken.
38 lines
1.8 KiB
TypeScript
38 lines
1.8 KiB
TypeScript
import { test as setup, expect } from '@playwright/test'
|
|
import { writeFileSync, mkdirSync } from 'node:fs'
|
|
import path from 'node:path'
|
|
import { seedDemoData } from './seed'
|
|
import { E2E_BASE_URL, E2E_SEED_FILE } from '../../playwright.config'
|
|
|
|
/**
|
|
* Populates the throwaway E2E database with the demo trip before any screenshot
|
|
* runs. Its own Playwright project so it executes exactly once, after `setup`
|
|
* (which produces the authenticated storageState) and before `screenshots`.
|
|
*
|
|
* The resulting ids are written to disk because Playwright projects do not
|
|
* share memory — the capture specs read them back.
|
|
*/
|
|
setup('seed the demo trip', async ({ page, playwright }) => {
|
|
// page.request carries the storageState cookie, so this is authenticated as
|
|
// the admin. The factory hands the seeder throwaway contexts for the other
|
|
// members — see the comment in seed.ts on why they must not share one.
|
|
const result = await seedDemoData(page.request, token =>
|
|
playwright.request.newContext({
|
|
baseURL: E2E_BASE_URL,
|
|
// MUST be explicit: newContext otherwise picks up the project's
|
|
// storageState, i.e. the admin's trek_session cookie — and the server
|
|
// reads the cookie BEFORE the Authorization header
|
|
// (server/src/middleware/auth.ts:9), so every "member" write would be
|
|
// recorded as the admin while still returning 200.
|
|
storageState: undefined,
|
|
extraHTTPHeaders: token ? { Authorization: `Bearer ${token}` } : {},
|
|
}),
|
|
)
|
|
|
|
expect(result.tripId, 'trip was created').toBeTruthy()
|
|
expect(result.placeIds.length, 'places were created').toBeGreaterThan(0)
|
|
|
|
mkdirSync(path.join(process.cwd(), 'e2e', '.tmp'), { recursive: true })
|
|
writeFileSync(path.join(process.cwd(), E2E_SEED_FILE), JSON.stringify(result, null, 2))
|
|
})
|