Provider postman run: Incorrect HTML-log output?

[alextreme]

Bug

Raised by @HenriKorver

I've started a Demo API run and this succeeds and all calls are green:

https://vng-staging.maykin.nl/server/ed9664ef-bec9-4e08-af3c-cae60599f815/

However when checking the HTML output it shows that requests have failed:

https://vng-staging.maykin.nl/server/ed9664ef-bec9-4e08-af3c-cae60599f815/log/

This was done using the following URL: https://ref.tst.vng.cloud/demo-api/api/v2

I'm not sure which of the two is correct. Perhaps something has changed in how we call newman?

[HenriKorver]

I want to show the HTML output in the demo coming Thursday. So it would be nice if this could be fixed no later than tomorrow, but even better today

[AlviseSembenico]

Problem is addressed here https://github.com/VNG-Realisatie/api-test-platform-code/pull/59

[HenriKorver]

Where can I see the fix? Test server (https://vng-test.maykin.nl) gives 401 Authorization Required

[AlviseSembenico]

I am upgrading stage right now

[AlviseSembenico]

It is now updated, You have to rerun the test though

[HenriKorver]

I get this error:

[AlviseSembenico]

The current update should fix the problem.

[HenriKorver]

Where can I test the fix?

[AlviseSembenico]

It is now released on staging, https://vng-staging.maykin.nl/server/80dfa5d9-4309-459b-b609-a48704352bce/ here the example

[HenriKorver]

Super cool!!!!! Will this also be rolled out to the production server (api-test.nl)?

[AlviseSembenico]

Sure Henri! I will be deployed on api-test as well

[HenriKorver]

Today? So I can show it tomorrow on the production version

[AlviseSembenico]

It has been already deployed.

[alextreme]

Currently verifying this on production after doing the deploy.

I do get errors from the ZGW & Demo APIs, but the newman reports are being generated again and the two outputs (JSON and HTML) are more in line with each other.

[HenriKorver]

It worked during the live demo and thus I was very happy