diff options
Diffstat (limited to '')
| -rw-r--r-- | bruiser/README.md | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/bruiser/README.md b/bruiser/README.md index 95a759a..3fef1f4 100644 --- a/bruiser/README.md +++ b/bruiser/README.md @@ -1,12 +1,14 @@ ## bruiser ### What is it? -First off let's start with concrete facts. bruiser is implemented as an interactive shell, you can ask it to list information regrading the source codes it is run on. Future implementation plans include mutating the code as you want it to, and the little feeature that gives bruiser it's name which is to look at the code and decide how to break it.<br/> +Bruiser is implemented as an interactive commandline interface. It features an embedded lua interpreter plus the history and auto-completion and suggestion features we have all come to expect from shell-like tools.<br/> +Regarding the actual functionality, it will feature non-blind selective mutations. You can ask it to list information regrading the source codes it is run on. The eventuality of this idea is to help with maintaining code or in giving the viewer an overview of the code. The final feature is the name-sale. It looks at the code and decides how to break it. For more explanation please read on.<br/> -### Why? -It's an interactive mutation tool, mutation has it's own uses like muation testing. It can give you some insight into the code-base you are maintaining.<br/> +### DSL? +bruiser has an embedded lua interpreter so nobody would have to deal with a new DSL.<br/> -### Implementation Ideas(Or bruiser Requirements if you will) -The analysis part can be handled by m0(mutator-lvl0), while bruiser consumes the report generated by m0. I'm leaning towards using the XML reoport mostly because of X-Path.<br/> -For the "getting to know the code" part we can do a feature extraction/categorization on the reports and then have some sort of a mutation database based on the results of running the mutants.<br/> -We need to have the makefile for the source code so we can build the mutants, fork them as a separate process(we don't want to crash bruiser), get the results and repeat. For that reason bruiser might be implented as a shell of some sort.<br/> +### Non-blind Selective mutation? +bruiser looks at your code, learns your code and then decides how to mutate your code. That's non-blind selective mutation.<br/> + +### How? +I'm going to wrire about it as soon as I get my thoughts organized. In the meantime you can look at the source code for some hints.<br/> |