bermudalamb
549a08038e
favorites, favorites-filter, sold-filter, orders and pending-publish. Five more copies of "register a customer" and three more of the hardcoded base URL go with them. Two locators that were hiding real knowledge are now named. `gridCell` is the item's whole antd column rather than its card, needed because the SOLD ribbon renders outside the card — three specs reached for `.ant-col` directly to get at it. And `chooseAvailability` goes through the title attribute because antd's Segmented hides the real radio behind a styled label, so the input is found by role and cannot be clicked; that fact was written out twice in comments and is now written once in code. The favorite control is located page-wide rather than within a card. The storefront paginates as items accumulate and the control is named for its item anyway, so scoping to a card bought nothing and broke whenever the card was on another page. favorites-filter keeps its local `favorite()` helper. It is genuinely local — decline the opt-in, wait for the fading modal to stop intercepting pointer events, confirm the heart flipped — and belongs to that file's subject rather than to the storefront. It now takes page objects as parameters instead of reaching for locators itself, which is what a spec-level helper should look like. Two specs still drive the registration form rather than taking the `customer` fixture, and deliberately. Both are about a signed-out visitor being interrupted mid-action — favoriting an item, or switching on the favorites filter — and the claim is that the thing they asked for survives the interruption. Replacing the interruption with an API call would delete the test. Verified: favorites 6/6, favorites-filter 7/7, sold-filter 6/6, orders and pending-publish 8/8. Notably favorites-filter's "keeps showing a favorite after it sells" passes, which had been failing on a strict-mode violation from two items sharing a name across runs. Refs #137
56 lines
1.8 KiB
TypeScript
56 lines
1.8 KiB
TypeScript
import { test, expect } from './fixtures';
|
|
|
|
test.describe('Order history has a page of its own', () => {
|
|
test('a signed-out visitor is sent to sign in', async ({ page, orders }) => {
|
|
await orders.goto();
|
|
|
|
await expect(page).toHaveURL(/\/login/, { timeout: 20000 });
|
|
});
|
|
|
|
// A page, not a modal: no dialog, and the storefront is not rendered behind
|
|
// it. Putting /orders in MODAL_ROUTES would quietly undo the whole change,
|
|
// and this is what would catch it.
|
|
test('renders as a page rather than a modal over the storefront', async ({
|
|
customer,
|
|
orders,
|
|
header
|
|
}) => {
|
|
await orders.goto();
|
|
|
|
await expect(orders.heading).toBeVisible({ timeout: 20000 });
|
|
await expect(orders.anyDialog).toHaveCount(0);
|
|
await expect(header.siteTitle).toBeHidden();
|
|
});
|
|
|
|
test('says so when there are no orders, rather than showing an empty table', async ({
|
|
customer,
|
|
orders
|
|
}) => {
|
|
await orders.goto();
|
|
|
|
await expect(orders.noOrdersNotice).toBeVisible({ timeout: 20000 });
|
|
await expect(orders.continueShoppingButton).toBeVisible();
|
|
});
|
|
|
|
test('Back to Shop returns to the storefront', async ({ page, customer, orders, header }) => {
|
|
await orders.goto();
|
|
await expect(orders.heading).toBeVisible({ timeout: 20000 });
|
|
|
|
await orders.backToShopButton.click();
|
|
|
|
await expect(page).toHaveURL(/\/$/);
|
|
await expect(header.siteTitle).toBeVisible();
|
|
});
|
|
|
|
// The account view is where a customer looks for their orders, so the route
|
|
// out of it is the part that has to keep working now the table has gone.
|
|
test('My Account links to it', async ({ page, customer, accountModal, orders }) => {
|
|
await accountModal.open();
|
|
|
|
await accountModal.orderHistoryButton.click();
|
|
|
|
await expect(page).toHaveURL(/\/orders/);
|
|
await expect(orders.heading).toBeVisible();
|
|
});
|
|
});
|