botsing-1.0.7

Release for the SSBSE 2019 tutorial on crash reproduction with Botsing.

botsing-1.0.6

Botsing-maven now executes botsing-preprocessing to clean the stack trace before executing botsing-reproduction (#85). See the Maven plugin documentation.

botsing-1.0.5

New features:

• Fixing Maven plugin for crash reproduction (see #83)

botsing-1.0.4

New features:

• Stack trace preprocessing (see #60) - See https://github.com/STAMP-project/botsing#botsing-preprocessing for documentation
• Behavioral model generator (see #36 and #37) - See the tutorial at https://github.com/STAMP-project/evosuite-model-seeding-tutorial
• Botsing crash reproduction Maven plugin (see #54)

Bugs fixed and other enhancements:

• Fixing bug in crossover operator (see #49)
• Fixing bug in guided mutation (see 8bbcf81)
• Refactoring classpath handling (see #63)

botsing-1.0.3

Fixing issues with Shading

botsing-1.0.2

Adding shading for dependencies to avoid classpath conflicts between the software under test dependencies and Botsing dependencies.

botsing-1.0.1

Minor release with bug fixes.

Botsing 1.0.0

Includes crash reproduction with weighted sum scalarization fitness function and simplified command line usage.

Command line interface

Botsing has three mandatory parameters:

• -crash_log the file with the stacktrace. The stacktrace should be clean and cannot contain any nested exceptions.
• -target_frame the target frame to reproduce. This number should be between 1 and the number of frames in the stacktrace.
• -projectCP the classpath of the project and all its dependencies. The classpath can be a folder containing all the required .jar files.

By default, Botsing uses the following parameter values:

• -Dsearch_budget=1800, a time budget of 30 min. This value can be modified by specifying an additional parameter in format -Dsearch_budget=60 (here, for 60 seconds).
• -Dpopulation=100, a default population with 100 individuals. This value may be modified using -Dpopulation=10 (here, for 10 individuals).
• -Dtest_dir=crash-reproduction-tests, the output directory where the tests will be created (if any test is generated). This value may be modified using -Dtest_dir=newoutputdir.

To check the list of options, use:

$ java -jar botsing-reproduction.jar -help
usage: java -jar botsing-reproduction.jar -crash_log stacktrace.log -target_frame 2
            -projectCP dep1.jar;dep2.jar  )
 -crash_log <arg>      File with the stack trace
 -D <property=value>   use value for given property
 -help                 Prints this help message.
 -projectCP <arg>      classpath of the project under test and all its
                       dependencies
 -target_frame <arg>   Level of the target frame

Example

java -jar botsing-reproduction.jar -crash_log LANG-1b.log -target_frame 2 -projectCP ~/bin