e2e tests time out

[ghost]

Description

e2e tests currently time out on execution.

Current status (checked boxes are test files that work properly):

• [x] opcua-iiot-browser-e2e.test.js
• [x] opcua-iiot-browser-recursive-e2e.test.js
• [ ] opcua-iiot-connector-e2e.test.js
• [ ] opcua-iiot-crawler-e2e.test.js
• [ ] opcua-iiot-event-listener-e2e.test.js
• [ ] opcua-iiot-flex-connector-e2e.test.js
• [ ] opcua-iiot-listener-e2e.test.js
• [ ] opcua-iiot-method-caller-e2e.test.js
• [x] opcua-iiot-read-e2e.test.js
• [ ] opcua-iiot-response-e2e.test.js
• [ ] opcua-iiot-result-filter-e2e.test.js
• [ ] opcua-iiot-server-aso-e2e.test.js
• [ ] opcua-iiot-server-cmd-e2e.test.js
• [x] opcua-iiot-write-e2e.test.js

In most test cases, the main issue seems to be that the inject, which starts the flow, is never triggered. The quick solution that fixes many cases immediately is to using helper.getNode(<Inject_Node_ID>) to find the inject node, and then calling injectNode.receive() on a couple second timeout to trigger the flow (this is handled by the function exported from the helper file).

In other cases the flow needs to be adapted, or the continued failure may be indicative of a bug.

Motivation

better code coverage allows us to more easily check if a change causes unforeseen behavior. Increasing code coverage lowers our reliance on manually using test-flows to check if a node or a specific function still works. It also allows such checks to be automated. such as in our actions, and more code coverage looks better to potential contributors.

[github-actions[bot]]

This issue is stale because it has been open 45 days with no activity. It will be closed in 5 days, but can be saved by removing the stale label or commenting.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. It will be closed in 15 days, but can be saved by removing the stale label or commenting.