It must be a bug.
Will need to investigate to see if it's possible to produce report without trimming the text.
For now you can try using ut_junit_reporter with teamcity.
You will not get the real-time progress reporting with junit, but it should be accurate and comprehensive.

Did some more investigation on that.
The actual problem is when the cursor report the actual and expected outputs do something like
Actual: refcursor [ count = 3 ] was expected to equal: refcursor [ count = 3 ]
And teamcity spects the [] to be scaped with |
I did the following and now it works like a charm:
On the UT_TEAMCITY_REPORTER_HELPER package:

 function test_failed(a_test_name varchar2, a_msg in varchar2 default null, a_details varchar2 default null, a_flow_id varchar2 default null, a_actual varchar2 default null, a_expected varchar2 default null) return varchar2 is
    l_props t_props;
  begin
    l_props('name') := a_test_name;
    l_props('message') := a_msg;
    l_props('details') := regexp_replace(a_details,'(\[)|(\])','|\1\2');
    l_props('flowId') := a_flow_id;

    if a_actual is not null and a_expected is not null then
      l_props('actual') := regexp_replace(a_actual,'(\[)|(\])','|\1\2');
      l_props('expected') := regexp_replace(a_expected,'(\[)|(\])','|\1\2');
    end if;

    return message('testFailed', l_props);
  end;

I think there is a better place to actualy scape the brakets but it was just trying stufs.

Can you give it a try?

Great stuff. You did sll thr hard work of investigation.
We will have it fixed soon.
Thanks - really helpful

@PabloTorresAnaya
I'd like to experiment a bit more with the reporter.
I didn't play around with TeamCity much, but looking at documentation, it seems possible to provide larger data as outcomes of test.
We need to escape all of the special characters.
https://confluence.jetbrains.com/display/TCD18/Build+Script+Interaction+with+TeamCity

I'll install TeamCity Docker image and see if I can get utPLSQL build running there.
https://hub.docker.com/r/jetbrains/teamcity-server/

yes, as I mention the not-escaped character were causing the issue in the end, the lenght was a dead-end clue.
Also, with the new version of the UTPLS the cursor only report the changes and not the full set.

From my point of view, escaping the "[" ,"]" characters should be suficient.

I tested on Teamcity locally (docker) with local database.
I encountered 2 issues:

• missing escape of |[ |]
• text longer tnan 4000
  If you're saying that you don't have any issues eith lenght that sounds strange as I sae those. Might need to ask Teamcity for explanation if the behavior is inconsistent.

Morning,
I dont have that issue (text onlger than 4000) because now the reporter only report the changes and the length droped to 2000 wich is totaly fine for team city.

If i have time i can try to reproduce the error but i think the issue still there.

So, I agree, there are 2 issues.