From 43594a08d4fdc3d37208a2c201443b514fbc5393 Mon Sep 17 00:00:00 2001 From: Metabase Docs bot Date: Fri, 1 Aug 2025 11:33:53 +0000 Subject: [PATCH] [auto] adding content to backport-55-00ceb1aff2575e93d00f9eea058e0271c0925b06->release-x.55.x --- _docs/latest/developers-guide/e2e-tests.md | 16 +++++++++------- _docs/v0.55/developers-guide/e2e-tests.md | 16 +++++++++------- .../docs/latest/developers-guide/e2e-tests.html | 15 +++++++++------ _site/docs/v0.55/developers-guide/e2e-tests.html | 15 +++++++++------ 4 files changed, 36 insertions(+), 26 deletions(-) diff --git a/_docs/latest/developers-guide/e2e-tests.md b/_docs/latest/developers-guide/e2e-tests.md index a2c61214cd..aff410c041 100644 --- a/_docs/latest/developers-guide/e2e-tests.md +++ b/_docs/latest/developers-guide/e2e-tests.md @@ -266,15 +266,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! diff --git a/_docs/v0.55/developers-guide/e2e-tests.md b/_docs/v0.55/developers-guide/e2e-tests.md index 4e294acaf6..714050b06d 100644 --- a/_docs/v0.55/developers-guide/e2e-tests.md +++ b/_docs/v0.55/developers-guide/e2e-tests.md @@ -264,15 +264,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! diff --git a/_site/docs/latest/developers-guide/e2e-tests.html b/_site/docs/latest/developers-guide/e2e-tests.html index a686931cb8..13f49ca9f9 100644 --- a/_site/docs/latest/developers-guide/e2e-tests.html +++ b/_site/docs/latest/developers-guide/e2e-tests.html @@ -5028,16 +5028,19 @@

Running Cypre

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. (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:

-
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.

If you navigate to the /admin/settings/license page, the license input field should display the active token. Be careful when sharing screenshots!

diff --git a/_site/docs/v0.55/developers-guide/e2e-tests.html b/_site/docs/v0.55/developers-guide/e2e-tests.html index e7755a4ac0..be919bf5fb 100644 --- a/_site/docs/v0.55/developers-guide/e2e-tests.html +++ b/_site/docs/v0.55/developers-guide/e2e-tests.html @@ -5030,16 +5030,19 @@

Running Cypre

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. (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:

-
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.

If you navigate to the /admin/settings/license page, the license input field should display the active token. Be careful when sharing screenshots!