mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-24 07:53:09 +00:00
fix: the merged tour, home and lightbox changes pass their checks
The demo gate test allows wanderer as the parity harness does, the open tour store is listed in the store registry, the trip chat card's test reads the dates and not the question's hidden label, the lightbox leaves the rtl baseline, and the tours module is formatted.
This commit is contained in:
@@ -18,7 +18,6 @@
|
||||
"components/Journey/JourneyMap.tsx": 1,
|
||||
"components/Journey/JourneyMapGL.tsx": 2,
|
||||
"components/Journey/MobileEntryView.tsx": 1,
|
||||
"components/Journey/PhotoLightbox.tsx": 3,
|
||||
"components/Journey/journeyPhotoLayer.ts": 1,
|
||||
"components/Layout/Navbar.tsx": 1,
|
||||
"components/Layout/OfflineBanner.tsx": 1,
|
||||
|
||||
@@ -39,7 +39,8 @@ describe('TripChatBlock', () => {
|
||||
expect(screen.getByRole('region', { name: 'Continue in a trip chat' })).toBeInTheDocument();
|
||||
expect(screen.getByText('Kyoto')).toBeInTheDocument();
|
||||
expect(screen.getByText('Trip chat')).toBeInTheDocument();
|
||||
expect(screen.getByText(/ to /)).toBeInTheDocument();
|
||||
// The dates, not the hidden label of the question, which has a "to" of its own.
|
||||
expect(screen.getByText(/\d to \w/)).toBeInTheDocument();
|
||||
expect(screen.getByText('Next')).toBeInTheDocument();
|
||||
expect(screen.getByText('12 places')).toBeInTheDocument();
|
||||
expect(screen.getByText('What is still missing?')).toBeInTheDocument();
|
||||
|
||||
@@ -59,6 +59,7 @@ export const UNRESET_STORES: Record<string, string> = {
|
||||
'its own tests put it back with clear(); it holds one open collection and nothing else reads it',
|
||||
useDocSyncOfferStore: NOT_YET,
|
||||
useHelpStore: NOT_YET,
|
||||
useOpenTourStore: 'the saved tour open in the Tours tab, set by its stage; the tests that read it set it themselves',
|
||||
usePluginStore: NOT_YET,
|
||||
useRoadtripPreferencesStore: NOT_YET,
|
||||
useSaveToCollectionStore: NOT_YET,
|
||||
|
||||
Reference in New Issue
Block a user