Cypress testing doesn't work

[~/git/zap (silabs)]$ npm run test:e2e

> zap@2022.1.11 test:e2e /home/timotej/git/zap
> npm run zap-devserver | cross-env E2E_TEST=true start-test "quasar dev" http-get://localhost:8080 "cypress open"

1: starting server using command "quasar dev"
and when url "[ 'http-get://localhost:8080' ]" is responding with HTTP status code 200
running tests using command "cypress open"

 Dev mode.......... spa
 Pkg quasar........ v1.17.1
 Pkg @quasar/app... v2.2.11
 Debugging......... enabled

 Configured browser support (at least 45.26% of global marketshare):
 · Chrome for Android >= 96
 · Firefox for Android >= 95
 · QQ for Android >= 10.4
 · UC for Android >= 12.12
 · Android >= 96
 · Baidu >= 7.12
 · Chrome >= 97
 · Edge >= 97
 · Firefox >= 95
 · IE >= 11
 · iOS >= 15.2
 · Kaios >= 2.5
 · Opera Mini >= all
 · Opera Mobile >= 64
 · Opera >= 82
 · Safari >= 15.2
 · Samsung >= 15.0

 App · Running "@quasar/testing" Quasar App Extension...
 App · Running "@quasar/testing-unit-jest" Quasar App Extension...
 App · Running "@quasar/testing-e2e-cypress" Quasar App Extension...
 App · Reading quasar.conf.js
 App · Checking listening address availability (0.0.0.0:8080)...
 App · Extension(@quasar/testing-e2e-cypress): Extending quasar.conf...
(node:32833) UnhandledPromiseRejectionWarning:   TypeError: Cannot read property 'tsCheckerConfig' of undefined

  - index.js:20 Object.fn
    [zap]/[@quasar]/quasar-app-extension-testing-e2e-cypress/src/index.js:20:24

  - quasar-conf-file.js:304 
    [zap]/[@quasar]/app/lib/quasar-conf-file.js:304:18

  - extensions-runner.js:24 ExtensionsRunner.runHook
    [zap]/[@quasar]/app/lib/app-extension/extensions-runner.js:24:15

  - quasar-conf-file.js:302 QuasarConfFile.compile
    [zap]/[@quasar]/app/lib/quasar-conf-file.js:302:27

  - quasar-dev:222 goLive
    [zap]/[@quasar]/app/bin/quasar-dev:222:24

  - task_queues.js:95 processTicksAndRejections
    internal/process/task_queues.js:95:5

(Use `node --trace-warnings ...` to show where the warning was created)
(node:32833) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:32833) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
project-chip / zap

Cypress testing doesn't work #365
