Slow require time in jest about node-opcua HOT 3 CLOSED

node-opcua loads approximately in 300ms on my computer.

If you are only using the client API, you could gain 25% to 30% load time by just using
"node-opcua-client" instead of "node-opcua".
Loading the server and address-space API is unnecessary if you are using the Client API.

Alternatively, you could use a different test framework ( mocha or vitest)

• node-opcua is using mocha, and we can parallel all test effectively,
• I am been experiencing with vitest lately and find it amazing.

from node-opcua.

Thanks for the tips.
In integration testing I am using both client and server.

I have found a jest runtime which will disable the isolation between test files:

https://www.npmjs.com/package/@m-abboud/hella-fast-jest-runtime

From its description:
The core problem that this is addressing is that jest runs test suites in isolation from each other. So for every test file you have jest has to reload many modules and setup a new test env which can be very slow at least on some projects especially ones using jsdom. Running test suites in isolation is of course helpful because it helps prevent tests interfering with each other which can be a real pain to debug and track down, but I've found that this type of problem is quite rare. The trade off of having way faster tests over these occasional test bugs is way worth it to me and probably other people too.

from node-opcua.

Thank for the tip. Let's close for now.

from node-opcua.