move automated tests to testing app folder

Author: PoojaB26

docs/marketplace/creators-hub/submission-criteria.md

@@ -396,7 +396,7 @@ Stay tuned for an upcoming "style guide" we're publishing that goes into deeper
 - **Criteria:** Projects should include automated tests that verify core functionality and key user workflows. While not required for approval, this is strongly recommended for libraries and will positively impact visibility.
 - **Why It Matters:** Automated tests help ensure reliability, catch regressions, and demonstrate your commitment to quality. They also improve your item's visibility.
 - **What To Do:**
-    - **Add Integration Tests:** Use FlutterFlow's [automated testing](../../testing-deployment-publishing/testing/automated-tests.md) features to verify your item's core functionality.
+    - **Add Integration Tests:** Use FlutterFlow's [automated testing](../../testing-deployment-publishing/running-your-app/automated-tests.md) features to verify your item's core functionality.
     - **Test Key Workflows:** Focus on testing critical user paths and features that users will rely on.
     - **For Libraries:** Since libraries are often used as building blocks in larger applications, thorough testing is particularly important to:
         - Verify that Library Values are properly implemented

docs/resources/ui/widgets/widget-commonalities.md

@@ -172,7 +172,7 @@ Values beyond this range will push the widget outside the visible screen area.
 
 ## Add Testing Value Key
 
-A **Value Key** is used to uniquely identify widgets during [**Automated Testing**](../../../testing-deployment-publishing/testing/automated-tests.md) in FlutterFlow. For example, on a Create Account page, you might use descriptive keys like `signupFirstNameField`, `signupEmailField`, `signupPasswordField`, and `signupSubmitButton`. This helps testing tools reliably locate and interact with the correct widgets. For more details, refer to the [complete guide here](../../../testing-deployment-publishing/testing/automated-tests.md).
+A **Value Key** is used to uniquely identify widgets during [**Automated Testing**](../../../testing-deployment-publishing/running-your-app/automated-tests.md) in FlutterFlow. For example, on a Create Account page, you might use descriptive keys like `signupFirstNameField`, `signupEmailField`, `signupPasswordField`, and `signupSubmitButton`. This helps testing tools reliably locate and interact with the correct widgets. For more details, refer to the [complete guide here](../../../testing-deployment-publishing/running-your-app/automated-tests.md).
 
 ![test-value-keys.avif](imgs/test-value-keys.avif)
 

docs/testing-deployment-publishing/publishing/pre-checks-publishing.md

@@ -13,7 +13,7 @@ This page outlines the important steps and checks to be made before publishing y
 
 Here’s a comprehensive list of these prechecks:
 
-1. **Functionality Testing**: Test the app manually across devices. You can also implement integration tests using FlutterFlow’s [**Automated Tests**](../testing/automated-tests.md) framework to cover various scenarios.
+1. **Functionality Testing**: Test the app manually across devices. You can also implement integration tests using FlutterFlow’s [**Automated Tests**](../running-your-app/automated-tests.md) framework to cover various scenarios.
 
 2. **Get Feedback**: Run your app in Run Mode to generate a shareable link to the session. You can share these links to gather feedback from users and testers, providing valuable insights and potential areas of improvement before the public release.
 3. **Optimizations & Enhancements**: Improve performance by implementing [optimization and enhancement](../../intro/ff-ui/toolbar.md#project-suggestions) suggestions. Ensure that images are properly sized, consider using higher compression for assets, and remove unused assets and custom widgets. These will help improve your app's speed and size.

docs/testing-deployment-publishing/running-your-app/_category_.json

@@ -1,4 +1,4 @@
 {
-    "label": "Running your App",
+    "label": "Testing your app",
     "position": 3
   }

…nt-publishing/testing/automated-tests.md …hing/running-your-app/automated-tests.mddocs/testing-deployment-publishing/testing/automated-tests.md renamed to docs/testing-deployment-publishing/running-your-app/automated-tests.md docs/testing-deployment-publishing/testing/automated-tests.md renamed to docs/testing-deployment-publishing/running-your-app/automated-tests.md

@@ -3,7 +3,7 @@ slug: /testing/automated-tests
 title: Automated Tests
 description: Discover how to effectively utilize automated testing in FlutterFlow to ensure your app performs as intended.
 tags: [Automated Tests, Testing]
-sidebar_position: 0
+sidebar_position: 2
 keywords: [Automated Tests, Testing, FlutterFlow]
 ---
 

docs/testing-deployment-publishing/testing/_category_.json

@@ -1,24 +1,22 @@
 
 .cardContainer {
-  padding-top: 20px;
-  display: grid;
-  grid-template-columns: repeat(auto-fit, minmax(300px, 1fr));
-  grid-auto-rows: 1fr;
-  gap: 24px;
-  width: 100%;
-  max-width: none;
-  margin: 0;
+    padding-top: 20px;
+    display: grid;
+    grid-template-columns: repeat(3, 1fr); /* Default to three columns */
+    grid-auto-rows: 1fr; /* Each row has equal height, adjusting to content */
+    gap: 20px;
 }
 
+
 /* Responsive adjustments */
-@media (max-width: 1024px) {
-  .cardContainer {
-    grid-template-columns: repeat(2, 1fr);
+@media (max-width: 1024px) { /* For tablets and smaller desktops */
+    .cardContainer {
+      grid-template-columns: repeat(2, 1fr); /* Two columns */
+    }
   }
+  
+@media (max-width: 768px) { /* For landscape phones and smaller tablets */
+.cardContainer {
+    grid-template-columns: 1fr; /* Single column for small devices */
 }
-
-@media (max-width: 768px) {
-  .cardContainer {
-    grid-template-columns: 1fr;
-  }
 }