ra-test

import * as React from "react"; import { TestContext } from 'ra-test'; import { render, fireEvent, screen } from '@testing-library/react'; // Imagine this is your custom react-admin Edit view component const MyCustomEditView = ({ basePath, id, resource }) => { const handleClick = () => { // In a real app, this might dispatch an action or navigate console.log(`Action for resource ${resource} with ID ${id} at ${basePath}`); }; return ( <div data-testid="my-custom-edit-view"> <h1>Edit {resource} #{id}</h1> <p>Base Path: {basePath}</p> <button onClick={handleClick}>Perform Action</button> </div> ); }; describe('MyCustomEditView', () => { const defaultEditProps = { basePath: '/posts', id: '123', resource: 'posts', }; it('should render the custom edit view with provided props', () => { render( <TestContext enableReducers> <MyCustomEditView {...defaultEditProps} /> </TestContext> ); expect(screen.getByText('Edit posts #123')).toBeInTheDocument(); expect(screen.getByText('Base Path: /posts')).toBeInTheDocument(); }); it('should simulate a button click', () => { const consoleSpy = jest.spyOn(console, 'log'); render( <TestContext enableReducers> <MyCustomEditView {...defaultEditProps} /> </TestContext> ); fireEvent.click(screen.getByText('Perform Action')); expect(consoleSpy).toHaveBeenCalledWith('Action for resource posts with ID 123 at /posts'); consoleSpy.mockRestore(); }); });