0049048: Improve jest tests to make them compatible with Node 16

Openbravo Issue Tracking System - POS2

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0049048

POS2

POS

public

2022-04-06 14:53

2022-06-07 22:37

Reporter

jarmendariz

Assigned To

jarmendariz

Priority

high

Severity

major

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

TAP

Fixed in Version

Merge Request Status

Review Assigned To

jarmendariz

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0049048: Improve jest tests to make them compatible with Node 16

Description

Some tests are passing with the current Node version (v14), but v16 introduces some changes that makes a few test fails.

At the moment we only noticed two scenarios:

1- In ErrorHandler.test.js, the runtime exception message changed from - "Cannot read property 'b' of undefined" to "Cannot read properties of undefined (reading 'b')

2- Unhandled Promise rejection warning:
Currently in v14 the following message appears:

(node:539993) 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:539993) [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.

Starting from v16, those warnings becomes errors, so it would be nice to fix them as soon as possible.

Steps To Reproduce

See description

Proposed Solution

Additional Information