Solved
Test Execute Summary Report Incomplete
Hi We're currently using Test Execute to run our smoke tests everyday. We've use the /ExportSummary argument on the CLI for Test Execute and noticed that only the first KWT on a test item collect...
Forum Discussion
We have it configured to stop test item only. Which made the other tests run. we're exporting both MHT and summary and the MHT does have the 5 test items but the summary does not which is what we parse to push results to AzureDevOps for the Pass/Fail flag
TanyaYatskovska
Alumni
Alumnithanks for the help, tristaanogre!
wmtan01 could you please clarify if the issue still persists? It's unclear from your past reply.
Hi,
Sorry for the late response.
This is how we configured the test items:
Test Items - We run NAT|EU|LeadManagerProject Configuration
I believe this should still continue the tests.
Here's what the summary looks like and what the mht file looks like since we export both:
MHT File
Summary XML provided by /ExportSummary
Just an update on this. I'm currently in discussion with Customer Support from Smartbear about this issue.
The Customer Care Engineer was able to replicate the issue and was able to point that it was because we were calling Log.SaveResultsAs in the middle of a collection of test items. We do it after each test run to have faster feedback. He is still in discussion with developers as to why the Log.SaveResultsAs would interfere with the summary generation.
IS there any update on this? We looked at this same method but noticed the same behavior so we stopped.
