Skip to main content
-1 votes
0 answers
87 views

I've been trying to get my test case that includes useActionState() and <form action={}> to pass. The scenario is as follows: When the "add balance" button is clicked, a <Modal/>...
Marya's user avatar
  • 196
3 votes
1 answer
62 views

I'm trying to learn how to use react-testing-library and having trouble getting started with some of my components. I keep receiving the error in the title, pointing at custom API hooks in the file. ...
npfist's user avatar
  • 167
0 votes
0 answers
67 views

I'm testing a Backstage plugin component that renders a list of Ansible components using the Backstage Table from @backstage/core-components. In my test, I mock the catalog API to return 2 entities (...
Pavan P Jangale's user avatar
0 votes
1 answer
83 views

I have a component like this to test: import {doSomethingMocked} form 'mockedLibrary'; const TheComponent = (props) => { const [isToTest, setIsToTest] = useState(false); const handleClick = ...
Daniel Reinaldo Zorro Forero's user avatar
-1 votes
2 answers
1k views

I am new to Next.js but not to React and Jest; this is the first test suite I'm setting up in Next.js. I have the following (extremely minimal, but this example does cause the error) component I am ...
cdyswnnr's user avatar
-1 votes
1 answer
652 views

I am experiencing an issue after upgrading to React-Router version 7.6.2. I was able to replicate the failure: StackBlitz. Note that this test passed when I had v6 of React-Router-DOM. The problem ...
Zlatan Sadibasic's user avatar
0 votes
1 answer
264 views

I have the following hook: function useWelcomeMessage() { const { data, error} = useGetWelcomeMessage(); const printMessage = useCallback(async () => { if (data) { alert(data) ...
Mark's user avatar
  • 2,041
0 votes
1 answer
35 views

I'm wondering if it's better to use findBy together with rejects.toThrow instead of using queryBy with not.toBeInTheDocument when checking that an element is not displayed in cases like the following. ...
Ken's user avatar
  • 1
0 votes
1 answer
46 views

I am testing my Input element by 2 way. adding value and click on button to "todo list" works fine adding value and enter the "input' field, but throws error. I am seeking ...
3gwebtrain's user avatar
  • 15.5k
1 vote
1 answer
171 views

Using NextJS 14 and react testing-library, we previously used to test client components and client-only pages that take dynamic URL parameters like this: type PageProps = { params: { date: string }...
James Crowley's user avatar
1 vote
0 answers
99 views

I know that this is a well trodden topic, but most of the articles and help topics on this talk about how to avoid, and don't actually detail what exactly causes it. I have a simple example of how we ...
dwjohnston's user avatar
  • 12.5k
0 votes
0 answers
96 views

I am trying to set up unit tests for a frontend project. Currently, i am trying to use vitest, since we use vite as well. Additionally i am going with HappyDom and TestingLibrary. Now, i am facing a ...
UberKong's user avatar
0 votes
1 answer
226 views

I'm building a NextJS (react) app with Chakra UI (version 3). I'd like to write unit tests, but I don't know to handle the way Chakra UI v3 handles select. Here's a sample test app: 'use client'; ...
John Tang Boyland's user avatar
0 votes
0 answers
133 views

I am using ToolbarPlugin from Lexical and using the code from Lexical repo. My Sonarqube has flagged below code for test coverage and am not sure what test needs to be inlcuded: `const $updateToolbar =...
Wolvoine41's user avatar
0 votes
0 answers
39 views

how to write unit tests for useUpdateTodo hook without mock useGetUserId // Get the user const useGetUserId = ()=>{ const { data: user } = useQuery({ queryKey: ['user', email], queryFn: ...
StanStanStan's user avatar

15 30 50 per page
1
2 3 4 5
249