commit 2d13fdb81b2e4151e7c7ac124801ed532abc00c8
author ilist <ilist@google.com> Fri Mar 05 05:42:56 2021 -0800
committer Copybara-Service <copybara-worker@google.com> Fri Mar 05 05:43:55 2021 -0800
tree c65414cf9e5f3ca9224ee447e61c1d00ab25493f
parent 4928295b236ec8f590a7e9d863502bc2f50a77d9

Provide mechanism to use "data" attribute in Bazel tests.

When supplying artifacts with "data" to Bazel tests, the file (for example tools/dir/file) is located in runfiles/sandbox at "../io_bazel/" (so in ../io_bazel/tools/dir/file). For purpose of mocking one needs to copy file from there to root dir (creating tools/dir/file).

PiperOrigin-RevId: 361126904

src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java

diff --git a/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java b/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java
index 5a48234..ca980cc 100644
--- a/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java
+++ b/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java
@@ -67,6 +67,9 @@
   /** Location of the bazel repo relative to the workspace root */
   public static final String BAZEL_REPO_PATH = "";
 
+  /** The file path in which to create files so that they end up under Bazel main repository. */
+  public static final String BAZEL_REPO_SCRATCH = "../io_bazel/";
+
   /** Relative path to the {@code process-wrapper} tool. */
   public static final String PROCESS_WRAPPER_PATH =
       "io_bazel/src/main/tools/process-wrapper";