Austin Bingham

Have a look at #197 (which links to at least one of those papers!) for some earlier discussion about this. I *think* it's well within our grasp; the architecture should...

> Assuming that the program is divided or has a proper architecture then second order and higher order mutation would not be very beneficial This is interesting! Do you have...

I think I understand what you're saying, but I don't fully agree with the conclusions. If the system I'm testing consists of multiple components communicating via some protocol (over the...

> it will make the logic behind each mutation much more complex Won't the diffs tell us a lot about mutation similarity? My (perhaps naive) view of HOMs is that...

I’d like to put some work into this as I have time. I think an obvious first step is to update the WorkDB so that individual WorkItems can refer to...

Once this foundational infrastructure is in place, we need to think about the harder, higher-level problems. How will we decide which higher-order mutations to do? We currently don’t have any...

This is a good idea, and it's a subset of larger principles we've discussed in other issues, e.g. #85 and #484. The best way to do it is with [a...

> I would very much like to add support for such a feature to cosmic ray So again, I would recommend a filter. You can define whatever relationship you want...

> I'm not clear on how to use the filter for limiting the tests to execute for each mutation Ah, I see. I was reading this incorrectly. As you say,...

Related to this (and what I was initially thinking about) is that filters can let you skip mutations to locations that don't need to be mutated. That is, if you've...