Hi,
Currently iteration names in Total Request Tab have same name which is very difficult to identify the intended Test API call. I am just trying to find is there anyway we can change or append name to iteration like Iteration: 1 - - < TestName> .
I am seeing this issue when I create a collection with only one parameterized request where URI and reqestBody read from the data file.
Appreciate your help and guidance to resolve this issue.
As this is quite a specific question relating to a particular project - Could you raise an issue on the GH repo, using the template to add all the relevant details, please?
I will then be able to help you get to the bottom of the problem you’re facing and hopefully we can come up with a solution together.
The htmlextra reporter is awesome. Just a small question about it. Is it possible to increment the iteration number in the final report? Every time an endpoint is called with different set of test data, can we increased the number instead by showing “Iteration 1” ? In the screenshot, i called the same endpoint 3 times with different set of test data, but “Iteration 1” is shown in all of them. It would be nice if we can show
Btw, im not using the built in functionality of postman by implementing data files for data-driven testing because my requirement is different. But I have an environment variable for the test datas and i am looping through it and using the postman.setNextRequest to control the execution.
That’s all being done in the same iteration so that’s why it’s creating the report like that. You’re just looping through a request several times, within the same iteration.
You would see the same on every reporter, it’s not specifically htmlextra. I can only show things based on the data being returned by the Newman run.
Another question though. Can we change the iteration number into something more meaningful? I am thinking of using the built in data files of postman. 1 iteration data will have a field called “scenarioDescription” eg. addANewTaxRate . Another iteration data will have a “scenarioDescription” of editExistingTaxRate and each of these iteration data will have its own endpoints which I need to chain together. For example, in the addANewTaxRate scenario, i will first call getExistingTaxRate and check the the new tax rate (that I am about to add) is not there yet, then call the add a new tax rate endpoint then call again the getExistingTaxRate to check if the new tax rate has been added.
So in the final report, i am looking at the meaningful scenarioDescription as iteration numbers instead of 1,2,3…