Improving Publish Test Results action

[gntpet]

Hey @freddydk ,

I been recently playing with improving publish-unit-test-result-action from this repo. There are more actions, doing the similar stuff. I chose to picked repo from EnricoMi, since it's allowed within our enterprise organization.

It has some advantages over AL-GO way of doing, since it's publishing it in more places:

I hade to make these two small changes in a pipeline: add required permissions & add new action

If I would like to implement this one, instead of standard Al-Go ones, what are my options? I don't want to loose system updates.

I also wonder if you considered using off the shelf actions for publish test results. What was the reason, you choose to build a custom one?

Best Regards,
Gintautas

[freddydk]

I will take this as requirement to the indirect template / customization functionality.
Microsoft cannot include 3rd party actions in AL-Go, but it would be nice to be able for partners to use other apps / actions in their repositories.

[gntpet]

There's one more idea that we would like to implement. It is to add notification steps (to Teams or Slack) for deployments and testresults. Can you take this requirement into account as well?

Is this template customization functionality planned already? any rough ETA?

[freddydk]

It is work in progress, but something that has been standing still for a while

#853

Hoping to have time to look more into this over the summer

[freddydk]

It is the next thing I will throw my attention to.

[KristofKlein]

I was looking into Allure Report the other day. That can collect the testresult and render them into a report, that it than can upload as a gitHub page. incl. history. I understrand MS does not want 3rd Party actions. Still this might be a path for the one or another... :)