[auto] adding content to cypress-tokens-cleanup->master (#363)

Co-authored-by: Metabase Docs bot <[email protected]>

Author: github-automation-metabase

_docs/master/developers-guide/e2e-tests.md

@@ -223,15 +223,17 @@ Prior to running Cypress against Metabase® Enterprise Edition™, set `MB_EDITI
 
 **Enterprise instance will start without a premium token!**
 
-If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests. We achieve this by prefixing environment variables with `CYPRESS_`.
-You should provide two tokens that correspond to the `EE/PRO` self-hosted (all features enabled) and `STARTER` Cloud (no features enabled) Metabase plans. For more information, please see [Metabase pricing page](/pricing/). (note: only a few tests require the no features token)
+If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests.
+You should provide 4 tokens:
 
-- `CYPRESS_ALL_FEATURES_TOKEN`
-- `CYPRESS_NO_FEATURES_TOKEN`
+- MB_ALL_FEATURES_TOKEN: all feature enabled, including new feature not released yet to customers
+- MB_STARTER_CLOUD_TOKEN: only 'hosting' feature enabled to simulate the starter plan on cloud
+- MB_PRO_CLOUD_TOKEN: PRO features enabled + 'hosting' to simulate the pro plan on cloud
+- MB_PRO_SELF_HOSTED_TOKEN: PRO features but no 'hosting' to simulate the pro self-hosted plan
 
-```
-MB_EDITION=ee ENTERPRISE_TOKEN=xxxxxx yarn test-cypress
-```
+You can configure these via ENVs or via the `cypress.env.json` file (see `cypress.env.json.example` for an example).
+
+For more information, please see [Metabase pricing page](/pricing/).
 
 If you navigate to the `/admin/settings/license` page, the license input field should display the active token. Be careful when sharing screenshots!
 

_site/docs/master/developers-guide/e2e-tests.html

@@ -5019,16 +5019,19 @@ <h2 id="running-cypress-tests-against-metabase-enterprise-edition">Running Cypre
 
 <p><strong>Enterprise instance will start without a premium token!</strong></p>
 
-<p>If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests. We achieve this by prefixing environment variables with <code class="language-plaintext highlighter-rouge">CYPRESS_</code>.
-You should provide two tokens that correspond to the <code class="language-plaintext highlighter-rouge">EE/PRO</code> self-hosted (all features enabled) and <code class="language-plaintext highlighter-rouge">STARTER</code> Cloud (no features enabled) Metabase plans. For more information, please see <a href="/pricing/">Metabase pricing page</a>. (note: only a few tests require the no features token)</p>
+<p>If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests.
+You should provide 4 tokens:</p>
 
 <ul>
-  <li><code class="language-plaintext highlighter-rouge">CYPRESS_ALL_FEATURES_TOKEN</code></li>
-  <li><code class="language-plaintext highlighter-rouge">CYPRESS_NO_FEATURES_TOKEN</code></li>
+  <li>MB_ALL_FEATURES_TOKEN: all feature enabled, including new feature not released yet to customers</li>
+  <li>MB_STARTER_CLOUD_TOKEN: only ‘hosting’ feature enabled to simulate the starter plan on cloud</li>
+  <li>MB_PRO_CLOUD_TOKEN: PRO features enabled + ‘hosting’ to simulate the pro plan on cloud</li>
+  <li>MB_PRO_SELF_HOSTED_TOKEN: PRO features but no ‘hosting’ to simulate the pro self-hosted plan</li>
 </ul>
 
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>MB_EDITION=ee ENTERPRISE_TOKEN=xxxxxx yarn test-cypress
-</code></pre></div></div>
+<p>You can configure these via ENVs or via the <code class="language-plaintext highlighter-rouge">cypress.env.json</code> file (see <code class="language-plaintext highlighter-rouge">cypress.env.json.example</code> for an example).</p>
+
+<p>For more information, please see <a href="/pricing/">Metabase pricing page</a>.</p>
 
 <p>If you navigate to the <code class="language-plaintext highlighter-rouge">/admin/settings/license</code> page, the license input field should display the active token. Be careful when sharing screenshots!</p>