title: How to run ProGuard on Android tests?
body: <p>We have a project with some library (and native) dependencies, like this:</p>
  
  <p>Native SDK &larr; Library (Wrapper) &larr; Main Project</p>
  
  <p>To start with, this structure <strong>cannot</strong> be changed, as we are reusing the parts. The problem I am facing is passing the 65k reference limit. This, of course, has a workaround - enable ProGuard. With it enabled, the project compiles. </p>
  
  <p>Since we are transitioning to the Android's default testing framework, we need to add some more dependencies to the testing config, so in dependencies we now have:</p>
  
  <pre><code>compile 'com.google.android.gms:play-services-base:7.5.0'
  compile 'com.google.android.gms:play-services-gcm:7.5.0'
  compile 'com.google.android.gms:play-services-safetynet:7.5.0'
  compile 'com.android.support:appcompat-v7:22.2.1'
  compile 'com.android.support:recyclerview-v7:22.2.1'
  
  compile files('libs/small-library1.jar')
  compile files('libs/small-library2.jar')
  compile files('libs/small-library3.jar')
  compile files('libs/medium-library1.jar')
  compile files('libs/medium-library2.jar')
  compile files('libs/medium-library3.jar')
  compile files('libs/huge-library1.jar')
  compile files('libs/huge-library2.jar')
  
  androidTestCompile 'com.android.support.test:runner:0.3'
  androidTestCompile 'com.android.support.test:rules:0.3'
  androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2'
  </code></pre>
  
  <p>We are using SDK (API) 22, so everything is pretty much at the latest version. The problem is, our native SDK has a bunch of code in the protobuf layer, and the library wrapper is big. With all other JARs, we are too high over the 65k limit (but as I said, ProGuard fixes this barely). Multi-dex is out of the question as it works well only on Android 5.0+.</p>
  
  <p>We're trying to reduce the codebase, but even then, Android Tests are failing with method reference overflow issues (i.e. not compiling). </p>
  
  <p>Is there any way to enable ProGuard for tests as well?</p>