Testiny Imported suddenly failing on my azure pipeline

Support
, ,
1

Hey!

I had my Azure pipeline set up to run tests, and then import the results to Testiny via the CLI tool. This worked perfectly until this weekend, and then it suddenly stopped working.

The logs aren’t giving me much, so I was wondering if anyone else had seen this and knew of a possible solution? We have a few major releases coming up, so having this resolved ASAP would be great

2

Hi and welcome to the Testiny forum!

I don’t see elevated errors on our servers. Could you please give some more information on what exactly you do with the CLI? E.g.

  • post the command line you are using
  • what are you importing: results to manual test runs or automated ones?
  • make sure that you’re using the latest version of the CLI

Thank you!

Additionally, if you send me you Testiny organization name and the exact time of the imports, I can probably find out a bit more :slight_smile:

Best regards,
Alex

3

Since Testiny v1.30.0 the minimum required node version is node v22. Apparently you’re using node v18 which already reached end-of-life (EOL) more than half a year ago.

Please, set the task to use node v22 or higher, recommended current LTS version is node v24.

Best regards,
Alex