The plugin should print info level logs on what it uses as inputs so the user can identify what is being used for inspection at a glance.

For example:

Source root:
  /src/main/java/
  /src/test/java/

Target classpath:
  /build/classes/test/

Source classspath:
  /build/classes/main/
  /build/classes/test/

tests/android-app-library
|- app/src/main/
|- app/src/instrumentTest
|- lib/src/main
|- lib/src/instrumentTest

Demonstrates how to properly configure stalker for a multi-project setup Android project.

• androidDefault()
• javaDefault()
• groovyDefault()

Example:

apply plugin: 'android'
apply plugin: 'stalker'

stalker {
  androidDefault()
  srcRoot 'my/other/android/path'
  srcClasspath 'my/cool/classpath'
  targetClasspath 'my/cool/target'
}

Instead of using the Exec task, use JGit for tighter integration with Git SCM

Instead of having the user configure srcRoot and srcClassPath manually, those options should be overrides.

The defaults should be detected based on what plugin was applied:

apply plugin: 'java'
apply plugin: 'stalker'

Should generate:

stalk {
    srcRoot "src/main/java"
    srcRoot "src/test/java"
    srcClassPath "$buildDir/classes/main"
    srcClassPath "$buildDir/classes/test"
    targetClassPath "$buildDir/classes/test"
}

This way, the typical user only needs to apply the plugin and it "just works."

Usages task assumes .java file extension

Or at least give an option to do so.

It feels weird to commit changes every time you want to trigger stalker, and it does not guarantee that you commit on the green (yeah, you can rebase, but... really?).

I plan on using this plugin in combination with (our test plugin)[https://github.com/novoda/gradle-android-test-plugin]. Using gradle -Dtest.single= for running single unit tests we might be able to do something that resembles TDD on Android.

👍 keep up the good work

A simple project with app code and instrument tests

tests/android
|- src/main
|- src/instrumentTest

When applying the plugin, it should assign some reasonable defaults for its configuration if it detects other plugins being applied, for example:

• apply plugin: 'java'
• apply plugin: 'android'
• apply plugin: 'android-library'

Sample project for an Android library

tests/android-library
|- src/main/
|- src/instrumentTest

Detect if a class depends on one of the affected classes and follow the dependency trail.

• interface I changes
• class A implements interface I
• test class B tests class A

B is the affected class in the target classpath

Follow the reverse inheritance chain

And keep it up to date ;)

When I follow the instruction on the README I get the error Could not find method srcClassPath() for arguments "$buildDir/classes/main". Your sample test-projects contradicts the README specifying ""${buildDir}/classes/main" both for srcClassPath and targetClassPath, I'm not sure if that's what you want.

Anyway, if you can use Maven snapshots instead of maven local at least we can try your nightly builds

Like the standard check task, Stalker should also add its own check task that selectively runs tests it detects to have been affected by code changes from stalk.