Use `vitest` for backend tests: - `bench` script now uses [vitest's `bench`](https://vitest.dev/api/#bench) - e2e test fails with same error happening now with jest:`data-testid` attribute not present. vitest left, jest right <img width="1264" height="603" alt="image" src="https://github.com/user-attachments/assets/56fc43a6-e143-4208-bf14-7e016aae7fa9" />
30 lines
889 B
JavaScript
30 lines
889 B
JavaScript
// @ts-check
|
|
|
|
import { queryByTestId } from "@testing-library/dom";
|
|
import { describe, expect, it } from "vitest";
|
|
|
|
import { renderError } from "../src/common/render.js";
|
|
|
|
import "@testing-library/jest-dom/vitest";
|
|
|
|
describe("Test render.js", () => {
|
|
it("should test renderError", () => {
|
|
document.body.innerHTML = renderError({ message: "Something went wrong" });
|
|
expect(
|
|
queryByTestId(document.body, "message")?.children[0],
|
|
).toHaveTextContent(/Something went wrong/gim);
|
|
expect(
|
|
queryByTestId(document.body, "message")?.children[1],
|
|
).toBeEmptyDOMElement();
|
|
|
|
// Secondary message
|
|
document.body.innerHTML = renderError({
|
|
message: "Something went wrong",
|
|
secondaryMessage: "Secondary Message",
|
|
});
|
|
expect(
|
|
queryByTestId(document.body, "message")?.children[1],
|
|
).toHaveTextContent(/Secondary Message/gim);
|
|
});
|
|
});
|