However, take in mind that the report is stored inside the Git repository as a note (it is invisible - and how other tools like Gerrit work) to avoid an external service.
I see, I skimmed over that section. Reason being, I expect to see __real__ reports for this topic as a product owner instead of mutable git notes that I would need to tool against. Git notes from my understanding are more for TODOs, and don't seem like the best output for test analysis.
Thank you for your commenst :) but let me ask a question: Why do you consider them mutable? They are related into a commit and they are stored into an specific ref (it is not the default for Git notes). Git notes are also used to store static code analysis results.
The tool could generate the report as a file, sure. But The problem is that you will need a service to retrieve that file and compare - and then it becomes a non generic solution.
Indeed, my question is what do you want to do with that file? It can generate it, but nobody will take benefit of it, right?
It really is subjective depending on your organization’s industry and contractual obligations, but from experience, testing artifacts are used for a number of business functions. If you’re working on something important, something that could be audited OR if you’re trying to prove basic compliancy (e.g., PCI compliance) or an ISO certification, then its required to provide static testing documentation.
Off the top of my head, I know that I can change a git note using add —force to change a note without caring about the commit. That’s why it’s mutable in a bad way.
5 comments
[ 3.5 ms ] story [ 24.4 ms ] threadHowever, take in mind that the report is stored inside the Git repository as a note (it is invisible - and how other tools like Gerrit work) to avoid an external service.
The tool could generate the report as a file, sure. But The problem is that you will need a service to retrieve that file and compare - and then it becomes a non generic solution.
Indeed, my question is what do you want to do with that file? It can generate it, but nobody will take benefit of it, right?
Off the top of my head, I know that I can change a git note using add —force to change a note without caring about the commit. That’s why it’s mutable in a bad way.