Weird unit test failure messages

Big_Cat_Public_Safety_Act · April 25, 2022, 2:38pm

[j@work mflix-js]$ npm test -t mongoclient

server@1.0.0 test
jest --passWithNoTests “mongoclient”

Determining test suites to run…Setup Mongo Connection
FAIL test/lessons/mongoclient.spec.js
● Test suite failed to run

TypeError: Class constructor NodeEnvironment cannot be invoked without 'new'



  at new MongoEnvironment (test/config/mongoEnvironment.js:30:113)
  at async TestScheduler.scheduleTests (node_modules/@jest/core/build/TestScheduler.js:333:13)
  at async runJest (node_modules/@jest/core/build/runJest.js:404:19)
  at async _run10000 (node_modules/@jest/core/build/cli/index.js:320:7)
  at async runCLI (node_modules/@jest/core/build/cli/index.js:173:3)

Test Suites: 1 failed, 1 total
Tests: 0 total
Snapshots: 0 total
Time: 0.085 s
Ran all test suites matching /mongoclient/i.
Teardown Mongo Connection
(node:2505966) Warning: Accessing non-existent property ‘count’ of module exports inside circular dependency
(Use node --trace-warnings ... to show where the warning was created)
(node:2505966) Warning: Accessing non-existent property ‘findOne’ of module exports inside circular dependency
(node:2505966) Warning: Accessing non-existent property ‘remove’ of module exports inside circular dependency
(node:2505966) Warning: Accessing non-existent property ‘updateOne’ of module exports inside circular dependency

I appear to be getting the above error on every uni test.

Big_Cat_Public_Safety_Act · April 25, 2022, 6:27pm

Similar issue above.

My .env file is in the top level directory, which is mflix-js

SourabhBagrecha · April 26, 2022, 6:28am

Hi @Big_Cat_Public_Safety_Act,
Can you please confirm if you have done the following already?

In case you have any doubts, please feel free to reach out to us.

Thanks and Regards.
Sourabh Bagrecha,
Curriculum Services Engineer

Big_Cat_Public_Safety_Act · April 26, 2022, 10:05am

@SourabhBagrecha

I have done that. The .env file is in the top level directory.

I tried this solution:

github.com/vercel/next.js

Typescript: `TypeError: Class constructor cannot be invoked without 'new'`

opened 06:12PM - 05 Oct 19 UTC

closed 05:38AM - 16 Oct 19 UTC

mwildehahn

# Bug report Getting the following error in my project: ``` TypeError: Cl…ass constructor cannot be invoked without 'new' ``` Looking at some related issues: https://github.com/zeit/next.js/issues/7914 it seems like this is because I'm using a library that requires targeting `es6`, which is fine, but I'm having issues telling next.js to use native classes instead of transpiling down to functions. tsconfig.json ``` { "compilerOptions": { "declaration": false, "target": "es6", "lib": [ "dom", "dom.iterable", "esnext" ], "allowJs": true, "skipLibCheck": true, "strict": false, "forceConsistentCasingInFileNames": true, "noEmit": true, "esModuleInterop": true, "module": "esnext", "moduleResolution": "node", "resolveJsonModule": true, "isolatedModules": true, "jsx": "preserve" }, "exclude": [ "node_modules" ], "include": [ "next-env.d.ts", "**/*.ts", "**/*.tsx" ] } ``` Transpiled code: ``` var CustomNodeFactory = /*#__PURE__*/ function (_AbstractReactFactory) { Object(_babel_runtime_corejs2_helpers_esm_inherits__WEBPACK_IMPORTED_MODULE_7__["default"])(CustomNodeFactory, _AbstractReactFactory); function CustomNodeFactory() { Object(_babel_runtime_corejs2_helpers_esm_classCallCheck__WEBPACK_IMPORTED_MODULE_1__["default"])(this, CustomNodeFactory); return Object(_babel_runtime_corejs2_helpers_esm_possibleConstructorReturn__WEBPACK_IMPORTED_MODULE_3__["default"])(this, Object(_babel_runtime_corejs2_helpers_esm_getPrototypeOf__WEBPACK_IMPORTED_MODULE_5__["default"])(CustomNodeFactory).call(this, "custom-node")); } Object(_babel_runtime_corejs2_helpers_esm_createClass__WEBPACK_IMPORTED_MODULE_2__["default"])(CustomNodeFactory, [{ key: "generateModel", value: function generateModel() { return new CustomNodeModel(); } }, { key: "generateReactWidget", value: function generateReactWidget(event) { return __jsx(CustomNodeWidget, { engine: this.engine, node: event.model, __source: { fileName: _jsxFileName, lineNumber: 76 }, __self: this }); } }]); return CustomNodeFactory; }(_projectstorm_react_canvas_core__WEBPACK_IMPORTED_MODULE_10__["AbstractReactFactory"]); ``` Typescript code: ``` class CustomNodeFactory extends AbstractReactFactory< CustomNodeModel, DiagramEngine > { constructor() { super("custom-node"); } generateModel() { return new CustomNodeModel(); } generateReactWidget( event: GenerateWidgetEvent<CustomNodeModel> ): JSX.Element { return <CustomNodeWidget engine={this.engine} node={event.model} />; } } ``` ## Expected behavior Use native es6 classes and avoid error. ## System information - OS: macOS - Version of Next.js: 9.0.7

{
  "presets": [
    [
      "next/babel",
      {
        "preset-env": { "targets": { "node": true } }
      }
    ]
  ],
  "plugins": []
}

And it worked.

But now, I get:

[junlue@worktop3 mflix-js]$ node -v
v14.17.1
[junlue@worktop3 mflix-js]$ npm test -t db-connection

> server@1.0.0 test
> jest --passWithNoTests "db-connection"

Determining test suites to run...Setup Mongo Connection
Test environment found at "/home/junlue/Desktop/mflix-js/test/config/mongoEnvironment.js" does not export a "getVmContext" method, which is mandatory from Jest 27. This method is a replacement for "runScript".

SourabhBagrecha · April 28, 2022, 10:14am

Hi Junlue, can your please post the complete error message that you are getting after fixing the previous issue?

In case you have any doubts, please feel free to reach out to us.

Thanks and Regards.
Sourabh Bagrecha,
Curriculum Services Engineer

system · May 3, 2022, 10:15am

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.