Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE: Budgetize Input amplification #471

Open
5 tasks
danglotb opened this issue Jul 16, 2018 · 1 comment
Open
5 tasks

FEATURE: Budgetize Input amplification #471

danglotb opened this issue Jul 16, 2018 · 1 comment

Comments

@danglotb
Copy link
Member

danglotb commented Jul 16, 2018

Characteristics

  • Issue Type: feature
  • Severity: feature, major

Description

Create a budget for the Input Amplification. Among the list of amplifiers, each of them gains a given amount of budget, e.g. a number of methods to produce. Then, we limit the input amplification according to this budget.

This aims at keeping diversity without wasting resources. In fact, each amplifier will produce the same amount of test methods that allows exploring each different path (path in a sense of exploration path, in the exploration space).

  • compute a budget
  • predict the consumption of amplifiers
  • stop the input amplification according to the budget
  • differentiate between random than hard-coded operators, because it is likely that we want to prioritize hard-coded operators rather than random

a side feature is:

  • unmark all amplified elements in case of all them have been amplified. However, we should only use random operators to keep doing the exploration.

Help is welcome

@danglotb
Copy link
Member Author

The budget implemented in #477 does not answer to this issue but implement another way.

For now, the SimpleBudgetizer selects a fair number for each Amplifier and each test methods to be amplified. The time consumption seems to be ok for now.

@danglotb danglotb removed their assignment Dec 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant