sites/partners/tests/pages/listings/add.test.tsx:124

• This negative assertion runs immediately after render, before AuthProvider has finished loading the mocked profile. At that point ListingGuard renders null for every user, so the test would pass even if a partner were incorrectly allowed once the async profile request resolves; wait for the profile/redirect state before asserting the page stays hidden.

    const { queryByRole } = render(<NewListing />)

    expect(queryByRole("heading", { name: "New listing" })).not.toBeInTheDocument()

sites/partners/tests/pages/listings/add.test.tsx:163

• This test does not actually exercise the nonRegulated behavior: the mocked jurisdiction from user has no enableNonRegulatedListings feature flag, and the assertions only check the same heading as the default render test. If the query param stopped setting the listing type, this test would still pass; enable the feature flag in the mock and assert the non-regulated state in the form.

  it("should render the page with nonRegulated query param", async () => {
    mockRouter({ jurisdictionId: JURISDICTION_ID, nonRegulated: "true" })
    document.cookie = "access-token-available=True"

sites/partners/tests/pages/listings/add.test.tsx:82

• Because the test render wrapper only provides AuthProvider (not the app's RequireLogin gate or a preloaded AuthContext profile), ListingGuard sees profile as undefined on the initial render and redirects to /unauthorized before this happy-path assertion eventually passes. Seed the auth context or wrap the page the same way as _app so these tests verify the page renders without triggering an unauthorized redirect.

    const { findByRole, getAllByText } = render(<NewListing />)

    expect(await findByRole("heading", { name: "New listing" })).toBeInTheDocument()