iamsanjay commented on PR #2487: URL: https://github.com/apache/solr/pull/2487#issuecomment-2138627916
+1 Knowing test history would empower (old/**new**) Devs to make better decision. For instance, I observed that lots of build failed due to the flaky test cases, and I did not even knew about this URL before David shared it with me. Research on this: As per one survey participants were asked what information or tools would be most helpful to them in order to better handle flaky test cases, from University of Passau, ([Martin and Gordon, 2022](https://arxiv.org/abs/2203.00483)). > We observe a significant demand for improved visualization of flakiness. They specifically request tools to display test result histories, with comments such as, "We run tests so often, I often miss the bigger picture", and a desire for "a tool to visualize how tests fail and succeed over time" Additionally, they emphasize that such a tool should include meta-information like "on which device/environment [the test was executed] The second most commonly stated wish asks for tools that can automatically detect flaky test. And that's I proposed before as well and you have told me to share it on dev mailing list. I will do it! https://arxiv.org/abs/2203.00483 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
