Alcotest: finding flaky OCaml tests with JUnit reports

I use Alcotest and dune-release for almost every OCaml package I release: the first runs the tests, and the second publishes the result on opam. Both had collected issues and pull requests over the years (the oldest issue I closed this week dates from 2017), so I spent the past week going through them. Alcotest 1.10.0 and dune-release 2.3.0 are the result. For me, the most useful changes are that Alcotest can now write JUnit reports without any change to your tests, and that tests can carry tags. A tool that reads a folder of reports can tell a flaky test from a broken one, and a tag then puts the flaky test aside until it is fixed. dune-release 2.3.0 is on opam, and Alcotest 1.10.0 is about to be. The opam-repository CI shows failures in packages that depend on it, which I want to triage properly first. Testing it before then is very welcome, with a pin: $ opam update $ opam install dune-release $ opam pin add -n https://github.com/mirage/alcotest.git#1.10.0 $ opam install alcotest…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town