I've just pushed some significant functionality from Muzak Pro into Muzak, which means that it's even easier for folks to work some mutation testing into their workflow and start seeing the benefits! Today I'm going to break down three ways that you might want to get started with that. »
It's fairly common for folks who haven't used mutation testing previously to not immediately see the value in the practice. Mutation testing is, after all, still a fairly niche and under-used tool in the average software development team's toolbox. So today I'm going to show a few specific types of relatively common problems that mutation testing is great at finding for us (and that humans are notoriously bad at finding). »
As of today, Muzak and Muzak Pro are live! If you follow me on twitter you may have seen some hints that I've been making some good progress recently on the mutation testing library that I've been working on for close to a year now, and I think things are in a good enough place to push up the first versions of both Muzak and Muzak Pro. »
I think it's fair to say that a good amount of folks - if not the majority of them - using Elixir in production today are doing so after migrating an application to Elixir from some other language instead of just building in Elixir from scratch. Of course this idea of re-writing an application is scary, and rightly so! But there are some ways to make this process simpler and less scary, and also to reduce the likelihood of introducing regressions during this process, and that's what I'm going to go over today. »
There are some nice new features coming in Elixir 1.11, and one many folks are excited about are some new compile-time checks. The one I've heard the most excitment about is the the compile-time check for non-existent fields in structs. »