I'm thinking then one could also write a task that checked the deps of a project for tested compatibility against a specific release.
On Friday, August 4, 2017 at 12:44:20 PM UTC-4, Josh Austin wrote: > > For an Elixir release regression testing tool we really wouldn't have to > run it except for when there was a new Elixir release candidate. I'm not > sure we'd need to trigger on each commit to elixir-lang/elixir. > > I wonder if you could build a mix task that could test against the latest > release candidate and upload the results to a central location. Then one > could opt-in by including that task in the Travis config. Maybe we wouldn't > get complete coverage exactly but it could be a nice way to ramp-up and > distribute the workload. > > On Wednesday, August 2, 2017 at 1:23:28 PM UTC-4, Josh Austin wrote: >> >> Any thoughts about building a regression testing tool for new Elixir >> releases? I'm thinking about something like cargobomb >> <https://github.com/rust-lang-nursery/cargobomb> which is used for Rust >> <https://www.rust-lang.org> release regression testing. >> >> Other cargobomb info: >> - blog post: https://brson.github.io/2017/07/10/how-rust-is-tested#s-ds >> - example report: >> http://cargobomb-reports.s3-website-us-west-1.amazonaws.com/nightly-2017-07-07/index.html >> >> I'm thinking having excellent tools like mix and hex.pm could enable >> something similar for Elixir. I'm interested in knowing your thoughts about >> this. >> >> Best, >> Josh Austin >> >> -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/bad3487d-a922-4071-8337-d7c8d787f7f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
