Closed igogo5yo closed 7 months ago
This also happens to me. I even tried updating the test suite name, and test case class name and name, to no avail. What works is deleting the section where the test case(s) created by the previous trcli
execution are, then re-executing trcli
.
Facing the same issue
I am facing this issue as well (only difference from @igogo5yo is I'm on windows). Even if I use the example junit results example from the README, I get the same error as @igogo5yo .
My command:
trcli -y -h <MYHOST> --project test --username <MYUSER> --password <MYPASSWORD> --verbose parse_junit --title "my automated test run" -f sample.xml
Okay the key for me was to go back to the automation_id and down at the bottom assign it to a project. I gave it a default value of 1. Now it works fine.
Hello and thanks for bringing this to our attention
If this worked at first, it is quite odd to fail a second time. The scenario where I might see this happening is when you have test cases which use a template to which the automation_id
is not applied. Please make sure you have configured the field according to the image below (where it's Text, you may have String, that's not an issue). Let me know if this may be the case.
@igogo5yo were you able to fix the mentioned issue? I got the same issue as you mentioned after doing the same procedure. How did you fix it?
Closing this issue in the upcoming days if further feedback is not provided
closing due to lack of feedback
TestRail CLI Version
1.5.0
CLI Environment
Mac 13.3.1 (M1 Chip), Python 3.11.3
TestRail Version
v7.8.0 Early Access (1141)
TestRail Instance Type
NA
Current behavior
I'm trying to upload the results:
and get the error:
Desired behavior
No response
More Details
I have configured the
automation_id
field as it said in the documentation. Before I added theautomation_id
field I've seen the message:After adding that filed I uploaded results successfully 1 time, then on the second try to upload results I get the error. Also, I've tried to delete and create again the
automation_id
field, but it didn't help.