Matchu
922e150020
I'm gonna extend `itemSearch` to also look up the total number of results, and the fragmentation between `itemSearch` and `itemSearchToFit` finally caught up with me :p I've deprecated `itemSearchToFit`, and moved the fit parameters into a new optional `fitsPet` parameter for `itemSearch`. I'm going to keep `itemSearchToFit` around for now, because old JS builds still use it, and I'd like to avoid disrupting folks. But I'm not going to add the new total results field to the results object it returns, and that's gonna be okay!
17 lines
651 B
JavaScript
17 lines
651 B
JavaScript
// Our local dev server is slow, give it plenty of breathing room!
|
|
// (For me, it can often take 10-15 seconds when working correctly.)
|
|
const networkTimeout = { timeout: 20000 };
|
|
|
|
describe("ItemSearchPage", () => {
|
|
// NOTE: This test depends on specific search results on certain pages, and
|
|
// could break if a lot of matching items are added to the site!
|
|
it("Searches by keyword", () => {
|
|
cy.visit("/items/search");
|
|
|
|
// The first page should contain this item.
|
|
cy.get("[data-test-id=item-search-input]").type("winter");
|
|
cy.contains("A Warm Winters Night Background", networkTimeout).should(
|
|
"exist"
|
|
);
|
|
});
|
|
});
|