enzyme | JavaScript Testing utilities for React | Unit Testing library

I have a same problem too, but i am using a serialport not epoll.

So, I think the cause of this problem is electron modules not the native module.

craco's Github readme, states that it is supporting Create React App (CRA) 4.*. By this statement, I'm assuming CRA 5 is not officially supported by craco.

However, this repository utilizes both CRA 5 and craco (but I have not verified that it is working). Use this repository to compare your setup (after verifying that the linked repositry is working), and try different settings/configs to see if you get further.

Could figure out a way, sharing it here.

For a given function foo, Zygote.pullback(foo, args...) returns foo(args...) and the backward pass (which allows for gradients computations).

My goal is to tell Zygote to use Enzyme for the backward pass.

This can be done by means of Zygote.@adjoint (see more here).

In case of array-valued functions, Enzyme requires a mutating version that returns nothing and its result to be in args (see more here).

The function f! in the question post is an Enzyme-compatible version of a sum of two arrays.

Since f! returns nothing, Zygote would simply return nothing when the backward pass is called on some gradient passed to us.

A solution is to place f! inside a wrapper (say f) that returns the array s

and to define Zygote.@adjoint for f, rather than f!.

Hence,

@Limey was on the right track!

The time-transformed version of ADAMTS13level.f needs to be added to the model, instead of being separated into a separate argument of coxph(...).

The form of coxph call when testing the time-dependent categorical variables is described in How to use the timeSplitter by Max Gordon.

Other helpful documentation:

coxph - fit proportional hazards regression model

There is a separate "screen" object exported from '@testing-library/react'. that has the findByText method. you unfortunately have to manually grab screen out of the library as auto imports just think its the global "screen" when you don't import explicitly.

It seems the CustomerListTable component you are testing in isolation doesn't have access to a routing context it's expecting as when it's rendered in the app normally. It's completely normal to need to wrap components when testing them with providers (redux, themes/styling, localization, routing, etc...) that are providing specific React Context values the component is accessing, typically via React hooks.

For the unit test you should wrap the component with the providers it's expecting to have.

You would want to set up the files after the test framework has been installed

Here are a couple of ways you can go about doing it (For this particular question, method 1 is more relevant)

Replace/Add --setupFilesAfterEnv instead of using --setupFiles

Example: "test": "react-scripts test --setupFilesAfterEnv

When looking closer at the source code of react-dom and react-dom/test-utils it seems like what's making this whole thing work is this setImmediate call happening after the first effect flush in recursivelyFlushAsyncActWork.

It seems like act chooses to use this recursivelyFlushAsyncActWork simply because the callback has the signature of being "thenable", i.e. a Promise. You can see this here.

This should mean that what happens is (simplified) this:

1. The useEffect callback is flushed (putting fetch on the event loop).
2. The setImmediate callback "ensures" our mock promise / fetch is resolved.
3. A third flush happens by a recursion inside the setImmediate callback (called by enqueueTask) making the state changes appear in the DOM.
4. When there's nothing left to flush it calls the outer most resolve and our act resolves.

In the code that looks kinda like this (except this is taken from an older version of react-dom from the node_modules of my React project, nowadays flushWorkAndMicroTasks seems to be called recursivelyFlushAsyncActWork):

Had to make a few changes to my original test suite and this is what worked for me: