From 69e964769f85ab473185fe47af27c9060e8850c2 Mon Sep 17 00:00:00 2001
From: Caroline McNamara <caroline.mcnamara@uk.ibm.com>
Date: Wed, 8 May 2024 14:23:48 +0100
Subject: [PATCH] add bootstrap prop for hybrid

---
 .../docs/writing-own-tests/running-test-modes.md     | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/src/markdown-pages/docs/writing-own-tests/running-test-modes.md b/src/markdown-pages/docs/writing-own-tests/running-test-modes.md
index 2389415f..7eb288c6 100644
--- a/src/markdown-pages/docs/writing-own-tests/running-test-modes.md
+++ b/src/markdown-pages/docs/writing-own-tests/running-test-modes.md
@@ -54,6 +54,18 @@ When you run a test locally, but using shared configuration, the Galasa bootstra
 
 ![running in local mode with shared configuration:](hybridrunmode.svg)
 
+To run tests in hybrid mode, add the following properties into your local `bootstrap.properties` file:
+
+```
+framework.config.store=galasacps://my.ecosystem.url/api
+framework.extra.bundles=dev.galasa.cps.rest
+```
+
+where: <br>
+- `galasacps://my.ecosystem.url/api` tells Galasa that `https://my.ecosystem.url/api` is the location of the Ecosystem REST API and <br>
+- `framework.extra.bundles` indicates that the Galasa framework should load the `dev.galasa.cps.rest` extension. This extension tells the Galasa framework how to handle URLs that start with `galasacps` as the *scheme* part of the URL. <br>
+
+
 After configuring authentication, you can run a test in hybrid mode by setting your bootstrap to refer to the Ecosystem in which the shared configuration is stored, and using the `runs submit local` <a href="https://github.com/galasa-dev/cli/blob/main/docs/generated/galasactl_runs_submit_local.md" target="_blank"> Galasa CLI</a> command. 
 
 ### <a name="whenremote"></a>When to run a test in the Galasa Ecosystem