This framework is for testing the toDex part of Soot (develop branch). For a detailed description (in german) see the master thesis Generating and testing Dalvik bytecode for Android. In short, the framework reads Android apps (as .apk files), converts them, and uses the Android emulator to test the converted app. To eliminate testing non-working apps, the untouched .apk file is run on the emulator beforehand. See this blog post for the general usage of Soot's Android capabilities.
The repo is a ready-to-use eclipse project (which expects Soot with the toDex part in the workspace). First, you have to implement the interface os.OperatingSystem and use it in the os.Commands.OS variable. See os.ExampleOS for details - it defines certain OS specific paths for external tools from the JDK or Android SDK.
The framework expects exactly one working Android emulator running. You can check if this is the case with "adb devices" on your command line. Given that, you should supply the main method in main.MainTesting with the path to the .apk you want to test. The framework produces messages on the Console to keep you informed. These messages are also saved in a log file at logs/messages.log. You can also run multiple APKs by providing multiple paths to the main method (no spaces, sorry). To see a summary of all the tests you ran, see logs/summary.log for a log file with one line per test.
If you do not provide any arguments to the main method, the framework will test the APKs in the "fdroid" folder of the project. These should originate from the F-Droid repository and were used during the framework's initial development. Note that some APKs are excluded from testing due to known failures (see fdroid.KnownFailures for details). To get all the current APKs in the repo, you could utilize the class fdroid.IndexXmlParser. Call its main method to get an URL list of all the latest apps in that repository.
In the package fuzzing, you will find a prototypical IntConstantFuzzer. This is to show how one could use the framework for fuzzing the "toDex" part or Android's virtual machine with Soot's output. The simple IntConstantFuzzer changes at most one integer constant in the original APK to zero. To enable fuzzing as a third step in the test framework, see the TODO in main.MainTesting.
To run an Android app, its APK has to be signed. The test framework uses the file debug.keystore as a source for the private key needed for signing. The file includes the private key "release_me", which is protected by the keystore's password "debugNotWork", which you can deliberately see in the source code of the method os.Commands.sign(Path). So, if anybody finds that key here on github: I'm OK with that ;)