:large_green_circle: :large_yellow_circle: :large_...

# random

[jendrik]

🟢 🟡 🟠 🔴

Are my tests flaky and how bad is it?
The Test Dashboard (by TestLens) answers these questions!

✏️ Read more in our blog: testlens.app/blog/…/test-dashboard
👀 See it in action: junit-team/junit-framework Test Dashboard>
🚀 Try TestLens yourself: github.com/marketplace/testlens-app

[Eugen Martynov]

Where test results info is stored? Is it in cloud service or GH artifacts?

[jendrik]

The test results are stored (by default for the last 90 days) on a server managed by us (TestLens GbR) located in Germany.

[Eugen Martynov]

Thanks! I was reading post and GH but it was not clear. Maybe should watch video first before asking the question.

[jendrik]

Well. Thanks for the feedback! That's indeed not very clear from the documentation/posts we currently have.

[Eugen Martynov]

Most pointing to GH

[jendrik]

The data is captured directly on the JUnit Framework level and sent directly to our server. GitHub "only" acts as the UI. So processed and selected data is sent back to GitHub as content of an issue description or a PR comment.
It is a GitHub-integrated product and currently only works for projects hosted on GitHub.

[Eugen Martynov]

Thinking loudly - not sure if there reliable and not harming the process way to hash test names and failure messages - so not the code sent to server but these hashes that will make it more acceptable for corporate clients.

[jendrik]

We'll have to see what concrete concerns are if it that is the blocker for someone to use TestLens.
Generally, if you want to use our product, which includes giving access rights to your GitHub account to our App to post comments, you need to be willing to share certain data with us.
If you are in a position to use cloud services, you already share data with other service providers – most prominently GitHub itself.

[jendrik]

Thanks for sharing your thoughts on this.

[Eugen Martynov]

Some people are using self hosted GH enterprise, and if I remember correctly GH actions are not provided there. But you're right - posting comments give access to source code already.

[jendrik]

We currently do not offer TestLens for self-hosted GitHub Enterprise. If we do support that in the future, I think it would only make sense if users could also host the TestLens backend themselves. And not have any data sharing issues. We may consider that in the future depending on how things work out.

[trevjones]

if github was a serious company this would have been built into their GHA ux years ago.

looks like they are slowly starting to add test coverage tracking though.

I really wish we could see a test and coverage integrated system. would be amazing to track coverage per test to then later fuel automatic test selection on hard data

[trevjones]

(pretty sure junit/gradle/jacoco as is can't track per test)

[Alexandru Caraus]

i use a gh action plugin, that reads attached jacoco and kover reports to show diff per pr/per file/ module

[Alexandru Caraus]

its oss so can be adapted probably to do the diff for a longer period

[Alexandru Caraus]

madrapps/jacoco-report is the gh actions plugin