As it stands for Gradle projects we can generate tests, but we will have to manually modify the build.gradle file in the given gradle project in order to add the EvoSuite dependency (as shown in testgeneration/init.gradle), so that they could be run with gradle test command (for profiling). For Maven projects the pom is updated programmatically. Theoretically one could use FileWriter to do this task for Gradle, but it would be much nicer to do this programmatically and it seems like wtih gradle tooling api version 6.6.1 it would be possible, hence I am not implementing the FileWriter hack. However, currently updating the tooling dependency breaks a Gin test, so perhaps it's best to put this issue on hold until we are ready for a general upgrade of dependencies.
As it stands for Gradle projects we can generate tests, but we will have to manually modify the build.gradle file in the given gradle project in order to add the EvoSuite dependency (as shown in testgeneration/init.gradle), so that they could be run with gradle test command (for profiling). For Maven projects the pom is updated programmatically. Theoretically one could use FileWriter to do this task for Gradle, but it would be much nicer to do this programmatically and it seems like wtih gradle tooling api version 6.6.1 it would be possible, hence I am not implementing the FileWriter hack. However, currently updating the tooling dependency breaks a Gin test, so perhaps it's best to put this issue on hold until we are ready for a general upgrade of dependencies.