Markus Zimmermann
Markus Zimmermann
Order should be 1. default values 2. config (if defined) 3. environment 4. direct CLI argument this should be implemented independent of the program so others can use it/the pattern...
To anyone who is reading this. i was a long time away from open source projects and have now a little more time on my hand. If you are interested...
If we do "go-mutesting --test-recursive some/package/..." we will go through every Go file and mutate it. The "--test-recursive" option here would maybe indicate to the user that we will run...
/example has a LOT of duplicate types of mutations. We only need a few here to handle the tests of /cmd/go-mutesting/main_test.go and to show some mutations to demonstrate go-mutesting in...
All cmd tests are simply looking at the statistic output, this is slightly problematic. All cmd tests should also compare the content of the generated mutations.
The mutation files should be generated using a Makefile target.
main.go is a mess. Everything that is not cmd argument related should be put into github.com/zimmski/go-mutesting. This would make it also possible to test a lot of functionality without need...
The migration to go/loader added a lot of execution time during testing. However, it also allows for a perfect type checking. We could at least remove some of the loading...
The AST should be cleaned from all comments, empty lines and odd formatting (i.e. usage of ";") before taking a checksum. This would lead a uniform coding style and could...
During IdentifiersInStatement we are reusing nodes which often leads to compile errors for the mutations. This for example happens if the node has comment or some position information attached to...