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
It would be great that, given a test method, an input amplifier is able to compute how many test methods it will produce.
The challenge in this issue is to not the loose performance and not do twice the same thing, e.g. getting all the literal that could be modified by the AllLiteralAmplifiers
This will be the first step for optimization on Budgetizer: ask the exact number of test methods to produce instead of generating all of them and then reduce them.
The text was updated successfully, but these errors were encountered:
Hi @deeplus, You can have a look at this maybe. It will allow you to go through different input amplifiers and input budgetizers without necessarily need to know every piece of DSpot.
It would be great that, given a test method, an input amplifier is able to compute how many test methods it will produce.
The challenge in this issue is to not the loose performance and not do twice the same thing, e.g. getting all the literal that could be modified by the
AllLiteralAmplifiers
This will be the first step for optimization on Budgetizer: ask the exact number of test methods to produce instead of generating all of them and then reduce them.
The text was updated successfully, but these errors were encountered: