fix: error handling for HTTP status 422

Added error handling for HTTP status 422 in API responses, returning a descriptive QaseError with relevant details.

qase-javascript-commons/changelog.md

@@ -2,6 +2,12 @@
 
 ## What's new
 
+Added error handling for HTTP status 422 in API responses, returning a descriptive QaseError with relevant details.
+
+# [email protected]
+
+## What's new
+
 Use the API v2 client by default. If you want to use the API v1 client, specify the `useV2` option in the config file or
 the environment variable `QASE_TESTOPS_USEV2` as `False`.
 

qase-javascript-commons/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qase-javascript-commons",
-  "version": "2.2.5",
+  "version": "2.2.6",
   "description": "Qase JS Reporters",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

qase-javascript-commons/src/reporters/testops-reporter.ts

@@ -791,7 +791,7 @@ export class TestOpsReporter extends AbstractReporter {
       return new QaseError(message + ': Not found.');
     }
 
-    if (error.response?.status === 400) {
+    if (error.response?.status === 400 || error.response?.status === 422) {
       return new QaseError(message + ': Bad request. Body: \n ' + JSON.stringify(model));
     }