This issue has now been resolved following an update to the Azure Load Environment via product team.
Azure Load Testing Preview - Load Tests Return 'Not Applicable' Failed status despite showing as successful in Exported Result Files & AppInsights
We are currently running a POC on the new Azure Load Testing feature (currently in preview) as a resource to run our jMeter tests against an in development API.
Unfortunately we are hitting a few problems with the output results displayed within a test run, namely the tests always fail with no start, end and duration time along with a 'Not Applicable' status when running against the APIs despite all tests running successfully directly within the jMeter GUI. The same tests when run in the Azure Load Testing tool also appear to show as 'Passed' when exporting results from the test screen.
Has anyone experienced this before and would be able to help, as this tool could be exactly what we are looking for if we can get it to output the correct results.
Our jMeter test is fairly simple and obtains a validation token which is used in the latter request, I have manually verified this is all authenticating correctly and the variables we are using in these tests are being correctly populated when run in Azure.
See attached screenshots:
Test Result
Exported Result
We have also attempted to use the 'Ultimate Thread Group' plugin following a suggestion on StackOverflow, but unfortunately this also appears to return the same results (passes when run locally or through Blazemeter) but returns no result in Azure Load Testing despite the requests returning a successful result in AppInsights.
If anyone would be able to help at all this would be greatly appreciated. Unfortunately at the moment this is preventing us from reccomending Azure as a tool for our upcoming Load Testing strategy.
Community Center Not monitored
2 answers
Sort by: Most helpful
-
-
Monalla-MSFT 13,071 Reputation points Moderator
2022-01-27T23:01:55.897+00:00 @Chris Tyler - Thanks for patiently working with us offline in the GitHub Repo,
After looking at the test results you sent us, we figured that we have fixed those issues in the last couple of weeks.
and when asked to run the test again, you confirmed that the tests are passing now and displaying full test results.
Hope that helped resolve your issue.
---------------------------------------------
If the above response was helpful, please feel free to "Accept as Answer" and "upvote" so it can be beneficial to the community.