You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pm.test("StoryID:" + request.name + " Response status is 200", function () { pm.response.to.have.status(200); });
Then the launch / items remain in progress forever and no results are ever logged
When we switched to:
pm.test("StoryID: Response status is 200", function () { pm.response.to.have.status(200); });
Then it started working:
There were no logs... or helpful information to determine this problem, it took several days of trial and error to find this issue. The request.name function in Postman literally just inserts the name of the request being made. This is there to make the names of the tests unique to solve an issue with the Junit parser in Bamboo.
We have a choice of incorrect results in bamboo and it working in Report portal. Correct results in bamboo and no results in report portal, or hard coding a unique name in our test suite and both work, but we introduce bad practice. We also tried creating a unique name as a variable and then passing in the variable string to the test name... report portal didn't like that either.
The text was updated successfully, but these errors were encountered:
When running with tests in postman like this:
pm.test("StoryID:" + request.name + " Response status is 200", function () { pm.response.to.have.status(200); });
Then the launch / items remain in progress forever and no results are ever logged
When we switched to:
pm.test("StoryID: Response status is 200", function () { pm.response.to.have.status(200); });
Then it started working:
There were no logs... or helpful information to determine this problem, it took several days of trial and error to find this issue. The request.name function in Postman literally just inserts the name of the request being made. This is there to make the names of the tests unique to solve an issue with the Junit parser in Bamboo.
We have a choice of incorrect results in bamboo and it working in Report portal. Correct results in bamboo and no results in report portal, or hard coding a unique name in our test suite and both work, but we introduce bad practice. We also tried creating a unique name as a variable and then passing in the variable string to the test name... report portal didn't like that either.
The text was updated successfully, but these errors were encountered: