bbf9274d37
* chore: upgrade Vitest to 4.0.16 and Vite to 6.4.1 - Update vitest from 2.1.9 to 4.0.16 - Update @vitest/ui from 2.1.9 to 4.0.16 - Update vitest-fetch-mock from 0.3.0 to 0.4.5 - Update vitest-mock-extended from 2.0.2 to 3.1.0 - Update vite from 4.5.14/5.4.21 to 6.4.1 across all packages - Update @vitejs/plugin-react to 5.1.2 - Update @vitejs/plugin-react-swc to 4.2.2 - Update @vitejs/plugin-basic-ssl to 2.1.0 - Update vite-plugin-dts to 4.5.4 - Rename vitest.config.ts to vitest.config.mts for ESM compatibility - Add globals: true to vitest config Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: address Vitest 4.0 and Vite 6 breaking changes - Convert arrow function mockImplementation patterns to regular functions (Vitest 4.0 breaking change: arrow functions can't be constructor mocks) - Fix CSS imports with ?inline suffix for Vite 6 compatibility - Add biome override to disable useArrowFunction rule for test files - Fix syntax errors in test files introduced by regex replacements Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: fix remaining Vitest 4.0 constructor mock patterns Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: fix more Vitest 4.0 constructor mock patterns and exclude API v2 spec files Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert more arrow function mocks to regular functions for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert more arrow function mocks to regular functions for Vitest 4.0 - Fix CrmService.integration.test.ts jsforce.Connection mock - Fix RetellSDKClient.test.ts Retell mock - Fix RetellAIService.test.ts CreditService mocks - Fix GoogleCalendarSubscriptionAdapter.test.ts CalendarAuth mock Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert Google Calendar and OAuthManager arrow function mocks for Vitest 4.0 - Fix googleapis.ts Calendar, OAuth2Client, and JWT mocks - Fix utils.ts JWT mock - Fix OAuthManager.ts defaultMockOAuthManager mock Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: add React plugin, jsdom environment, and fix more constructor mocks for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert HostRepository PrismaClient mock to regular function for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: add useOrgBranding mock to React component tests for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: update TestFunction type for Vitest 4.0 compatibility Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert listBookingReports constructor mocks to regular functions for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert UserRepository constructor mock to regular function for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert OrganizationPaymentService constructor mock to regular function for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert more constructor mocks to regular functions for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: add apps/web path aliases to vitest config Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: fix test issues for Vitest 4.0 compatibility - Fix Response constructor 204 status code issue in testUtils.ts - Fix FeaturesRepository mock persistence in handleNotificationWhenNoSlots.test.ts - Add @vitest-environment node directive to formSubmissionUtils.test.ts - Fix document.querySelector mock in embed.test.ts Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: clear EventManager spy between tests for Vitest 4.0 compatibility Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: update TeamRepository mock pattern for Vitest 4.0 compatibility Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert RoutingFormResponseRepository mock to regular function for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: convert more constructor mocks to regular functions for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: fix mock reset and spy clear issues for Vitest 4.0 Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: fix remaining test failures for Vitest 4.0 upgrade - Fix booking-validations.test.ts: convert UserRepository mock to regular function - Fix route.test.ts: update 500 error test to mock ImageResponse instead of fetch - Fix users-public-view.test.tsx: add missing mocks for getOrgFullOrigin and useRouterQuery - Add @calcom/web path alias to vitest config Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: add vitest-mocks for generated files that don't exist in CI - Add svg-hashes.json mock for route.test.ts - Add tailwind.generated.css mock for embed.test.ts - Update vitest config to use mock files Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: update vitest config aliases for CI compatibility - Use array format for aliases to ensure proper ordering - Add @calcom/platform-constants alias to resolve from source - Add @calcom/embed-react alias to resolve from source - Ensure svg-hashes.json mock alias is matched before @calcom/web Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: add @calcom/embed-snippet alias for CI compatibility Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * Fix wrong test * fix: migrate from CLI flags to VITEST_MODE env var for Vitest 4.0 Vitest 4.0 no longer allows custom CLI flags like --packaged-embed-tests-only. This change migrates to using VITEST_MODE environment variable instead: - VITEST_MODE=packaged-embed for packaged embed tests - VITEST_MODE=integration for integration tests - VITEST_MODE=timezone for timezone-dependent tests Updated vitest.config.mts to handle mode-based include/exclude patterns. Updated CI workflows and package scripts to use the new env var approach. Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: return default include pattern instead of undefined in vitest config The getTestInclude() function was returning undefined for the default case, but Vitest 4.0 expects an array. This caused 'resolved.include is not iterable' error in CI. Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: always set INTEGRATION_TEST_MODE for jsdom environment The getBookingFields.ts file checks for INTEGRATION_TEST_MODE to allow server-side imports in the jsdom environment. Without this, tests fail with 'getBookingFields must not be imported on the client side' error. Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> * fix: support legacy CLI flags for backwards compatibility with main workflow The CI runs workflows from main branch, which uses the old CLI flag approach (yarn test -- --integrationTestsOnly). This commit adds backwards compatibility by checking both VITEST_MODE env var and process.argv for the legacy flags. Co-Authored-By: Volnei Munhoz <volnei.munhoz@gmail.com> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
255 lines
9.6 KiB
TypeScript
255 lines
9.6 KiB
TypeScript
/* eslint-disable playwright/missing-playwright-await */
|
|
import { fireEvent, render, screen } from "@testing-library/react";
|
|
import { useState } from "react";
|
|
import { vi } from "vitest";
|
|
|
|
import { Button, buttonClasses } from "./Button";
|
|
|
|
const observeMock = vi.fn();
|
|
|
|
window.ResizeObserver = vi.fn().mockImplementation(function() {
|
|
return {
|
|
disconnect: vi.fn(),
|
|
observe: observeMock,
|
|
unobserve: vi.fn(),
|
|
};
|
|
});
|
|
|
|
vi.mock("../tooltip", async () => {
|
|
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
|
const actual = (await vi.importActual("../tooltip")) as any;
|
|
const TooltipMock = (props: object) => {
|
|
const [open, setOpen] = useState(false);
|
|
|
|
return (
|
|
<actual.Tooltip
|
|
{...props}
|
|
open={open}
|
|
onOpenChange={(isOpen: boolean) => {
|
|
setOpen(isOpen);
|
|
}}
|
|
/>
|
|
);
|
|
};
|
|
return {
|
|
Tooltip: TooltipMock,
|
|
};
|
|
});
|
|
|
|
// TODO: (SEAN) Fix tests for button component. Seems to be a change in the way vitest/react-testing-library is working with the DOM.
|
|
// The tests below are skipped for now, but we need to fix them.
|
|
describe.skip("(skipped) Tests for Button component", () => {
|
|
test("Should apply the icon variant class", () => {
|
|
render(<Button variant="icon">Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button");
|
|
const buttonComponentClass = buttonClasses({ variant: "icon" });
|
|
const buttonClassArray = buttonClass.className.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.some((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
});
|
|
|
|
test("Should apply the fab variant class", () => {
|
|
render(<Button variant="fab">Test Button</Button>);
|
|
expect(screen.getByText("Test Button")).toHaveClass("hidden md:inline");
|
|
});
|
|
|
|
test("Should apply the secondary color class", () => {
|
|
render(<Button color="secondary">Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button");
|
|
const buttonComponentClass = buttonClasses({ color: "secondary" });
|
|
const buttonClassArray = buttonClass.className.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.some((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
});
|
|
|
|
test("Should apply the minimal color class", () => {
|
|
render(<Button color="minimal">Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button");
|
|
const buttonComponentClass = buttonClasses({ color: "minimal" });
|
|
const buttonClassArray = buttonClass.className.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.some((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
});
|
|
|
|
test("Should apply the sm size class", () => {
|
|
render(<Button size="sm">Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button");
|
|
const buttonComponentClass = buttonClasses({ size: "sm" });
|
|
const buttonClassArray = buttonClass.className.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.some((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
});
|
|
|
|
test("Should apply the base size class", () => {
|
|
render(<Button size="base">Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button");
|
|
const buttonComponentClass = buttonClasses({ size: "base" });
|
|
const buttonClassArray = buttonClass.className.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.some((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
});
|
|
|
|
test("Should apply the lg size class", () => {
|
|
render(<Button size="lg">Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button");
|
|
const buttonComponentClass = buttonClasses({ size: "lg" });
|
|
const buttonClassArray = buttonClass.className.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.some((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
});
|
|
|
|
test("Should apply the loading class", () => {
|
|
render(<Button loading>Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button");
|
|
const buttonComponentClass = buttonClasses({ loading: true });
|
|
const buttonClassArray = buttonClass.className.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.some((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
});
|
|
|
|
test("Should apply the disabled class when disabled prop is true", () => {
|
|
render(<Button disabled>Test Button</Button>);
|
|
const buttonClass = screen.getByText("Test Button").className;
|
|
const expectedClassName = "disabled:cursor-not-allowed";
|
|
expect(buttonClass.includes(expectedClassName)).toBe(true);
|
|
});
|
|
|
|
test("Should apply the custom class", () => {
|
|
const className = "custom-class";
|
|
render(<Button className={className}>Test Button</Button>);
|
|
expect(screen.getByText("Test Button")).toHaveClass(className);
|
|
});
|
|
|
|
test("Should render as a button by default", () => {
|
|
render(<Button>Test Button</Button>);
|
|
const button = screen.getByText("Test Button");
|
|
expect(button.tagName).toBe("BUTTON");
|
|
});
|
|
|
|
test("Should render StartIcon and Plus icon if is fab variant", async () => {
|
|
render(
|
|
<Button variant="fab" StartIcon="plus" data-testid="start-icon">
|
|
Test Button
|
|
</Button>
|
|
);
|
|
expect(await screen.findByTestId("start-icon")).toBeInTheDocument();
|
|
expect(await screen.findByTestId("plus")).toBeInTheDocument();
|
|
});
|
|
|
|
test("Should render just StartIcon if is not fab variant", async () => {
|
|
render(
|
|
<Button StartIcon="plus" data-testid="start-icon">
|
|
Test Button
|
|
</Button>
|
|
);
|
|
expect(await screen.findByTestId("start-icon")).toBeInTheDocument();
|
|
expect(screen.queryByTestId("plus")).not.toBeInTheDocument();
|
|
});
|
|
|
|
test("Should render EndIcon and Plus icon if is fab variant", async () => {
|
|
render(
|
|
<Button variant="fab" EndIcon="plus" data-testid="end-icon">
|
|
Test Button
|
|
</Button>
|
|
);
|
|
expect(await screen.findByTestId("end-icon")).toBeInTheDocument();
|
|
expect(await screen.findByTestId("plus")).toBeInTheDocument();
|
|
});
|
|
|
|
test("Should render just EndIcon if is not fab variant", async () => {
|
|
render(
|
|
<Button EndIcon="plus" data-testid="end-icon">
|
|
Test Button
|
|
</Button>
|
|
);
|
|
expect(await screen.findByTestId("end-icon")).toBeInTheDocument();
|
|
expect(screen.queryByTestId("plus")).not.toBeInTheDocument();
|
|
});
|
|
});
|
|
|
|
describe.skip("(Skipped) Test for button as a link", () => {
|
|
test("Should render Link if have href", () => {
|
|
render(<Button href="/test">Test Button</Button>);
|
|
|
|
const buttonElement = screen.getByText("Test Button");
|
|
|
|
expect(buttonElement).toHaveAttribute("href", "/test");
|
|
expect(buttonElement.closest("a")).toBeInTheDocument();
|
|
});
|
|
|
|
test("Should render Wrapper if don't have href", () => {
|
|
render(<Button>Test Button</Button>);
|
|
expect(screen.queryByTestId("link-component")).not.toBeInTheDocument();
|
|
expect(screen.getByText("Test Button")).toBeInTheDocument();
|
|
});
|
|
|
|
test("Should render Tooltip if exists", () => {
|
|
render(<Button tooltip="Hi, Im a tooltip">Test Button</Button>);
|
|
const tooltip = screen.getByTestId("tooltip");
|
|
expect(tooltip.getAttribute("data-state")).toEqual("closed");
|
|
expect(tooltip.getAttribute("data-state")).toEqual("instant-open");
|
|
expect(observeMock).toBeCalledWith(tooltip);
|
|
});
|
|
test("Should not render Tooltip if no exists", () => {
|
|
render(<Button>Test Button</Button>);
|
|
expect(screen.queryByTestId("tooltip")).not.toBeInTheDocument();
|
|
expect(screen.getByText("Test Button")).toBeInTheDocument();
|
|
});
|
|
|
|
test("Should render as a button with a custom type", () => {
|
|
render(<Button type="submit">Test Button</Button>);
|
|
const button = screen.getByText("Test Button");
|
|
expect(button.tagName).toBe("BUTTON");
|
|
expect(button).toHaveAttribute("type", "submit");
|
|
});
|
|
|
|
test("Should render as an anchor when href prop is provided", () => {
|
|
render(<Button href="/path">Test Button</Button>);
|
|
const button = screen.getByText("Test Button");
|
|
expect(button.tagName).toBe("A");
|
|
expect(button).toHaveAttribute("href", "/path");
|
|
});
|
|
|
|
test("Should call onClick callback when clicked", () => {
|
|
const handleClick = vi.fn();
|
|
render(<Button onClick={handleClick}>Test Button</Button>);
|
|
const button = screen.getByText("Test Button");
|
|
fireEvent.click(button);
|
|
expect(handleClick).toHaveBeenCalledTimes(1);
|
|
});
|
|
|
|
test("Should render default button correctly", () => {
|
|
render(<Button loading={false}>Default Button</Button>);
|
|
const buttonClass = screen.getByText("Default Button").className;
|
|
const buttonComponentClass = buttonClasses({ variant: "button", color: "primary", size: "base" });
|
|
const buttonClassArray = buttonClass.split(" ");
|
|
const hasMatchingClassNames = buttonComponentClass
|
|
.split(" ")
|
|
.every((className) => buttonClassArray.includes(className));
|
|
expect(hasMatchingClassNames).toBe(true);
|
|
expect(screen.getByText("Default Button")).toHaveAttribute("type", "button");
|
|
});
|
|
|
|
test("Should pass the shallow prop to Link component when href prop is passed", () => {
|
|
const href = "https://example.com";
|
|
render(<Button href={href} shallow />);
|
|
|
|
const linkComponent = screen.getByTestId("link-component");
|
|
expect(linkComponent).toHaveAttribute("shallow", "true");
|
|
});
|
|
});
|