ENG-540: split content of testing-your-assistant.mdx docs

CHANGELOG.mdx

@@ -2788,9 +2788,9 @@ Upgrade dependent libraries with security vulnerabilities (Pillow, TensorFlow, u
 
 - [#6285](https://github.com/rasahq/rasa/issues/6285): Predictions of the [`FallbackClassifier`](./building-classic-assistants/components.mdx#fallbackclassifier) are
   ignored when
-  [evaluating the NLU model](./production/testing-your-assistant.mdx#evaluating-an-nlu-model)
+  [evaluating the NLU model](./building-classic-assistants/testing-your-assistant.mdx#evaluating-an-nlu-model)
   Note that the `FallbackClassifier` predictions still apply to
-  [test stories](./production/testing-your-assistant.mdx#writing-test-stories).
+  [test stories](./building-classic-assistants/testing-your-assistant.mdx#writing-test-stories).
 - [#6474](https://github.com/rasahq/rasa/issues/6474): Adapt the training data reader and emulator for wit.ai to their latest format.
 - [#6498](https://github.com/rasahq/rasa/issues/6498): Adding configurable prefixes to Redis [Tracker](./production/tracker-stores.mdx) and [Lock Stores](./production/lock-stores.mdx) so that a single Redis instance (and logical DB) can support multiple conversation trackers and locks.
   By default, conversations will be prefixed with `tracker:...` and all locks prefixed with `lock:...`. Additionally, you can add an alphanumeric-only `prefix: value` in `endpoints.yml` such that keys in redis will take the form `value:tracker:...` and `value:lock:...` respectively.
@@ -4164,7 +4164,7 @@ This can help to fix problems when using `rasa shell` with custom actions which
 
 ### Improved Documentation
 
-- [#2237](https://github.com/rasahq/rasa/issues/2237): Restructure the “Evaluating models” documentation page and rename this page to [Testing Your Assistant](./production/testing-your-assistant.mdx).
+- [#2237](https://github.com/rasahq/rasa/issues/2237): Restructure the “Evaluating models” documentation page and rename this page to [Testing Your Assistant](./building-classic-assistants/testing-your-assistant.mdx).
 
 - [#5302](https://github.com/rasahq/rasa/issues/5302): Improved documentation on how to build and deploy an action server image for use on other servers such as Rasa X deployments.
 

docs/docs/building-classic-assistants/glossary.mdx

@@ -40,7 +40,7 @@ A way to store bot responses externally instead of including them directly in th
 
 The process of using user messages and conversation data to influence the design of an assistant and train the model, combined with engineering best practices. There are 6 steps that make up CDD: Share, Review, Annotate, Fix, Track, and Test.
 
-## [Conversation Tests](../production/testing-your-assistant.mdx)
+## [Conversation Tests](./testing-your-assistant.mdx)
 
 Modified story format that includes the full text of the user message in addition to the intent label. Test conversations are saved to a test set file (conversation_tests.md), which is used to evaluate the model’s predictions across an entire conversation.
 

docs/docs/building-classic-assistants/stories.mdx

@@ -200,7 +200,7 @@ Overusing OR statements will slow down training.
 ## Test Conversation Format
 
 The test conversation format is a format that combines both NLU data and stories
-into a single file for evaluation. Read more about this format in [Testing Your Assistant](../production/testing-your-assistant.mdx).
+into a single file for evaluation. Read more about this format in [Testing Your Assistant](./testing-your-assistant.mdx).
 
 :::caution testing only
 This format is only used for testing and cannot be used for training.