Allure Report Azure DevOps extension not generating appropriate Test body nor attaching any screenshots #2537
Unanswered
ciconq
asked this question in
Bug Reports
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I have reported this in an already opened bug(not by me and not specifying if it is for
Allure Report Azure DevOps extension
but I have decided to report it there in order not to create a separate bug) for screenshots generation but still haven't had any clear answer if this is already a known issue for over a month now so I decided to open a separate bug for better transparency as the already opened bug was a bit less descriptive.This is how I am currently seeing the
Test body
within a report inAzure DevOps
(actual result):As you can see the
Console Output
and theFailed screenshot
sections are missing and we just have theConsole Output
without any clear structure andunknown
strings against each row that was logged(as expectedunknown
should not be displayed).As well as the attached screenshot missing(using
AllureApi
to attach it).And this is how I was seeing the
Test body
within a reportAzure DevOps
at the end of March(expected result):Locally
everything is working as expected but not onAzure DevOps
. I have tried with all versions from2.25.0
up until latest2.29.0
.Currently the only way for this to work as expected on
Azure DevOps
is to have thebatchingBasedOnAgentsOption
andcustomBatchSizeValue
options specified in theVSTest@2
task which generates the expectedTest body
.Options:
This was previously working without specifying the
batchingBasedOnAgentsOption
andcustomBatchSizeValue
options.Just wanted to report this so it can be fixed when necessary.
Currently I will stick with the
batching
options above as it resolves the already known issue ofVSTest@2
task when rerunning failedNUnit
parameterized tests.Thank you for your time and attention!
Beta Was this translation helpful? Give feedback.
All reactions