You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While there are a number of mutations today for defining scenarios, we've found them unhelpful in some cases due to either being too trivial or too limiting. I'd like to propose a new run mutation that would act similar to git bisect run, where an arbitrary shell script + any arguments is given. This would be invoked before each iteration to apply a set of changes handled by the script.
One example where we would want to use this is to apply changes that would specifically change the dependency graph in a build profiling Dagger, such as adding a parameter to an injected class's constructor. This would give flexibility for scenario authors to profile specific cases unique to their build.
The text was updated successfully, but these errors were encountered:
While there are a number of mutations today for defining scenarios, we've found them unhelpful in some cases due to either being too trivial or too limiting. I'd like to propose a new
run
mutation that would act similar togit bisect run
, where an arbitrary shell script + any arguments is given. This would be invoked before each iteration to apply a set of changes handled by the script.One example where we would want to use this is to apply changes that would specifically change the dependency graph in a build profiling Dagger, such as adding a parameter to an injected class's constructor. This would give flexibility for scenario authors to profile specific cases unique to their build.
The text was updated successfully, but these errors were encountered: