diff --git a/astro.config.mjs b/astro.config.mjs index f12bb1dc..5f7e1aa7 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -121,7 +121,13 @@ export default defineConfig({ { label: 'Classical Test Case Editor', link: '/project/tests/classical-test-case-editor' }, { label: 'BDD Test Case Editor', link: '/project/tests/bdd-test-case-editor' }, { label: 'Converting to BDD', link: '/project/tests/converting-to-bdd' }, - { label: 'Copy and Move your Tests', link: '/project/tests/copy-and-move-your-tests' }, + { label: 'Copying Tests and Suites', link: '/project/tests/copying-tests-and-suites' }, + { label: 'Move Tests', link: '/project/tests/move-tests' }, + { label: 'Bulk Test Selection', link: '/project/tests/bulk-test-selection' }, + { label: 'Test Tree Display', link: '/project/tests/test-tree-display' }, + { label: 'Restoring Deleted Tests', link: '/project/tests/restoring-deleted-tests' }, + { label: 'Undetaching Tests', link: '/project/tests/undetaching-tests' }, + { label: 'Test URL and ID', link: '/project/tests/test-url-and-id' }, { label: 'Create a Test', link: '/project/tests/create-a-test' }, { label: 'Test Steps and Expected Results', link: '/project/tests/test-steps-and-expected-results' }, { label: 'Edit Test Steps', link: '/project/tests/edit-test-steps' }, @@ -130,7 +136,7 @@ export default defineConfig({ { label: 'Tags, Labels, and Assignees', link: '/project/tests/tags-labels-and-assignees' }, { label: 'Test Priority', link: '/project/tests/test-priority' }, { label: 'Dynamic Parameters', link: '/project/tests/dynamic-parameters' }, - { label: 'Other Features for Test case Design', link: '/project/tests/other-features-for-test-case-design' }, + { label: 'Sharing Tests and Suites', link: '/project/tests/sharing-tests-and-suites' }, ], }, { diff --git a/redirects.js b/redirects.js index 7d383f9b..1b506aae 100644 --- a/redirects.js +++ b/redirects.js @@ -105,6 +105,10 @@ const redirects = { "/project/runs/import-export/import-tests-from-source-code.md": "/project/import-export/import/import-tests-from-source-code", "/project/runs/runs/reporter/pipes/testomatio.md": "/test-reporting/pipes/testomatio", "/reference/reporter/artifacts/#privacy": "/test-reporting/artifacts/#private-access", + "/project/tests/copy-and-move-your-tests": "/project/tests/copying-tests-and-suites", + "/project/tests/other-features-for-test-case-design": "/project/tests/sharing-tests-and-suites", + "/project/test_design_features": "/project/tests/sharing-tests-and-suites", + "/project/copy_move_tests": "/project/tests/copying-tests-and-suites", } export default redirects \ No newline at end of file diff --git a/src/content/docs/advanced/mermaid-diagrams/index.md b/src/content/docs/advanced/mermaid-diagrams/index.md index e4bda5f1..be6fa369 100644 --- a/src/content/docs/advanced/mermaid-diagrams/index.md +++ b/src/content/docs/advanced/mermaid-diagrams/index.md @@ -1,5 +1,5 @@ --- -title: Mermaid Diagrams for Test Design +title: Mermaid Diagrams description: Add Mermaid diagrams to test and suite descriptions in Testomat.io to model workflows, decision branches, state transitions, and dependencies before testing begins. type: article url: https://docs.testomat.io/advanced/mermaid-diagrams @@ -10,11 +10,11 @@ head: content: Mermaid diagrams, test design, flowchart, state diagram, E2E journey, coverage map, defect reproduction, suite description, markdown editor, Testomat.io --- -Write the diagram as a code block, and Testomat.io shows it as a picture. Add a Mermaid diagram to any test or suite description. Diagrams are most useful for big features with many states. Use a diagram to show a workflow, the branches of a scenario, or how parts of your product connect. +Write the diagram as a code block, and Testomat.io shows it as a picture. Add a Mermaid diagram to any test description. Diagrams are most useful for big features with many states. Use a diagram to show a workflow, the branches of a scenario, or how parts of your product connect. ## Add a Diagram to a Description -1. Open the test or suite you want to document. +1. Open the test you want to document. 2. Click **Edit**. 3. Switch to the **Markdown** tab. 4. Add a fenced code block that starts with ` ```mermaid `. @@ -39,12 +39,6 @@ Each diagram has **SVG** and **PNG** buttons. Click one to download the picture - test data and its variants, - the steps that reproduce a bug. -:::note - -Testomat.io can build a mindmap for you. **Generate Project Structure** reads your folders and suites and suggests a new structure as a diagram. Learn more: [AI-Powered Features](https://docs.testomat.io/advanced/ai-powered-features/ai-powered-features). - -::: - ## Next Steps - [AI-Powered Features](https://docs.testomat.io/advanced/ai-powered-features/ai-powered-features) diff --git a/src/content/docs/project/comments-notifications/comments.md b/src/content/docs/project/comments-notifications/comments.md index 33c86272..28d56453 100644 --- a/src/content/docs/project/comments-notifications/comments.md +++ b/src/content/docs/project/comments-notifications/comments.md @@ -52,7 +52,7 @@ Deleting a comment removes it from the thread for everyone. This cannot be undon ## Comments in shared projects -Comments are always project-specific. When a suite or test [is shared](https://docs.testomat.io/project/tests/other-features-for-test-case-design/#sharing-tests-suites-and-folders) with another project, its comments are not transferred with the shared tests. +Comments are always project-specific. When a suite or test [is shared](https://docs.testomat.io/project/tests/sharing-tests-and-suites/#share-a-test-suite-or-folder) with another project, its comments are not transferred with the shared tests. :::note @@ -64,4 +64,4 @@ The same applies in the other direction: a comment left in a target project is n - [Mentions and notifications](./mentions-and-notifications.md) - [Running tests manually](https://docs.testomat.io/project/runs/running-tests-manually) -- [Other Features for Test case Design](https://docs.testomat.io/project/tests/other-features-for-test-case-design) +- [Sharing Tests and Suites](https://docs.testomat.io/project/tests/sharing-tests-and-suites) diff --git a/src/content/docs/project/tests/bdd-test-case-editor.md b/src/content/docs/project/tests/bdd-test-case-editor.md index 97fefb37..10c26477 100644 --- a/src/content/docs/project/tests/bdd-test-case-editor.md +++ b/src/content/docs/project/tests/bdd-test-case-editor.md @@ -31,7 +31,7 @@ In a BDD project, each suite is a `.feature` file. The scenarios inside the file ![Test overview in the BDD editor of Testomat.io UI](./images/bdd-projects/1-test-overview.png) -A feature file cannot contain another feature file, so a suite cannot contain other suites. Use folders to group feature files. Tests are organised like files in your code, so a manual test can become automated without moving it. See [Suites and Folders](https://docs.testomat.io/project/tests/other-features-for-test-case-design/#suites-and-folders) to learn more. +A feature file cannot contain another feature file, so a suite cannot contain other suites. Use folders to group feature files. Tests are organised like files in your code, so a manual test can become automated without moving it. See [Suites and Folders](https://docs.testomat.io/project/tests/suites-and-folders) to learn more. ## Gherkin Syntax diff --git a/src/content/docs/project/tests/bulk-test-selection.md b/src/content/docs/project/tests/bulk-test-selection.md new file mode 100644 index 00000000..2e9dbedd --- /dev/null +++ b/src/content/docs/project/tests/bulk-test-selection.md @@ -0,0 +1,60 @@ +--- +title: Bulk Test Selection +description: Select multiple tests in Testomat.io and run bulk actions such as adding labels and tags, changing priority, copying, moving, downloading, or deleting tests. +type: article +url: https://docs.testomat.io/project/tests/bulk-test-selection +head: + - tag: meta + attrs: + name: keywords + content: bulk actions, multi-select, select multiple tests, bulk labels, bulk priority, bulk delete, download tests, Testomat.io +--- + +Update several tests at once instead of opening them one by one. + +Select the tests you need on the **Tests** page, then choose an action from the bulk panel. + +## Select Multiple Tests + +1. Go to the **Tests** page. +2. Select the tests you need in one of these ways: + - Click the checkbox next to a test. + - Click the checkbox on a folder or suite to select everything inside it. + - Click **Select all tests** next to a suite. + +The bulk actions panel appears at the bottom of the page and shows how many tests are selected. + +![The bulk actions panel at the bottom of the Tests page with three tests selected](./images/bulk-test-selection/1-bulk-actions-menu.png) + +All actions you choose from this panel apply to the selected tests. To clear the selection, click **✕** on the right of the panel. + +## Bulk Actions + +Choose the action you need and follow the prompts that appear. + +| Action | What it does | +| --- | --- | +| **Run** | Starts a test run with the selected tests. | +| **Labels** | Adds or removes labels and custom fields. | +| **Milestones** | Assigns the selected tests to a milestone. | +| **Copy** | Copies the selected tests to another folder or project. | +| **Move** | Moves the selected tests to another suite or folder in the same project. | +| **Share** | Makes the selected tests available in another project while keeping one original. | +| **Tags** | Adds existing tags or creates new ones. | +| **Link** | Links a defect to the selected tests. | +| **Priority** | Sets a priority for the selected tests. | +| **Delete** | Deletes the selected tests. | +| **⋯** | Downloads the selected tests as a spreadsheet. | + +:::note + +**Delete** removes all selected tests. Check your selection before confirming, especially when working with a large group of tests. Deleted tests can be restored for 90 days. See [Pulse](https://docs.testomat.io/project/pulse). + +::: + +## Next Steps + +- [Test Priority](https://docs.testomat.io/project/tests/test-priority) +- [Tags, Labels, and Assignees](https://docs.testomat.io/project/tests/tags-labels-and-assignees) +- [Move Tests](https://docs.testomat.io/project/tests/move-tests) + diff --git a/src/content/docs/project/tests/classical-test-case-editor.md b/src/content/docs/project/tests/classical-test-case-editor.md index 283721b1..843287bf 100644 --- a/src/content/docs/project/tests/classical-test-case-editor.md +++ b/src/content/docs/project/tests/classical-test-case-editor.md @@ -48,7 +48,7 @@ A suite can have its own description. Use it for information that applies to all - test data, - setup steps. -Add this information once at the suite level instead of repeating it in every test. See [Suites and Folders](https://docs.testomat.io/project/tests/other-features-for-test-case-design/#suites-and-folders) for more information. +Add this information once at the suite level instead of repeating it in every test. See [Suites and Folders](https://docs.testomat.io/project/tests/suites-and-folders) for more information. ## Test Descriptions @@ -90,7 +90,7 @@ Priority shows which tests matter most. The priority icon appears next to the te | **Normal** | Default priority | | **High** | High-importance test | -Set priority when you create a test, change it while editing, or update many tests at once. See [Test Priority](https://docs.testomat.io/project/tests/test-case-creation-and-editing/#test-priority). +Set priority when you create a test, change it while editing, or update many tests at once. See [Test Priority](https://docs.testomat.io/project/tests/test-priority). ## Steps and Expected Results @@ -176,7 +176,7 @@ Open home page {{URL}} Enter an invalid mobile number ${Mobile No} ``` -See [Add Dynamic Parameters to a Test](https://docs.testomat.io/project/tests/test-case-creation-and-editing/#add-dynamic-parameters-to-a-test). +See [Dynamic Parameters](https://docs.testomat.io/project/tests/dynamic-parameters). ## Automation Mapping In a Classical project, Testomat.io connects automated tests to your test cases using the test title and file path. diff --git a/src/content/docs/project/tests/copy-and-move-your-tests.md b/src/content/docs/project/tests/copy-and-move-your-tests.md deleted file mode 100644 index 535533b2..00000000 --- a/src/content/docs/project/tests/copy-and-move-your-tests.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -title: Copy and Move your Tests -description: Learn how to create effective test designs with Testomat.io. This guide covers building test scenarios, using various test design techniques, and integrating them into your project workflow for improved test case management and automated test runs. -type: article -url: https://docs.testomat.io/project/copy_move_tests -head: - - tag: meta - attrs: - name: keywords - content: test design, test cases, test management, test automation, testing techniques, Testomat.io, BDD, Gherkin, Cucumber, test scenarios, project workflow, software testing, duplicate, meta data, link attachments, link issues, link labels ---- - -## How to Copy your Tests, Test Suites, and Folders - -You can copy a single test from a test suite, an entire test suite, or even a folder containing a set of test suites. You can copy these items either within your current project or to a different project. - -### Copying Tests or Test Suites Within Your Project - -1. Go to the **Tests** page. -2. Select the item you want to copy (e.g., a test suite). -3. Open the drop-down menu by clicking the **three dots** next to the **Edit** button. -4. Click **Copy**. -5. Select the destination folder where you want to move your test suite. - -![Testomat.io - 'Copy' button](./images/Copy_option_Tests.png) -![Testomat.io - 'Copy tests' pop-up](./images/copy_test_inside_project.png) - -### Copying Tests or Test Suites to Another Project - -1. Go to the **Tests** page. -2. Select the item you want to copy (e.g., a test suite). -3. Open the drop-down menu by clicking the **three dots** next to the **Edit** button. -4. Click **Copy**. -5. In the pop-up menu, click **'Change project'**. -6. Select the specific project from the drop-down list. -7. Select the destination folder where you want to move your test suite. - -![Testomat.io - 'Change project' button](./images/change_project_button.png) - -### Advanced Copy Options - -When copying tests, suites, or folders, you can include additional metadata. To do this, open the **Copy** modal and expand the **More options** section. - -- **Assign labels** — copies all labels associated with tests, suites, or folders, including **custom labels** -- **Assign attachments** — copies all attached files to tests, suites, or folders -- **Assign issues** — copies linked issues - -![More options](./images/att1_1033.png) - -:::note - -Linked issues are copied only if the destination project has an active integration with the **same Issue Management System and the same project/configuration**. - -Otherwise, linked issues will be **skipped** and **not copied**. - -::: - -You can select **one**, **multiple**, or **all** options at the same time, depending on your needs. If no options are selected, the system creates a copy **without labels, issues, or attachments** by default. - -These advanced options are available for **all copy modes**: - -- **Same project** -- **Other project** -- **Bulk selection project** (for suites and folders) - -:::note - -**Bulk selection project** is not available when copying individual tests. Tests must belong to a suite, while bulk copying places items into the **project root**, which is not supported for tests. - -::: - -This flexibility allows you to either fully duplicate test assets with all related context or create a clean copy without additional metadata. - -## Duplicate Tests - -The **Duplicate** feature allows you to quickly create a copy of an existing test inside Testomat.io. It helps QA engineers reuse test structure, steps, and configuration without creating tests from scratch. - -When a test is duplicated: - -- A new independent test is created in the same suite -- Test content, steps, and parameters are copied -- The new test name automatically includes a **Copy** badge - -During duplication, you can also choose whether to copy additional metadata using **Advanced Duplicate Options**. This allows you to either create a clean test or a full clone of the original test depending on your workflow. - -You can optionally duplicate: - -- Labels -- Linked issues -- Attachments - -These options help preserve test organization, traceability, and supporting materials when creating similar tests. - -### How to Duplicate Test - -1. Navigate to the **Tests** section -2. Open a test you want to duplicate -3. Click the (`⋯`) actions menu -4. Click the **Duplicate** - -![Duplicate](./images/att1_7987.png) - -When the **Choose duplicate settings** modal opens: - -5. Select advanced duplication options if needed: - -- Assign labels -- Assign issues -- Assign attachments - -6. Click **Duplicate** button to confirm - -![Duplicate tests](./images/att2_7987.png) - -A new test is created immediately with the selected metadata. - -:::note - -Your selected duplication settings are **remembered automatically**. The next time you open the **Choose duplicate settings** modal, previously selected metadata will already be preselected, so you don’t need to configure them every time. - -::: - -## Move Your Tests - -You may need to move your tests within a project, for example to another suite. For this purpose, you can use **Move** or **Drag and Drop** functionality. - -### Move menu action - -1. Go to the **Tests** page. -2. Select the item you want to move (e.g. a test suite). -3. Open the drop-down menu by clicking the three dots next to the Edit button. -4. Click **Move**. - -![Alt Move tests button ](./images/move_tests_1.png) - -5. Select the destination folder where you want to move your tests. - -![Alt Move tests button ](./images/move_tests_2.png) - -### Drag and Drop option - -1. Go to the **Tests** page. -2. Expand the folder or suite where you want to move your test(s). -3. Hover over the test, suite, or folder you want to move until the drag handle (⠿) appears. -4. Click and hold the drag handle, then drag the item to your desired location. -5. Position the item slightly below the item you want it to appear under. When space opens up, release to drop. - -![Alt Move tests button ](./images/drag_and_drop.gif) - -**Move several items at once** - -Select multiple rows, then drag any one of them - the whole selection travels together and keeps its relative order. - -**Copy instead of move** - -Hold `Alt` (`Option` on Mac) while you drop to create copies rather than move the items. This works for a single item and for a multi-item selection. - -## How to restore deleted tests? - -The **Trash Bin** feature is designed to enhance data recovery and user experience by allowing users to easily restore accidentally deleted suites or test cases. Revisions are stored for up to 90 days, ensuring that valuable testing data is not permanently lost and can be quickly recovered without the need for complex restoration processes. - -![Testomat.io - Trash Bin](./images/New_vzUGVzmP_2024-08-13.gif) - -You can also track changes to Suits and Test Cases, including deletions, on the [Pulse](https://docs.testomat.io/usage/pulse/) page. diff --git a/src/content/docs/project/tests/copying-tests-and-suites.md b/src/content/docs/project/tests/copying-tests-and-suites.md new file mode 100644 index 00000000..4f7dbabf --- /dev/null +++ b/src/content/docs/project/tests/copying-tests-and-suites.md @@ -0,0 +1,126 @@ +--- +title: Copying Tests and Suites +description: Copy a test, a suite, or a folder in Testomat.io - inside the current project or into another one - choose whether labels, attachments, and linked issues come with it, and duplicate a test inside its own suite. +type: article +url: https://docs.testomat.io/project/tests/copying-tests-and-suites +head: + - tag: meta + attrs: + name: keywords + content: copy tests, copy suite, copy folder, copy to another project, duplicate test, copy badge, assign labels, assign attachments, assign issues, Testomat.io +--- + +Copy tests, suites, and folders when you want to reuse existing test cases without changing the originals. + +You can copy an item to another folder in the same project or to a different project. You can also duplicate a test directly in the same suite. + +The new item is independent from the original. Changes you make to one do not affect the other. + +![Copy lets you choose the destination, Duplicate places the new test next to the original](./images/copying-tests-and-suites/copy-vs-duplicate.png) + +## Copy or Duplicate + +Choose the option that matches what you want to do: + +| Feature | What it does | +| --- | --- | +| **Copy** | Creates a new test, suite, or folder in the location you choose. | +| **Duplicate** | Creates a new test in the same suite as the original. | +| **Move** | Moves the original item to another location. | +| **Share** | Makes the same test available in another project while keeping one original. | + +Use **Share** instead of **Copy** when several projects need to use the same test and you want changes to the original to stay connected. + +## Copy a Test, Suite, or Folder + +A new test can land in the same suite, in another folder, or in another project. The original never moves. + +![The original test stays in place and produces a second test in the same suite, another folder, or another project](./images/copying-tests-and-suites/where-the-copy-goes.png) + +All copy actions start from the same menu. + +1. Go to the **Tests** page. +2. Open the test, suite, or folder you want to copy. +3. Click the **⋯** menu in the top-right corner. +4. Click **Copy**. + +![The actions menu open on a test, with Copy at the top](./images/copying-tests-and-suites/1-copy-test.png) + +The **Copy** window opens with two tabs — **Same project** and **Other project**. + +### Copy Within the Same Project + +1. Stay on the **Same project** tab. +2. Select the destination folder. Use **Search by title** to find it faster. +3. Click **Copy**. + +The copy appears in the selected folder. The original stays where it was. + +### Copy to Another Project + +1. Open the **Other project** tab. +2. Select the destination project. +3. Select the destination folder. +4. Click **Copy**. + +:::note + +Bulk copying is available for suites and folders. A single test cannot be copied through bulk selection because tests belong to suites. + +::: + +### Choose What to Copy + +By default, Testomat.io copies the test content without its additional data. To include more: + +1. In the **Copy** window, click the gear icon in the bottom-left corner. +2. Under **More options**, select what you want to include. +3. Click **Copy**. + +![The Copy window with the Same project tab open and More options expanded from the gear icon](./images/copying-tests-and-suites/2-advanced-copy.png) + +| Option | What it copies | +| --- | --- | +| **Assign labels** | Labels and custom labels. | +| **Assign issues** | Issues linked to the tests, suites, or folders. | +| **Assign attachments** | Files attached to the tests, suites, or folders. | + +You can select any combination of these options. The line next to the gear icon always describes the result, for example *Creates a copy without labels and without issues and without attachments*. + +Leave the options empty when you are creating a clean starting point for a new feature. Include attachments and labels when you want to reuse the existing test setup. + +To copy several items with the same options, click **Copy in Bulk Edit**. + +Linked issues are copied only when the destination project uses an active integration with the same issue management system and the same project or configuration. Otherwise, the issues are skipped. + +:::note + +These options are available when copying within the same project, to another project, or through bulk selection. + +::: + +## Duplicate a Test + +Use **Duplicate** when you need another version of a test in the same suite. The duplicate keeps the test content, steps, and parameters. + +1. Open the test. +2. Click the **⋯** menu in the top-right corner. +3. Click **Duplicate**. +4. Select what you want to include — the same options as for copying. +5. Click **Duplicate**. + +![The actions menu open on a test, with Duplicate highlighted](./images/copying-tests-and-suites/3-duplicate-test.png) + +The new test appears in the same suite and gets a **Copy** badge. Rename it when you are ready. + +:::note + +Testomat.io remembers your duplicate settings and uses the same selections the next time you duplicate a test. + +::: + +## Next Steps + +- [Suites and Folders](https://docs.testomat.io/project/tests/suites-and-folders) +- [Tags, Labels, and Assignees](https://docs.testomat.io/project/tests/tags-labels-and-assignees) +- [Bulk Edit](https://docs.testomat.io/advanced/bulk-edit-folder) diff --git a/src/content/docs/project/tests/create-a-test.md b/src/content/docs/project/tests/create-a-test.md index 1a906a7e..e8eadd22 100644 --- a/src/content/docs/project/tests/create-a-test.md +++ b/src/content/docs/project/tests/create-a-test.md @@ -58,7 +58,7 @@ Open test to add the details. Each written title in a line becomes a separate test in the suite. It is similar to the **Quick Test Creation** but a bit in other way. This is useful when you want to create the tests first and add description later. -You can also use [keyboard shortcuts](https://docs.testomat.io/usage/keyboard-shortcuts/) to create and edit tests and suites. +You can also use [keyboard shortcuts](https://docs.testomat.io/advanced/shortcuts/) to create and edit tests and suites. ## Save a Test diff --git a/src/content/docs/project/tests/dynamic-parameters.md b/src/content/docs/project/tests/dynamic-parameters.md index 4d8f1430..9681d045 100644 --- a/src/content/docs/project/tests/dynamic-parameters.md +++ b/src/content/docs/project/tests/dynamic-parameters.md @@ -120,7 +120,7 @@ Using `${}` everywhere keeps the syntax consistent. ## Next Steps -- [Test Steps and Expected Results](./test-steps-and-expected-results.md) -- [Edit Test Steps](./edit-test-steps.md) -- [Tags, Labels, and Assignees](./tags-labels-and-assignees.md) +- [Test Steps and Expected Results](https://docs.testomat.io/project/tests/test-steps-and-expected-results) +- [Edit Test Steps](https://docs.testomat.io/project/tests/edit-test-steps) +- [Tags, Labels, and Assignees](https://docs.testomat.io/project/tests/tags-labels-and-assignees) diff --git a/src/content/docs/project/tests/images/2023-08-03_00.37.59@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.37.59@2x.png deleted file mode 100644 index df66a342..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.37.59@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_00.40.35@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.40.35@2x.png deleted file mode 100644 index 22cc2897..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.40.35@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_00.42.32@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.42.32@2x.png deleted file mode 100644 index 4e007160..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.42.32@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_00.45.26@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.45.26@2x.png deleted file mode 100644 index fd091a10..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.45.26@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_00.49.14@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.49.14@2x.png deleted file mode 100644 index aeb000ae..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.49.14@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_00.53.02@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.53.02@2x.png deleted file mode 100644 index 6a4eaa2b..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.53.02@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_00.54.46@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.54.46@2x.png deleted file mode 100644 index 74364277..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.54.46@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_00.57.10@2x.png b/src/content/docs/project/tests/images/2023-08-03_00.57.10@2x.png deleted file mode 100644 index b6f1c502..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_00.57.10@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.01.17@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.01.17@2x.png deleted file mode 100644 index c3e01813..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.01.17@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.05.06@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.05.06@2x.png deleted file mode 100644 index 0e657586..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.05.06@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.06.27@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.06.27@2x.png deleted file mode 100644 index 2386fae8..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.06.27@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.07.03@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.07.03@2x.png deleted file mode 100644 index 1a08eb54..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.07.03@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.10.41@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.10.41@2x.png deleted file mode 100644 index 810ef79b..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.10.41@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.12.09@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.12.09@2x.png deleted file mode 100644 index 7b701738..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.12.09@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.12.54@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.12.54@2x.png deleted file mode 100644 index 8da2114d..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.12.54@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.15.20@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.15.20@2x.png deleted file mode 100644 index 2687b221..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.15.20@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.15.54@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.15.54@2x.png deleted file mode 100644 index 20943525..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.15.54@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.17.58@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.17.58@2x.png deleted file mode 100644 index ef8f8c02..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.17.58@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.19.08@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.19.08@2x.png deleted file mode 100644 index 344e34b9..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.19.08@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.21.06@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.21.06@2x.png deleted file mode 100644 index 9207f4f9..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.21.06@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.21.41@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.21.41@2x.png deleted file mode 100644 index 6c0cd945..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.21.41@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.23.41@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.23.41@2x.png deleted file mode 100644 index b1bfa25d..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.23.41@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.24.31@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.24.31@2x.png deleted file mode 100644 index 629225d5..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.24.31@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.25.30@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.25.30@2x.png deleted file mode 100644 index b0bfe84d..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.25.30@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/2023-08-03_01.25.47@2x.png b/src/content/docs/project/tests/images/2023-08-03_01.25.47@2x.png deleted file mode 100644 index 67cd6db7..00000000 Binary files a/src/content/docs/project/tests/images/2023-08-03_01.25.47@2x.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/BDD_edit_suite.png b/src/content/docs/project/tests/images/BDD_edit_suite.png deleted file mode 100644 index 30d10398..00000000 Binary files a/src/content/docs/project/tests/images/BDD_edit_suite.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/BDD_edit_test.png b/src/content/docs/project/tests/images/BDD_edit_test.png deleted file mode 100644 index 4e2ac54a..00000000 Binary files a/src/content/docs/project/tests/images/BDD_edit_test.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_0ldrsL29_2024-10-05.gif b/src/content/docs/project/tests/images/New_0ldrsL29_2024-10-05.gif deleted file mode 100644 index 6539053c..00000000 Binary files a/src/content/docs/project/tests/images/New_0ldrsL29_2024-10-05.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_10TBA7jV_2024-08-03.png b/src/content/docs/project/tests/images/New_10TBA7jV_2024-08-03.png deleted file mode 100644 index 1b9163d3..00000000 Binary files a/src/content/docs/project/tests/images/New_10TBA7jV_2024-08-03.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_1hpi4Xy4_2024-10-07.png b/src/content/docs/project/tests/images/New_1hpi4Xy4_2024-10-07.png deleted file mode 100644 index da56387c..00000000 Binary files a/src/content/docs/project/tests/images/New_1hpi4Xy4_2024-10-07.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_1pgghaYx_2024-08-08.png b/src/content/docs/project/tests/images/New_1pgghaYx_2024-08-08.png deleted file mode 100644 index b9756e1e..00000000 Binary files a/src/content/docs/project/tests/images/New_1pgghaYx_2024-08-08.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_8DanPb4g_2024-10-08.png b/src/content/docs/project/tests/images/New_8DanPb4g_2024-10-08.png deleted file mode 100644 index 63805829..00000000 Binary files a/src/content/docs/project/tests/images/New_8DanPb4g_2024-10-08.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_926xDzhS_2024-08-13.png b/src/content/docs/project/tests/images/New_926xDzhS_2024-08-13.png deleted file mode 100644 index 4f1bede3..00000000 Binary files a/src/content/docs/project/tests/images/New_926xDzhS_2024-08-13.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_9mLj3wh3_2024-10-07.png b/src/content/docs/project/tests/images/New_9mLj3wh3_2024-10-07.png deleted file mode 100644 index 24cb7863..00000000 Binary files a/src/content/docs/project/tests/images/New_9mLj3wh3_2024-10-07.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_OwQMWpps_2024-10-07.png b/src/content/docs/project/tests/images/New_OwQMWpps_2024-10-07.png deleted file mode 100644 index 44638c5b..00000000 Binary files a/src/content/docs/project/tests/images/New_OwQMWpps_2024-10-07.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_VxPGvi8Y_2024-10-07.png b/src/content/docs/project/tests/images/New_VxPGvi8Y_2024-10-07.png deleted file mode 100644 index be44b414..00000000 Binary files a/src/content/docs/project/tests/images/New_VxPGvi8Y_2024-10-07.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_g6FZ3V7n_2024-08-10.png b/src/content/docs/project/tests/images/New_g6FZ3V7n_2024-08-10.png deleted file mode 100644 index 81c1c294..00000000 Binary files a/src/content/docs/project/tests/images/New_g6FZ3V7n_2024-08-10.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/New_vzUGVzmP_2024-08-13.gif b/src/content/docs/project/tests/images/New_vzUGVzmP_2024-08-13.gif deleted file mode 100644 index 697fa3cf..00000000 Binary files a/src/content/docs/project/tests/images/New_vzUGVzmP_2024-08-13.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/Preview_attach_1.gif b/src/content/docs/project/tests/images/Preview_attach_1.gif deleted file mode 100644 index e7477f90..00000000 Binary files a/src/content/docs/project/tests/images/Preview_attach_1.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/Rendering_test_param_1.gif b/src/content/docs/project/tests/images/Rendering_test_param_1.gif deleted file mode 100644 index 7de65712..00000000 Binary files a/src/content/docs/project/tests/images/Rendering_test_param_1.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/Save_To_Draft_and_View_Test.png b/src/content/docs/project/tests/images/Save_To_Draft_and_View_Test.png deleted file mode 100644 index eae3b561..00000000 Binary files a/src/content/docs/project/tests/images/Save_To_Draft_and_View_Test.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/apply_draft_or_delete_buttons.png b/src/content/docs/project/tests/images/apply_draft_or_delete_buttons.png deleted file mode 100644 index 79ca4da4..00000000 Binary files a/src/content/docs/project/tests/images/apply_draft_or_delete_buttons.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/bulk-test-selection/1-bulk-actions-menu.png b/src/content/docs/project/tests/images/bulk-test-selection/1-bulk-actions-menu.png new file mode 100644 index 00000000..c6bd94e7 Binary files /dev/null and b/src/content/docs/project/tests/images/bulk-test-selection/1-bulk-actions-menu.png differ diff --git a/src/content/docs/project/tests/images/copying-tests-and-suites/1-copy-test.png b/src/content/docs/project/tests/images/copying-tests-and-suites/1-copy-test.png new file mode 100644 index 00000000..f55cc37d Binary files /dev/null and b/src/content/docs/project/tests/images/copying-tests-and-suites/1-copy-test.png differ diff --git a/src/content/docs/project/tests/images/copying-tests-and-suites/2-advanced-copy.png b/src/content/docs/project/tests/images/copying-tests-and-suites/2-advanced-copy.png new file mode 100644 index 00000000..035852c1 Binary files /dev/null and b/src/content/docs/project/tests/images/copying-tests-and-suites/2-advanced-copy.png differ diff --git a/src/content/docs/project/tests/images/copying-tests-and-suites/3-duplicate-test.png b/src/content/docs/project/tests/images/copying-tests-and-suites/3-duplicate-test.png new file mode 100644 index 00000000..f61d9d86 Binary files /dev/null and b/src/content/docs/project/tests/images/copying-tests-and-suites/3-duplicate-test.png differ diff --git a/src/content/docs/project/tests/images/copying-tests-and-suites/copy-vs-duplicate.png b/src/content/docs/project/tests/images/copying-tests-and-suites/copy-vs-duplicate.png new file mode 100644 index 00000000..9386ea5f Binary files /dev/null and b/src/content/docs/project/tests/images/copying-tests-and-suites/copy-vs-duplicate.png differ diff --git a/src/content/docs/project/tests/images/copying-tests-and-suites/where-the-copy-goes.png b/src/content/docs/project/tests/images/copying-tests-and-suites/where-the-copy-goes.png new file mode 100644 index 00000000..90b6a068 Binary files /dev/null and b/src/content/docs/project/tests/images/copying-tests-and-suites/where-the-copy-goes.png differ diff --git a/src/content/docs/project/tests/images/edit_suite.png b/src/content/docs/project/tests/images/edit_suite.png deleted file mode 100644 index a7587b8a..00000000 Binary files a/src/content/docs/project/tests/images/edit_suite.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/edit_test_classical_editor.png b/src/content/docs/project/tests/images/edit_test_classical_editor.png deleted file mode 100644 index 1e7bf25c..00000000 Binary files a/src/content/docs/project/tests/images/edit_test_classical_editor.png and /dev/null differ diff --git a/src/content/docs/project/tests/images/gif1_2384.gif b/src/content/docs/project/tests/images/gif1_2384.gif deleted file mode 100644 index ceafa2b9..00000000 Binary files a/src/content/docs/project/tests/images/gif1_2384.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/gif1_7327.gif b/src/content/docs/project/tests/images/gif1_7327.gif deleted file mode 100644 index 7ea7550c..00000000 Binary files a/src/content/docs/project/tests/images/gif1_7327.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/gif2_2384.gif b/src/content/docs/project/tests/images/gif2_2384.gif deleted file mode 100644 index cffd747d..00000000 Binary files a/src/content/docs/project/tests/images/gif2_2384.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/gif2_7327.gif b/src/content/docs/project/tests/images/gif2_7327.gif deleted file mode 100644 index 37a8595d..00000000 Binary files a/src/content/docs/project/tests/images/gif2_7327.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/link_bdd.gif b/src/content/docs/project/tests/images/link_bdd.gif deleted file mode 100644 index e602140c..00000000 Binary files a/src/content/docs/project/tests/images/link_bdd.gif and /dev/null differ diff --git a/src/content/docs/project/tests/images/move-tests/1-move-test.png b/src/content/docs/project/tests/images/move-tests/1-move-test.png new file mode 100644 index 00000000..cd91515a Binary files /dev/null and b/src/content/docs/project/tests/images/move-tests/1-move-test.png differ diff --git a/src/content/docs/project/tests/images/move-tests/2-drag-suite.png b/src/content/docs/project/tests/images/move-tests/2-drag-suite.png new file mode 100644 index 00000000..5cf3e939 Binary files /dev/null and b/src/content/docs/project/tests/images/move-tests/2-drag-suite.png differ diff --git a/src/content/docs/project/tests/images/move-tests/one-test-new-place.png b/src/content/docs/project/tests/images/move-tests/one-test-new-place.png new file mode 100644 index 00000000..320d5a47 Binary files /dev/null and b/src/content/docs/project/tests/images/move-tests/one-test-new-place.png differ diff --git a/src/content/docs/project/tests/images/restoring-deleted-tests/1-trash-bin.png b/src/content/docs/project/tests/images/restoring-deleted-tests/1-trash-bin.png new file mode 100644 index 00000000..8a184824 Binary files /dev/null and b/src/content/docs/project/tests/images/restoring-deleted-tests/1-trash-bin.png differ diff --git a/src/content/docs/project/tests/images/restoring-deleted-tests/2-restore.png b/src/content/docs/project/tests/images/restoring-deleted-tests/2-restore.png new file mode 100644 index 00000000..298f9a63 Binary files /dev/null and b/src/content/docs/project/tests/images/restoring-deleted-tests/2-restore.png differ diff --git a/src/content/docs/project/tests/images/sharing-tests-and-suites/1-sharing-settings.png b/src/content/docs/project/tests/images/sharing-tests-and-suites/1-sharing-settings.png new file mode 100644 index 00000000..32b60768 Binary files /dev/null and b/src/content/docs/project/tests/images/sharing-tests-and-suites/1-sharing-settings.png differ diff --git a/src/content/docs/project/tests/images/sharing-tests-and-suites/2-share-test-with-other-projects.png b/src/content/docs/project/tests/images/sharing-tests-and-suites/2-share-test-with-other-projects.png new file mode 100644 index 00000000..9bdf876a Binary files /dev/null and b/src/content/docs/project/tests/images/sharing-tests-and-suites/2-share-test-with-other-projects.png differ diff --git a/src/content/docs/project/tests/images/sharing-tests-and-suites/3-sharing-multiple-tests.png b/src/content/docs/project/tests/images/sharing-tests-and-suites/3-sharing-multiple-tests.png new file mode 100644 index 00000000..4792a54e Binary files /dev/null and b/src/content/docs/project/tests/images/sharing-tests-and-suites/3-sharing-multiple-tests.png differ diff --git a/src/content/docs/project/tests/images/sharing-tests-and-suites/one-source-many-projects.png b/src/content/docs/project/tests/images/sharing-tests-and-suites/one-source-many-projects.png new file mode 100644 index 00000000..f9109736 Binary files /dev/null and b/src/content/docs/project/tests/images/sharing-tests-and-suites/one-source-many-projects.png differ diff --git a/src/content/docs/project/tests/images/sharing-tests-and-suites/what-travels-what-stays.png b/src/content/docs/project/tests/images/sharing-tests-and-suites/what-travels-what-stays.png new file mode 100644 index 00000000..d471f6be Binary files /dev/null and b/src/content/docs/project/tests/images/sharing-tests-and-suites/what-travels-what-stays.png differ diff --git a/src/content/docs/project/tests/images/test-tree-display/1-display-menu.png b/src/content/docs/project/tests/images/test-tree-display/1-display-menu.png new file mode 100644 index 00000000..37750348 Binary files /dev/null and b/src/content/docs/project/tests/images/test-tree-display/1-display-menu.png differ diff --git a/src/content/docs/project/tests/images/test-tree-display/2-tests-unhidden.png b/src/content/docs/project/tests/images/test-tree-display/2-tests-unhidden.png new file mode 100644 index 00000000..959ce328 Binary files /dev/null and b/src/content/docs/project/tests/images/test-tree-display/2-tests-unhidden.png differ diff --git a/src/content/docs/project/tests/images/test-tree-display/3-toolbar-pinned.png b/src/content/docs/project/tests/images/test-tree-display/3-toolbar-pinned.png new file mode 100644 index 00000000..9df716d5 Binary files /dev/null and b/src/content/docs/project/tests/images/test-tree-display/3-toolbar-pinned.png differ diff --git a/src/content/docs/project/tests/images/test-tree-display/4-tests-hidden.png b/src/content/docs/project/tests/images/test-tree-display/4-tests-hidden.png new file mode 100644 index 00000000..c2dd3e6c Binary files /dev/null and b/src/content/docs/project/tests/images/test-tree-display/4-tests-hidden.png differ diff --git a/src/content/docs/project/tests/images/test-url-and-id/1-copy-test-id-url.png b/src/content/docs/project/tests/images/test-url-and-id/1-copy-test-id-url.png new file mode 100644 index 00000000..6b9418b2 Binary files /dev/null and b/src/content/docs/project/tests/images/test-url-and-id/1-copy-test-id-url.png differ diff --git a/src/content/docs/project/tests/images/test-url-and-id/paste-an-id-get-a-link.png b/src/content/docs/project/tests/images/test-url-and-id/paste-an-id-get-a-link.png new file mode 100644 index 00000000..7aa6ddb0 Binary files /dev/null and b/src/content/docs/project/tests/images/test-url-and-id/paste-an-id-get-a-link.png differ diff --git a/src/content/docs/project/tests/images/undetaching-tests/1-undetach-tests.png b/src/content/docs/project/tests/images/undetaching-tests/1-undetach-tests.png new file mode 100644 index 00000000..edd5cc65 Binary files /dev/null and b/src/content/docs/project/tests/images/undetaching-tests/1-undetach-tests.png differ diff --git a/src/content/docs/project/tests/images/undetaching-tests/2-clear-detached-state.png b/src/content/docs/project/tests/images/undetaching-tests/2-clear-detached-state.png new file mode 100644 index 00000000..a42fe659 Binary files /dev/null and b/src/content/docs/project/tests/images/undetaching-tests/2-clear-detached-state.png differ diff --git a/src/content/docs/project/tests/move-tests.md b/src/content/docs/project/tests/move-tests.md new file mode 100644 index 00000000..28647046 --- /dev/null +++ b/src/content/docs/project/tests/move-tests.md @@ -0,0 +1,75 @@ +--- +title: Move Tests +description: Move tests, suites, and folders to another place in a project using the Move menu or drag and drop. +type: article +url: https://docs.testomat.io/project/tests/move-tests +head: + - tag: meta + attrs: + name: keywords + content: move tests, move suite, drag and drop tests, reorder tests, test tree, multi-select move, Testomat.io +--- + +Move a test, suite, or folder when you want to change its place in the project tree. + +Moving does not create a copy. The same item simply appears in its new location. + +![A test leaves one folder and arrives in another, still as a single test](./images/move-tests/one-test-new-place.png) + +You can move items using the **Move** menu or by dragging and dropping them. + +:::note + +Moving works within the same project. To use a test in another project, copy or share it instead. + +::: + +## Ways to Move an Item + +### Use the Move Menu + +Use the menu when you already know where you want to place the item. + +1. Go to the **Tests** page. +2. Select the test, suite, or folder you want to move. +3. Click the (`...`) menu in the top-right corner. +4. Click **Move**. +5. Select the destination folder and click **Move** again. + +![The actions menu open on a test, with Move highlighted](./images/move-tests/1-move-test.png) + +### Drag and Drop + +Use drag and drop when you want to place an item directly in the project tree. + +1. Go to the **Tests** page. +2. Open the folder or suite where you want to move the item. +3. Hover over the test, suite, or folder until the drag handle appears. +4. Drag the item to its new location. +5. Drop it when the destination is highlighted. + +![A suite dragged into a folder](./images/move-tests/2-drag-suite.png) + +## Move Several Items + +1. Select the items you want to move. +2. Drag one of the selected items. +3. Drop the selection in the new location. + +All selected items move together and keep their order. + +## Copy While Dragging + +If you want to create a copy instead of moving the original, hold **Alt** on Windows or **Option** on Mac while dropping the item. This creates a copy inside the current project. + +:::note + +Dragging with **Alt**/**Option** copies the items without giving you options for labels, attachments, or issues. To choose what to copy, see [Copying Tests and Suites](https://docs.testomat.io/project/tests/copying-tests-and-suites). + +::: + +## Next Steps + +- [Copying Tests and Suites](https://docs.testomat.io/project/tests/copying-tests-and-suites) +- [Suites and Folders](https://docs.testomat.io/project/tests/suites-and-folders) + diff --git a/src/content/docs/project/tests/other-features-for-test-case-design.md b/src/content/docs/project/tests/other-features-for-test-case-design.md deleted file mode 100644 index 2d19aae9..00000000 --- a/src/content/docs/project/tests/other-features-for-test-case-design.md +++ /dev/null @@ -1,417 +0,0 @@ ---- -title: Other Features for Test case Design -description: Learn how to use Testomat.io's test design features to manage test cases, apply design techniques, and organize your test structure effectively for automation and collaboration. -type: article -url: https://docs.testomat.io/project/test_design_features -head: - - tag: meta - attrs: - name: keywords - content: test design, test case management, test automation, Testomat.io, test organization, software testing, testing tools, test suites, test structure, folders, mark as favorite, export suite to PDF, multiselection, labels, tags, share tests, share suites, share folders, unlink shared tests, single source of truth ---- - -Once you select one or more tests, a bulk actions panel appears above the test list. From there you can run, organize, or clean up all the selected tests at once, without opening each of them. - -| Action | What it does | -|--------|--------------| -| **Run** | Launches a test run containing the selected items. | -| **Labels** | Add or remove labels or custom fields for the selected tests. | -| **Copy** | Copy selected tests within the current project or to another project. | -| **Move** | Move tests to another test suite or folder within the same project. | -| **Tags** | Assign existing tags or create new ones for the selected tests. | -| **+ Link** | Open a pop-up to link a related defect to the selected tests. | -| **Priority** | Set priority levels for the selected tests. | -| **More options (`⋯`)** | Contains the additional **Download** action - export selected tests to a spreadsheet. | -| **Delete** | Permanently remove the selected tests. | - -Learn more about [labels](https://docs.testomat.io/advanced/tags-labels/labels-and-custom-fields) and on [using tags](https://docs.testomat.io/advanced/tags-labels/tags/). - -## URL/ID Quick Copy - -Depending on your needs, you can set up a convenient way to copy **URL/IDs** in **Test Cases**, **Suites** and **Runs**. - -To start, you need to open a **Test Case** (**Suite** or **Run**): - -1. Click the copy icon to open the modal window. -2. In the window that opens, you can copy the format you are interested in. -3. Turn on the toggle next to a format if you need to use it frequently. -4. Now, every time you click on the ID, the selected format will be copied to clipboard without any further actions. - -![Testomat.io - URL/ID Copy](./images/New_1pgghaYx_2024-08-08.png) - -## Display Settings - -The **Display** menu at the top of the **Tests** page lets you control how the test structure and side view are presented. Settings are applied instantly and persist across sessions. - -The following options are available: - -- **Hide tests in tree** -- **Pin sidebar** - -![Display](./images/att1_7327.png) - -### Hide Tests in Tree - -**Hide tests in tree** shows only folders and suites in the main tree, hiding individual test entries from the list. - -This is useful in large projects where the tree becomes difficult to navigate due to the number of tests. Hiding them keeps the structure clean and makes it easier to find the suite or folder you need without scrolling through hundreds of test entries. - -![Hide Tests in Tree](./images/gif2_7327.gif) - -### Pin Sidebar - -**Pin sidebar** keeps both the test tree and test or suite details visible at the same time — giving you access to filters, search, and actions while reviewing tests and suites, so you can navigate without losing context and stay focused during QA activities. - -You can enable it in two ways: - -- Click the **Pin icon** in the top-right corner of the test or suite detail panel -- Open the **Display** menu at the top of the Tests page and toggle **Pin sidebar** - -| State | Behavior | -| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -| **Unpinned** (default) | The sidebar opens over the Tests page. Some toolbar actions may not be accessible. | -| **Pinned** | The sidebar is fixed alongside the test tree. The full **Tests** page toolbar — filters, search, Display menu, and actions — remains accessible. | - -![Pin feature](./images/gif1_7327.gif) - -Use **Pin Sidebar** when navigating multiple tests in sequence, or during QA audits. It keeps the test tree, filters, search, and actions accessible while reviewing test details, providing: - -- Faster navigation between tests and suites -- Continuous focus during QA activities -- Less UI friction throughout your workflow - -### Preview Tests in Branches - -You can review tests created inside a branch without switching to that branch. Branch preview allows you to: - -* See newly created tests -* Review changes before switching branches -* Compare work between branches -* Reduce unnecessary branch switching - -This helps teams review changes faster and improves collaboration during feature development. - -## Suites and Folders - -Unlike other test management systems, **Testomat.io doesn't allow suite to include other suites and tests**. That's why you can either create a suite (a collection of tests) or folder (collection of suites). - -:::note -When creating a suite you have to explicitly set its type: a suite or a folder. -::: - -![Testomat.io - New suite](./images/2023-08-03_00.53.02@2x.png) - -This was designed so tests structure could match the filesystem. For instance, if you use BDD project, feature file can contain scenarios, but can't contain other feature files. The same for automated tests, a file can contain tests but can't contain other files. - -It's assumed that in any moment a manual test can be automated, so it is important to keep the filesystem structure in a project. - -An empty suite can be converted to folder or vice versa - -![Testomat.io - Empty suite](./images/2023-08-03_00.54.46@2x.png) - -Also you can set an emoji icon for the suite - -![Testomat.io - Pick emoji](./images/2023-08-03_00.57.10@2x.png) - -If your test is deeply nested within suites and folders, you can use breadcrumbs with tooltips to navigate the project structure more effectively. - -![Testomat.io - Breadcrumbs tooltip](./images/New_g6FZ3V7n_2024-08-10.png) - -## Undetach Tests - -A bad import can mark a whole suite of automated tests as **Detached** - they were imported before, but the latest import did not find them. You can bring them back in bulk instead of one at a time. - -On the **Tests** page, filter by state **Detached**. A banner appears with an **Undetach tests** action that clears the state from every detached test at once. - -:::note - -The action is project-wide: it clears every detached test in the project, not only the ones matching your current filter. That is what makes it useful after a misconfigured import, when detached tests are scattered across suites. - -::: - -For something narrower, a suite's menu offers **Undetach** when it contains detached tests, and any single detached test can be undetached from its own menu. - -:::note - -A detached test that no longer carries any code comes back as a manual test rather than an automated one. - -::: - -### Mark Folders & Suites as Favourites - -Working with large projects often means navigating through a long test tree or running the same search queries over and over again. To make your workflow smoother, we’ve introduced the **'Starred'** feature for test suites and folders. - -**Now you can:** - -- ⭐ **Star any suite/folder** you plan to work on — whether it’s for the current sprint, a specific release, or ongoing maintenance. -- 📂 **Create your own quick-access list** of suites to eliminate repetitive navigation through the entire test tree. -- 🔍 **Mark favourites directly from search results** — if you’re looking for a test or suite/folders by keyword or using filters you can instantly star it without leaving the search view. -- ⏱ **Quickly return to starred suites/folders** even after filters or selections are reset — simply use the **'Starred'** filter to jump back. -- 🛠 **Work more efficiently** by keeping frequently accessed suites/folders at your fingertips, especially in large or multi-team projects. - -Whether you’re focusing on smoke tests, regression packs, or a specific customer scenario, the **'Starred'** feature ensures you spend less time navigating and more time testing. - -![Testomat.io - Mark Folders & Suites as Favourites](./images/star_suite.gif) - -:::note - -To remove all suites/folders from Favourites with one click: Use the **'Starred'** filter -> click '**Crossed star'** button -> confirm action. - -![Testomat.io - UnMark Folders & Suites as Favourites](./images/unstar_suite.png) -::: - -### Convert Suite to Folder - -When working on test design, it is common to start writing tests inside a single suite and later realize that the suite should become a higher-level section containing multiple suites. - -Previously, restructuring required creating new folders and manually moving tests. To simplify this workflow, Testomat.io allows converting an existing suite into a folder — even if the suite already contains tests. - -When converting: - -- a **new folder with the same name** is created -- the **original suite is placed inside this folder** -- all existing tests remain unchanged - -This allows you to reorganize test structure without recreating suites or losing test history. - -#### How to Convert a Suite to a Folder - -1. Navigate to the **Tests** page -2. Open the suite you want to restructure -3. Click the **Extra menu (⋯)** -4. Select **Convert to folder** -5. Confirm the action in the popup - -![Convert to folder](./images/att1_9.png) - -Before conversion: - -``` -Notifications (Suite) -|-- Test 1 -|-- Test 2 -``` - -After conversion: - -``` -Notifications (Folder) -└── Notifications (Suite) - ├── Test 1 - └── Test 2 -``` - -You can now create additional suites inside the folder and reorganize tests as needed. - -#### Why This Is Useful - -Test structures rarely stay perfect from the start. As your project grows, suites can become too large or cover multiple sub-features. - -Converting a suite to a folder allows QA engineers to: - -- **Reorganize tests on the fly** without stopping test creation -- **Split large suites into smaller, logical sub-suites** inside the new folder -- **Preserve all tests and history** — no need to recreate suites or move tests manually -- **Optionally rename** the folder or the inner suite to reflect its new role, keeping the hierarchy clear - -This makes the test tree easier to navigate and maintain, ensuring a **scalable and readable structure** as the project grows. - -## Export Suite as PDF - -You can now download any suite as a **PDF file**. This feature is designed to help teams share test results, documentation, or audit trails with stakeholders who may not have access to the platform itself. - -**Using this feature is simple:** - -1. Go to the **Tests** page. -2. Open the desired suite. -3. Click **'Extra menu'** button. -4. Select **'Export as PDF'** option from the dropdown menu. - -![Testomat.io - Export Suite as PDF](./images/Export_Suite_1.png) - -The export captures the entire test suite, including all individual test cases, their IDs, types, steps, expected results and screenshots. - -![Testomat.io - Export Suite as PDF](./images/Export_Suite_2.png) - -This makes it convenient to share test content outside of Testomat.io, whether for reviews, documentation, or reporting purposes. - -## Sharing Tests, Suites, and Folders - -The **Share** feature is designed to keep test logic and structure consistent across multiple projects while keeping execution results independent. - -**Key principles:** - -- Shared items have **a single source project** controlling content and updates -- Shared items are **read-only** in target projects; editing is only possible in the source project or after unlinking -- Target projects maintain local execution context: runs, logs, statuses, results -- Items can be re-shared to additional projects without creating duplicates -- Only projects of the same type can share items (e.g., BDD → BDD, Classic → Classic) - -:::note - -The **Share** feature is a **paid feature**, included in Professional, Enterprise, and Trial plans. - -::: - -You can share the following entities between projects: - -- Test -- Suite -- Folder - -:::note - -Folders act as containers for shared content. The folder itself is not marked as shared, but its nested items are. - -::: - -### Project Sharing Settings - -Control which users can share tests and suites: - -- **On:** All users can share tests and suites with other projects. -- **Off (default):** Only Owners and Managers can share. - -To change the default settings: - -1. Navigate to the **Settings** in the sidebar -2. Select the **Project** -3. Toggle **On** to allow access - -![Share settigns](./images/att1_7821.png) - -These settings apply to both initially shared and re-shared items. - -:::note - -Only **Owners and Managers** can enable or disable the sharing toggle. - -::: - -### How Sharing Works - -When a test, suite, or folder is shared, specific data from the source project is propagated to all target projects, while other information remains local. - -| Data | Shared Behavior | -| ---------------------- | --------------------------------------------------------------------------------------- | -| Title & Description | Shared; cannot be changed in target projects | -| Attachments | Shared; cannot be changed or new ones added in target projects | -| Labels & custom labels | Shared; additional labels can be added locally in target projects | -| Tags | Shared; cannot be changed in target projects | -| Priority | Shared; cannot be changed in target projects | -| Linked issues | Shared (if integration is enabled) | -| Assignee | Shared (if the user exists in the target project); cannot be changed in target projects | -| Test author | Shared (if the user exists in the target project) | -| Runs | Not Shared; each project reports its own results | -| History | Not Shared; always project-specific | -| Requirements | Not Shared; always project-specific | -| Comments | Not Shared; always project-specific | - -### Synchronization behavior - -When an item is first shared, all data marked as **Shared** in the table above is propagated to target projects. After sharing is established, only a limited set of fields continues to synchronize when changes are made in the source project. - -- New tests added to a shared suite in the source project automatically appear in all linked projects -- Updates to **Title**, **Description**, and **Tags** are synchronized from the source project after sharing -- Other shared fields are **not** synchronized after the initial share - -### Permissions and Restrictions - -- Shared items are **read-only** in target projects -- Editing is allowed **only in the source project** -- Editing becomes available **only after unlinking** the shared item -- AI actions are disabled for for shared items -- Execution is allowed in all projects -- Execution results remain local to each project - -### How to Share a Single Item - -1. Navigate to the **Tests** page -2. Open a test, suite, or folder in the source project -3. Click the **More options** button -4. Select **Share to other projects** - -![Select Share to other projects](images/att3_2384.png) - -5. Open the **Bulk selection project** tab to share with multiple projects, or stay on **Other project** to share with a single project -6. Choose target project(s) -7. Click the **Share** button - -![Share suite](./images/att4_2384.png) - -- Icons and tooltips indicating shared projects appear -- The selected items will appear in the chosen projects as shared and read-only -- Suites and folders shared in bulk are placed in the **Root** by default -- Sharing tests allow only for a single project - -![Overview](./images/att6_2384.png) - -### How to Share in Bulk - -Bulk sharing is available when multi-select mode is enabled. - -1. Navigate to the **Tests** page -2. Enable **Multi-select** mode -3. Select multiple tests, suites, or folders -4. Click **Share** button at the toolbar -5. Choose a target project(s) -6. Select the destination -7. Click the **Share** button - -![Bulk Share](./images/att1_2384.png) - -All selected items will be shared at once and follow the same shared rules. - -### How to Re-share Shared Items - -Tests and suites that were already shared to a project can be shared again to other projects. - -When an item is re-shared: - -- Original source remains the same (**Single Source of Truth**) -- Editing is still allowed only in the original source project -- For both initially shared and re-shared items, the same indicator shows the original source project - -Learn more about the [sharing process here](https://docs.testomat.io/project/tests/other-features-for-test-case-design/#how-to-share-a-single-item). - -### How Execution History Works for Shared Tests - -Shared tests remain linked to the source project, but execution context is always project-specific. - -- Running a shared test or suite in a target project creates a local run -- Logs, statuses, and results are tracked only in that project - -This ensures teams can reuse test logic while keeping execution data isolated and meaningful for each project, while still reflecting updates to the source test where relevant. - -![Excute shared tests](./images/gif2_2384.gif) - -:::note - -If a test run is in progress, and the source test is updated (e.g., its description is changed), the update is applied across all linked projects. - -::: - -### Unlinking Shared Items - -Unlinking breaks the connection to the source project, making the item fully editable in the target project. - -1. Open the shared test, suite, or folder in the target project -2. Click the **More options** button -3. Select **Unlink share** button - -![Unlink share](./images/gif1_2384.gif) - -After unlinking: - -- it is no longer updated from the source project -- the Single Source of Truth relationship is removed -- the item behaves as a local project entity and can be modified freely -- a log entry appears in the **History**, indicating that the item was unlinked from the shared source - -Use unlinking only when a test or suite must diverge from its source version. - -### Best Practices - -- Treat the source project as a **Single Source of Truth**. -- Use shared tests for stable, reusable flows (smoke, regression, core scenarios). -- Unlink shared items only when necessary. diff --git a/src/content/docs/project/tests/restoring-deleted-tests.md b/src/content/docs/project/tests/restoring-deleted-tests.md new file mode 100644 index 00000000..3c07c56b --- /dev/null +++ b/src/content/docs/project/tests/restoring-deleted-tests.md @@ -0,0 +1,54 @@ +--- +title: Restoring Deleted Tests +description: Restore deleted tests and suites from the Trash Bin in Testomat.io. Deleted tests and suites are kept for 90 days. +type: article +url: https://docs.testomat.io/project/tests/restoring-deleted-tests +head: + - tag: meta + attrs: + name: keywords + content: trash bin, restore deleted test, restore suite, recover test case, revisions, 90 days, Pulse, Testomat.io +--- + +Deleted tests and suites are kept in the **Trash Bin** for 90 days. If you delete something by mistake, you can restore it without creating the test again. + +## Restore a Test or Suite + +1. Go to the **Tests** page. +2. Open the **Trash Bin** from the (`...`) menu. + +![Trash Bin option in the actions menu](./images/restoring-deleted-tests/1-trash-bin.png) + +In the trashbin window: + +1. Find the deleted test or suite. +2. Click **Restore**. + +![Trash Bin with the Restore button next to a deleted test](./images/restoring-deleted-tests/2-restore.png) + +The item returns to the test tree in the same place it was before deletion. + +:::note + +Tests and suites are kept for 90 days. After that, they are permanently removed. + +::: + +## Find Out What Was Deleted + +If you are not sure what happened to a test or suite, check **Pulse** first. It shows project activity, including deletions, so you can see what was changed and when. See [Pulse](https://docs.testomat.io/project/pulse). + +## Deleted Attachments + +Attachments have a separate retention period and are restored from the **Attachments** tab, not the **Trash Bin**. + +| Item | Kept for | Restore from | +| --- | --- | --- | +| Tests and suites | 90 days | **Trash Bin** | +| Attachments | 30 days | **Attachments** tab | + +## Next Steps + +- [Move Tests](https://docs.testomat.io/project/tests/move-tests) +- [Test Attachments](https://docs.testomat.io/project/tests/test-attachments) + diff --git a/src/content/docs/project/tests/sharing-tests-and-suites.md b/src/content/docs/project/tests/sharing-tests-and-suites.md new file mode 100644 index 00000000..0be2007b --- /dev/null +++ b/src/content/docs/project/tests/sharing-tests-and-suites.md @@ -0,0 +1,175 @@ +--- +title: Sharing Tests and Suites +description: Share a test, suite, or folder from one Testomat.io project to others so the test logic stays the same everywhere while runs stay local. Covers permissions, what is shared, sharing many items at once, re-sharing, and unlinking. +type: article +url: https://docs.testomat.io/project/tests/sharing-tests-and-suites +head: + - tag: meta + attrs: + name: keywords + content: share tests, share suite, share folder, single source of truth, read-only tests, unlink share, re-share, shared projects, Testomat.io +--- + +Share a test, suite, or folder when you want to use the same test in several projects without creating separate copies. + +One project remains the source of the shared test. Other projects use it as read-only content, while each project keeps its own test runs and results. + +![One source project owns the test, and every linked project uses it as read-only with its own runs](./images/sharing-tests-and-suites/one-source-many-projects.png) + +Use **Share** when the test should stay the same across projects. Use [Copying Tests and Suites](https://docs.testomat.io/project/tests/copying-tests-and-suites) when each project needs its own version. + +:::note + +Folders are used to organize shared content. The folder itself is not shared, but the tests and suites inside it can be. + +::: + +## Sharing Rules + +A shared test follows a few simple rules: + +- The source project owns the test content. +- The test is read-only in other projects. +- Each project keeps its own runs, results, and history. +- You can share the same test with multiple projects. +- Projects must use the same test type: BDD with BDD or Classical with Classical. + +:::note + +Share is available on Professional, Enterprise, and Trial plans. + +::: + +## Allow Your Team to Share Tests + +By default, only Owners and Managers can share tests and suites. You can allow all project members to use sharing. + +1. Go to **Settings** in the sidebar. +2. Select **Project**. +3. Toggle the **Share to other projects** switch on. + +![Sharing setting on the Project settings page](./images/sharing-tests-and-suites/1-sharing-settings.png) + +The **Sharing** block also holds **Share Living Docs** and **Enable Public Report**. These are separate features - see [Living Documentation](https://docs.testomat.io/advanced/living-doc) and [Share Report Publicly](https://docs.testomat.io/project/runs/reports#share-report-publicly). + +| Setting | Who can share | +| --- | --- | +| **On** | All project members | +| **Off** | Owners and Managers | + +Only Owners and Managers can change this setting. + +## Shared Test Data + +When you share a test, its test content becomes available in the target project. Run-related information stays in the project where it was created. + +![Test content travels to the linked projects, while runs, history, and comments stay in each project](./images/sharing-tests-and-suites/what-travels-what-stays.png) + +| Data | Shared? | +| --- | --- | +| Title and description | Yes | +| Attachments | Yes | +| Labels and custom labels | Yes | +| Tags | Yes | +| Priority | Yes | +| Linked issues | Yes, when the integration is available | +| Assignee | Yes, when the user exists in the target project | +| Test author | Yes, when the user exists in the target project | +| Runs and results | No | +| History | No | +| Requirements | No | +| Comments | No | + +## Synchronized Fields + +After the first share, changes to title, description, and tags are synchronized from the source project to all linked projects. + +New tests added to a shared suite are also available in linked projects. + +Other shared fields are not updated after the initial share. + +:::note + +Shared tests are read-only in target projects. To edit a shared test there, you must first unlink it. + +::: + +## Share a Test, Suite, or Folder + +1. Go to the **Tests** page in the source project. +2. Open the test, suite, or folder you want to share. +3. Click (`...`). +4. Select **Share to other projects**. +5. Choose **Other project** for one project or **Bulk selection project** for several projects. +6. Select the target project or projects. +7. Click **Share**. + +![Share with other projects option in a test](./images/sharing-tests-and-suites/2-share-test-with-other-projects.png) + +The shared item appears in the selected projects as read-only. + +:::note + +Suites and folders shared in bulk are added to the **Root** of the target project. A single test can be shared with one project at a time. + +::: + +## Share Several Items + +Use bulk sharing when you want to share multiple tests, suites, or folders at once. + +1. Go to the **Tests** page. +2. Select the items you want to share. +3. Click **Share** in the toolbar. +4. Select the target projects. +5. Select the destination. +6. Click **Share**. + +![Sharing multiple tests](./images/sharing-tests-and-suites/3-sharing-multiple-tests.png) + +All selected items are shared using the same settings. + +## Share an Item With More Projects + +You can share an item that is already shared with additional projects. The original source project remains the owner. The new project connects directly to that original source. + +This means sharing does not create a chain between projects. All linked projects use the same source. + +## Run Shared Tests + +Sharing the test content does not share its run history. When you run a shared test in another project, Testomat.io creates a run in that project. Its logs, status, and results stay there. + +This lets different projects use the same test while keeping their own testing history. + +:::note + +If the source test changes while a run is in progress, updates to the shared test content are applied to the linked projects. + +::: + +## Unlink a Shared Test + +Unlink a test when you want to make it independent from the source project. + +:::caution + +Unlinking is permanent for that connection. If you want the same test to stay synchronized with the source, keep it shared. + +::: + +1. Open the shared test, suite, or folder in the target project. +2. Click (`...`). +3. Select **Unlink share**. + +After unlinking: + +- the item no longer receives updates from the source +- it becomes editable in the current project +- it works as a local test, suite, or folder +- the unlink action is recorded in **History** + +## Next Steps + +- [Test URL and ID](https://docs.testomat.io/project/tests/test-url-and-id) +- [Suites and Folders](https://docs.testomat.io/project/tests/suites-and-folders) + \ No newline at end of file diff --git a/src/content/docs/project/tests/suites-and-folders.md b/src/content/docs/project/tests/suites-and-folders.md index 50ecbe46..504f3b07 100644 --- a/src/content/docs/project/tests/suites-and-folders.md +++ b/src/content/docs/project/tests/suites-and-folders.md @@ -98,5 +98,5 @@ You can now add other suites to the folder. ## Next Steps - [Create a Test](https://docs.testomat.io/project/tests/create-a-test) -- [Copy and Move your Tests](https://docs.testomat.io/project/tests/copy-and-move-your-tests) -- [Other Features for Test case Design](https://docs.testomat.io/project/tests/other-features-for-test-case-design) \ No newline at end of file +- [Copying Tests and Suites](https://docs.testomat.io/project/tests/copying-tests-and-suites) +- [Sharing Tests and Suites](https://docs.testomat.io/project/tests/sharing-tests-and-suites) \ No newline at end of file diff --git a/src/content/docs/project/tests/tags-labels-and-assignees.md b/src/content/docs/project/tests/tags-labels-and-assignees.md index 9f8b5d43..1666aff3 100644 --- a/src/content/docs/project/tests/tags-labels-and-assignees.md +++ b/src/content/docs/project/tests/tags-labels-and-assignees.md @@ -91,7 +91,7 @@ Assigning a test in a run does not change its test assignment. ## Next Steps -- [Create a Test](./create-a-test.md) -- [Test Attachments](./test-attachments.md) +- [Create a Test](https://docs.testomat.io/project/tests/create-a-test) +- [Test Attachments](https://docs.testomat.io/project/tests/test-attachments) - [Tags](https://docs.testomat.io/advanced/tags-labels/tags/) \ No newline at end of file diff --git a/src/content/docs/project/tests/test-attachments.md b/src/content/docs/project/tests/test-attachments.md index 7503d634..1528e915 100644 --- a/src/content/docs/project/tests/test-attachments.md +++ b/src/content/docs/project/tests/test-attachments.md @@ -106,7 +106,7 @@ Deleted attachments stay available for **30 days**, so you can restore one if yo 3. Click the **Delete** icon. 4. Confirm the deletion. -### From edit mode +### From Edit Mode 1. Open the test and click **Edit**. 2. Open the **Attachments** tab. diff --git a/src/content/docs/project/tests/test-priority.md b/src/content/docs/project/tests/test-priority.md index c2faed6a..5022c019 100644 --- a/src/content/docs/project/tests/test-priority.md +++ b/src/content/docs/project/tests/test-priority.md @@ -122,7 +122,7 @@ For more information, see [Analytics Dashboards (Widgets)](https://docs.testomat ## Next Steps -- [Tags, Labels, and Assignees](./tags-labels-and-assignees.md) -- [Create a Test](./create-a-test.md) +- [Tags, Labels, and Assignees](https://docs.testomat.io/project/tests/tags-labels-and-assignees) +- [Create a Test](https://docs.testomat.io/project/tests/create-a-test) - [Bulk Edit](https://docs.testomat.io/advanced/bulk-edit-folder) diff --git a/src/content/docs/project/tests/test-tree-display.md b/src/content/docs/project/tests/test-tree-display.md new file mode 100644 index 00000000..f96a6d90 --- /dev/null +++ b/src/content/docs/project/tests/test-tree-display.md @@ -0,0 +1,53 @@ +--- +title: Test Tree Display +description: Adjust the Tests page in Testomat.io by hiding tests in the tree, pinning the sidebar, or previewing tests from another branch. +type: article +url: https://docs.testomat.io/project/tests/test-tree-display +head: + - tag: meta + attrs: + name: keywords + content: display settings, hide tests in tree, pin sidebar, test tree, branch preview, navigation, Testomat.io +--- + +Adjust the **Tests** page to make your test tree easier to work with. Open the **Display** menu at the top of the **Tests** page to: + +- hide individual tests from the tree +- keep the sidebar open while you work + +![The Display menu with the Hide tests in tree and Pin sidebar toggles](./images/test-tree-display/1-display-menu.png) + +These settings only change your view. They do not change the tests or affect other team members. + +## Hide Tests in the Tree + +Hide individual tests when you want to see a simpler project structure. By default the tree lists every test inside its suite. + +![The test tree with every test listed inside its suite](./images/test-tree-display/2-tests-unhidden.png) + +With **Hide tests in tree** enabled, the tree shows only folders and suites. Tests are hidden from the tree but remain available in the project. + +This is useful when you have many tests and want to focus on the project structure. + +To show the tests again, open **Display** and turn off **Hide tests in tree**. + +## Pin the Sidebar + +Pin the sidebar when you want to see the test tree while working with a test or suite. You can pin it in either of these ways: + +- Click the **Pin** icon in the top-right corner of the test or suite panel. +- Open **Display** and turn on **Pin sidebar**. + +![The pinned sidebar: the test tree on the left, the test details on the right, and the toolbar still at the top](./images/test-tree-display/3-toolbar-pinned.png) + +When the sidebar is pinned, the test tree stays visible next to the test or suite details. The **Tests** page toolbar, including search, filters, and display settings, also stays available. + +Turn it off when you want more space for the test details. + +![The test tree with tests hidden and only folders and suites shown](./images/test-tree-display/4-tests-hidden.png) + +## Next Steps + +- [Suites and Folders](https://docs.testomat.io/project/tests/suites-and-folders) +- [Bulk Test Selection](https://docs.testomat.io/project/tests/bulk-test-selection) + diff --git a/src/content/docs/project/tests/test-url-and-id.md b/src/content/docs/project/tests/test-url-and-id.md new file mode 100644 index 00000000..f2fc2f14 --- /dev/null +++ b/src/content/docs/project/tests/test-url-and-id.md @@ -0,0 +1,56 @@ +--- +title: Test URL and ID +description: Copy the URL or ID of a test, suite, or run in Testomat.io and set your preferred format for quick copying. +type: article +url: https://docs.testomat.io/project/tests/test-url-and-id +head: + - tag: meta + attrs: + name: keywords + content: test ID, test URL, copy ID, copy link, quick copy, suite ID, run ID, Testomat.io +--- + +Every test, suite, and run has its own ID and URL. The **Copy** window offers them in four formats, so you can pick the one that fits where you are pasting. + +| Format | Looks like | Best for | +| --- | --- | --- | +| **URL** | `https://app.testomat.io/projects/my-project/test/62b223e8-rich-editor` | Sharing the item outside Testomat.io | +| **@TID** | `@T62b223e8` | Cross-links inside a test or suite description | +| **ID** | `62b223e8` | Places where the `@T` prefix is not wanted | +| **Markdown** | `[@T62b223e8](https://app.testomat.io/projects/my-project/test/62b223e8)` | Tickets, chats, and commit messages that render Markdown | + +## Copy a URL or ID + +1. Open the test, suite, or run. +2. Click the copy icon next to the ID at the top of the panel. +3. Click the copy icon on the row with the format you need. + +![The Copy window with the URL, @TID, ID, and Markdown formats](./images/test-url-and-id/1-copy-test-id-url.png) + +The **Title** and **Description** buttons at the bottom copy the item title and its description. + +## Set a Default Format + +If you usually copy the same format, set it as the default. + +1. Open the **Copy** window. +2. Turn on the toggle next to the format you use most often. + +After that, clicking the ID copies your selected format immediately. + +## Link Tests and Suites + +When you paste a copied **@TID** into a test or suite description, Testomat.io turns it into a clickable cross-link with a preview. + +- **Classical projects:** paste the **@TID** directly. +- **BDD projects:** add `#` before the ID. + +![Copy an @TID, paste it into another description, and it becomes a clickable cross-link](./images/test-url-and-id/paste-an-id-get-a-link.png) + +See [Classical Project](https://docs.testomat.io/project/tests/classical-test-case-editor) and [BDD Project](https://docs.testomat.io/project/tests/bdd-test-case-editor). + +## Next Steps + +- [Sharing Tests and Suites](https://docs.testomat.io/project/tests/sharing-tests-and-suites) +- [Bulk Test Selection](https://docs.testomat.io/project/tests/bulk-test-selection) + diff --git a/src/content/docs/project/tests/undetaching-tests.md b/src/content/docs/project/tests/undetaching-tests.md new file mode 100644 index 00000000..5858e7ce --- /dev/null +++ b/src/content/docs/project/tests/undetaching-tests.md @@ -0,0 +1,82 @@ +--- +title: Undetaching Tests +description: Restore detached tests in Testomat.io after an import no longer finds them. Undetach all detached tests in a project, a suite, or a single test. +type: article +url: https://docs.testomat.io/project/tests/undetaching-tests +head: + - tag: meta + attrs: + name: keywords + content: detached tests, undetach tests, test state, manual test, automated test, failed import, Testomat.io +--- + +When an import no longer finds an automated test in your source code, Testomat.io marks the test as **Detached**. + +The test stays in your project. If the test is still needed, you can **Undetach** it and remove the **Detached** state. + +## Understand Test States + +Each test has a state that shows how it is used: + +| State | What it means | +| --- | --- | +| **Manual** | The test is run manually and is not connected to automation code. | +| **Automated** | The test is connected to automation code imported into Testomat.io. | +| **Detached** | The test was imported before, but the latest import did not find it in the source code. | + +For example, a change in your automation project can cause an imported test to become **Detached**. The test is still there, so you can decide what to do with it. + +## Undetach All Detached Tests + +If an import detached many tests, you can restore them all at once. + +1. Go to the **Tests** page. +2. Open the **Detached** tab. +3. Click **Undetach tests** in the banner. + +![The Undetach tests banner on the Tests page filtered by Detached](./images/undetaching-tests/1-undetach-tests.png) + +Testomat.io removes the **Detached** state from all detached tests in the project. + +:::note + +This action applies to all detached tests in the project, not only the tests shown on the **Detached** tab. + +::: + +The banner also offers **Delete detached tests**. Use it only when the tests are gone from your source code for good - it removes them instead of restoring them. + +## Undetach a Suite + +If only one suite needs to be restored: + +1. Open the suite with detached tests. +2. Click the (`...`) menu in the top-right corner. +3. Click **Clear "Detached" state**. + +![Undetach option in the suite menu](./images/undetaching-tests/2-clear-detached-state.png) + +All detached tests in the suite are restored. + +## Undetach a Single Test + +To restore just one test: + +1. Open the detached test. +2. Click the (`...`) menu in the top-right corner. +3. Click **Clear "Detached" state**. + +The **Detached** state is removed from the test. + +:::note + +If the test no longer has automation code, undetaching it changes the test to **Manual**. If automation code is available again, the test can be connected through a later import. + +::: + +## Next Steps + +- [Test Tree Display](https://docs.testomat.io/project/tests/test-tree-display) +- [Restoring Deleted Tests](https://docs.testomat.io/project/tests/restoring-deleted-tests) +- [Import Tests From Source Code](https://docs.testomat.io/project/import-export/import/import-tests-from-source-code) + \ No newline at end of file