text-summary | text description from a given personality profile | Natural Language Processing library

To anyone who might stumble upon this: I was able to catch the error with the "stop on exception" feature of chrome. In it we still only saw that a "null" was thrown (and no stacttrace whatsoever) but we also saw that the error happens in a zone.js task object, which provided enough information about what causes the error.

It was us. Sorry for the trouble. We threw a null object in one of the tests and did not catch it. That's a quite bad practice.

I found the solution, it was just in the file jest.tsconfig.json change the field "sourceMap" to true:

I think it was just a node_modules problem, as your repo worked after download and initialization. I think babel can fail silently if it's dependencies are out of order.

I removed package.lock (because I use yarn to manage things) and then yarn to init the dependecies.

jest runs via Node runtime, meaning there are no browser APIs. You will need to mock it. Look into jest setupFiles.

Create a setup file:

There may be any compiler error which is causing Karma Runner to Stop or you can look for your test.ts file as follows-

// Then we find all the tests. const context = require.context('./', true, /.spec.ts$/);

make sure to allow all spec.ts here.

If you want to run it by entering a command like below, you must first install serverless and the serverless plugins you use globally, for example

I found the answer here with this article!

https://sourcedcode.com/blog/aem/how-to-write-javascript-unit-tests-for-aem-client-libraries-with-jest

This is EXACTLY what I needed and the results are PERFECT!

You could do this in awk, please try following code.

Change your values as:- autoWatch: true, singleRun: false,

Optional change, it may or may not required restartOnFileChange: true

Remove space before colon:- browserDisconnectTimeout: 210000, browserNoActivityTimeout: 210000