}));
+
+describe("AdminUsersPage", () => {
+ const mockUser = { id: "1", name: "Admin", role: "admin" };
+
+ beforeEach(() => {
+ jest.clearAllMocks();
+ (getCurrentUser as jest.Mock).mockReturnValue(mockUser);
+ (isAdminUser as jest.Mock).mockReturnValue(true);
+ (usersApi.list as jest.Mock).mockResolvedValue({
+ data: [
+ { id: "1", name: "John Doe", email: "john@example.com", role: "candidate", status: "active", created_at: new Date().toISOString() }
+ ],
+ pagination: { total: 1, page: 1, limit: 10 }
+ });
+ (adminCompaniesApi.list as jest.Mock).mockResolvedValue({ data: [] });
+ });
+
+ it("renders and lists users", async () => {
+ render();
+
+ expect(screen.getByText("User management")).toBeInTheDocument();
+ // Loading state
+ expect(screen.getAllByText("Loading...").length).toBeGreaterThan(0);
+
+ await waitFor(() => {
+ expect(screen.getByText("John Doe")).toBeInTheDocument();
+ expect(screen.getByText("john@example.com")).toBeInTheDocument();
+ });
+ });
+
+ it("opens create user dialog", async () => {
+ render();
+
+ await waitFor(() => screen.getByText("New user"));
+
+ // Since DialogTrigger is mocked as div, fire click
+ // Note: In real Shadcn, DialogTrigger wraps button.
+ // We need to find the "New user" button which is inside DialogTrigger.
+ // Our mock wraps children.
+
+ fireEvent.click(screen.getByText("New user"));
+
+ // Check if dialog content appears
+ // The mock Dialog renders children if open.
+ // However, the button inside DialogTrigger usually toggles state in parent.
+ // But our mock Dialog just renders based on 'open' prop controlled by parent state.
+ // Wait, the parent component controls `isDialogOpen`.
+ // The real `DialogTrigger` calls `onOpenChange(true)`.
+ // Our mock `DialogTrigger` implementation `{ children, onClick }` is nice but `onClick` isn't passed from `DialogTrigger` prop in real usage?
+ // Actually `DialogTrigger` usually doesn't take onClick, it handles it internally.
+ // But we can't easily trigger the state change in the parent unless we simulate the real trigger behavior.
+ // Since we cannot rely on complex interaction in mock, we might skip "interactions" tests if mocks are too shallow.
+ // Or we assume `New user` button click works if we didn't mock Button to do nothing.
+ // But `Dialog` relies on `isDialogOpen` state.
+
+ // Let's rely on standard library behavior:
+ // The code has `