Hi,

Same fail here using Jenkins 2.277.3 and xunit 3.0.2 report junit/xunit

The xml result are generated correcty but show:

INFO: Processing JUnit
WARNING: All test reports are empty.
INFO: Check 'Failed Tests' threshold.
INFO: The total number of tests for the threshold 'Failed Tests' exceeds the specified "failure threshold" value.
INFO: Setting the build status to FAILURE
Build step 'Publish xUnit test result report' changed build result to FAILURE
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE

Rollback to 2.4.0 works correctly.

What is happening to fail with xunit 3.0.2?

Regards,

Cesar Jorge

You can delete the xunit 3.x from the available plugins until this critical bug is fixed?

Regards,

Cesar Jorge

no, I never do that.

The bug is critical only if you produce reports sometimes and do not update is an acceptable workaround since there is not automatic update.

Other workaround is put an empty test case result

Uhm, the workaround is that always put one file empty?

But all my tests always write the results all found:

"Ficheros XML con los informes de tests" => tests/results/features.TS04_flow.002.xml

workspace]$ ls -l tests/results/features.TS04_flow*
rw-r---- 1 jenkins jenkins 75839 abr 21 16:09 tests/results/features.TS04_flow.002.xml

Sorry my bad.

The "Skip if there are no test files" means do not throw error is there are not test files at all. If there are test files but empty (suite should have at least 1 test) than threashold is considered.

I followed your steps using JUnit and it works. This is the output of XUnit (3.0.2):

Running as SYSTEM
Compilazione in corso nello spazio di lavoro D:\git\xunit-plugin\work\workspace\test
INFO: Processing JUnit
INFO: [JUnit] - No test report file(s) were found with the pattern '**/*' relative to 'D:\git\xunit-plugin\work\workspace\test' for the testing framework 'JUnit'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'JUnit'?"
WARNING: All test reports are empty.
INFO: Check 'Failed Tests' threshold.
INFO: Setting the build status to SUCCESS
Finished: SUCCESS

[ nfalco

We had to downgrade and use 2.4.0. I am in the process of upgrading Jenkins, and thought I'd give 3.0.2 a chance. Having the same issue. Please note: there are NO files found (they are not just empty files). Why does it complain about no files being found and then files are empty? Can you check it with custom-tool as well, please? We will have to stay on 2.4.0 but I'm not sure how long that is feasable.

INFO: Processing Custom Tool
INFO: [Custom Tool] - No test report file(s) were found with the pattern 'dev/bin/vnv/mod/tests/**/utf*.xml' relative to 'T:\' for the testing framework 'Custom Tool'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'Custom Tool'?"
WARNING: All test reports are empty.
INFO: Check 'Failed Tests' threshold.
INFO: The total number of tests for the threshold 'Failed Tests' exceeds the specified "failure threshold" value.
INFO: Setting the build status to FAILURE

skhushalani I need the job configuration

You can remove skipped threashold it is empty.

I have copy you exact configuration and locally it does not fails. the failed threashold return SUCCESS