Skip to content
Node package

feature: the ability to specify a test metadata in tests #1789

Sign in to view logs

feature: the ability to specify a test metadata in tests

feature: the ability to specify a test metadata in tests #1789

Triggered via push September 16, 2024 14:21
@gibiwgibiw
pushed 0f5ed03
feature/add_metadata
Status Failure
Total duration 21s
Artifacts –

npm.yml

on: push
Matrix: test
Matrix: build-n-publish
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
Project qaseio - Node 16
Process completed with exit code 1.
Project qase-javascript-commons - Node 16
The job was canceled because "_16_qaseio" failed.
Project qase-javascript-commons - Node 16
The operation was canceled.
Project qase-cucumberjs - Node 16
The job was canceled because "_16_qaseio" failed.
Project qase-cucumberjs - Node 16
The operation was canceled.
Project qase-newman - Node 16
The job was canceled because "_16_qaseio" failed.
Project qase-newman - Node 16
Process completed with exit code 1.
Project qase-cypress - Node 16
The job was canceled because "_16_qaseio" failed.
Project qase-cypress - Node 16
The operation was canceled.
Project qaseio - Node 16
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Project qaseio - Node 16
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/