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

Add Support for Relevant Classes #32

Closed
nmaguirre opened this issue Sep 26, 2014 · 0 comments
Closed

Add Support for Relevant Classes #32

nmaguirre opened this issue Sep 26, 2014 · 0 comments

Comments

@nmaguirre
Copy link
Collaborator

So far, Stryker has no support for relevant classes. As a consequence, the only relevant class to be considered for the repair is the class containing the method to repair.

Add support for relevant classes. Relevant classes are represented as a string, e.g.,

"examples.bintree.base.BinTree,examples.bintree.base.Node"

This issue involves the following tasks:

  • add an attribute to BasicProgramRepairer to hold the relevant classes. By default, relevantClasses only hold the class containing the method to fix.
  • add constructors to BasicProgramRepairer that enable the creation of instances by passing, besides other necessary parameters, the relevant classes. DO NOT REMOVE existing constructors; provide new ones.
  • add an attribute to StrykerRepairSearchProblem to hold the relevant classes. By default, relevantClasses only hold the class containing the method to fix.
  • add constructors to StrykerRepairSearchProblem that enable the creation of instances by passing, besides other necessary parameters, the relevant classes. DO NOT REMOVE existing constructors; provide new ones.
  • update method success in class StrykerRepairSearchProblem to pass relevant classes when calling TACO, when relevant classes are provided.
  • add command line options to RepairerCLI, to optionally provide relevant classes when calling Stryker from the command line.
  • add/update appropriate javadoc comments to modified/introduced routines and attributes.
  • add tests to verify that your modifications work as expected.
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

2 participants