The component-tests-workshop's discuss from goldbergyoni

component-tests-workshop's Issues

Where are the solutions?

I was watching the recording of the workshop which cut off at about 1 hr and was curious where the solutions to the challenges are?

Object.error [as handleError] (src/error-handling.js:4:13)

Hi @goldbergyoni ,

When running npm run test as part of the workshop preparation, I get heaps of error related to Object.error

  2 | const errorHandler = {
  3 |   handleError: async (errorToHandle) => {
> 4 |     console.error(errorToHandle);
    |             ^
  5 |     metricsExporter.fireMetric('error', {
  6 |       errorName: errorToHandle.name || 'generic-error',
  7 |     });

  at Object.error [as handleError] (src/error-handling.js:4:13)
  at handleError (src/entry-points/sensors-api.js:110:24)
  at Layer.handle_error (node_modules/express/lib/router/layer.js:71:5)
  at trim_prefix (node_modules/express/lib/router/index.js:326:13)
  at node_modules/express/lib/router/index.js:286:9
  at Function.process_params (node_modules/express/lib/router/index.js:346:12)
  at next (node_modules/express/lib/router/index.js:280:10)
  at node_modules/express/lib/router/index.js:646:15
  at next (node_modules/express/lib/router/index.js:265:14)
  at next (node_modules/express/lib/router/route.js:136:14)
  at next (src/entry-points/sensors-api.js:65:7)

A worker process has failed to exit gracefully

Hi Yoni, when running npm run test with node 18.1.0, tests are passing, but I'm getting this error message:

A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.

Recommend Projects