Add standaline_test to prove remote test execution

Author: martin4861

.github/workflows/ci.yaml

@@ -29,5 +29,8 @@ jobs:
           username: ${{ secrets.GH_NAME }}
           password: ${{ secrets.GH_TOKEN }}
 
-      - name: Build and test
+      - name: Build
         run: bazel build --remote_header=x-buildbuddy-api-key=${{ secrets.BUILDBUDDY_TEST }} --remote_executor=grpcs://remote.buildbuddy.io --config=rbe //...
+      
+      - name: Test
+        run: bazel test --remote_header=x-buildbuddy-api-key=${{ secrets.BUILDBUDDY_TEST }} --remote_executor=grpcs://remote.buildbuddy.io --config=rbe //:standalone_test

BUILD.bazel

@@ -530,6 +530,16 @@ test_suite(
     ],
 )
 
+swift_cc_test(
+    name = "standalone_test",
+    srcs = ["tests/standalone_test.cc"],
+    includes = ["tests"],
+    local_defines = ["CSV_IO_NO_THREAD"],
+    type = UNIT,
+    deps = ["@gtest//:gtest_main"],
+    standard=17,
+)
+
 platform(
     name = "docker_image_platform",
     constraint_values = [

tests/standalone_test.cc

@@ -0,0 +1,5 @@
+#include <gtest/gtest.h>
+
+TEST(StandaloneTest, SampleTest) {
+    EXPECT_EQ(1 + 1, 2);
+}