Currently CrashTestCase is only used by Chrome, and therefore uses the constant CrashFileManager.CRASH_DUMP_DIR to determine where to store minidumps.

For WebView we will want to use a different directory (or a sub-directory) to store Minidumps (so that the Chrome, and WebView upload mechanisms don't clash).

We could either pass a different 'cache dir' to CrashFileManager from WebView, or we could remake CrashFileManager to take an additional parameter being the crash sub-directory.

Either way, it would be nice to be able to use the test utility CrashTestCase for WebView-specific tests as well - but then we need to set the correct crash directory during CrashTestCase.setUp().
One way to do this is having CrashTestCase be overridable to use a different crash directory (i.e. 

CrashTestCase {
  setup() {
    mCrashDir = getCrashDir();
  }
}

and then create a WebView-specific CrashTestCase.