From 7cde91fa55826c6b50f326da23f0cc72f0ad798e Mon Sep 17 00:00:00 2001 From: Ian VanSchooten Date: Wed, 27 Apr 2022 15:21:23 -0400 Subject: [PATCH 1/2] Document limitation for .mdx and .svelte stories --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 111a6eb9..15a773d1 100644 --- a/README.md +++ b/README.md @@ -147,7 +147,7 @@ yarn test-storybook --url https://the-storybook-url-here.com By default, the test runner transforms your story files into tests. It also supports a secondary "stories.json mode" which runs directly against your Storybook's `stories.json`, a static index of all the stories. -This is particularly useful for running against a deployed storybook because `stories.json` is guaranteed to be in sync with the Storybook you are testing. In the default, story file-based mode, your local story files may be out of sync--or you might not even have access to the source code. +This is particularly useful for running against a deployed storybook because `stories.json` is guaranteed to be in sync with the Storybook you are testing. In the default, story file-based mode, your local story files may be out of sync--or you might not even have access to the source code. Furthermore, it is not possible to run the test-runner directly against `.mdx` or `.svelte` stories, and stories.json mode must be used. To run in stories.json mode, first make sure your Storybook has a v3 `stories.json` file. You can navigate to: From 5ccece69daaea64dff1cee5a7db971f27ba23fa5 Mon Sep 17 00:00:00 2001 From: Ian VanSchooten Date: Wed, 27 Apr 2022 15:54:10 -0400 Subject: [PATCH 2/2] Just mdx --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 15a773d1..64e11d3a 100644 --- a/README.md +++ b/README.md @@ -147,7 +147,7 @@ yarn test-storybook --url https://the-storybook-url-here.com By default, the test runner transforms your story files into tests. It also supports a secondary "stories.json mode" which runs directly against your Storybook's `stories.json`, a static index of all the stories. -This is particularly useful for running against a deployed storybook because `stories.json` is guaranteed to be in sync with the Storybook you are testing. In the default, story file-based mode, your local story files may be out of sync--or you might not even have access to the source code. Furthermore, it is not possible to run the test-runner directly against `.mdx` or `.svelte` stories, and stories.json mode must be used. +This is particularly useful for running against a deployed storybook because `stories.json` is guaranteed to be in sync with the Storybook you are testing. In the default, story file-based mode, your local story files may be out of sync--or you might not even have access to the source code. Furthermore, it is not possible to run the test-runner directly against `.mdx` stories, and stories.json mode must be used. To run in stories.json mode, first make sure your Storybook has a v3 `stories.json` file. You can navigate to: