testeiya 0.2.1 → 0.3.10

package/skills/testeiya/testomatio-docs/docs/project/import-export/export-tests/download-manual-tests-as-files.md

@@ -1,378 +0,0 @@
----
-title: Download Manual Tests as Files
-description: Learn how to manage manual tests using Git version control by exporting them from Testomat.io as Markdown files. This guide details how to export tests, track changes locally, write and update tests using a code editor, and then seamlessly import changes back into Testomat.io using the CLI. This workflow aligns manual testing with modern DevOps practices, offering full history, branching, and collaborative editing benefits.
-type: article
-url: https://docs.testomat.io/project/import-export/export-tests/download-manual-tests-as-files
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Export to Markdown, Testomat.io, manual tests, Git repository, version control, import from Markdown, CLI, track changes, Markdown files, mixed projects, create new tests, update existing tests, bulk edit, delete tests, change project structure, test management, export, import, Markdown Support.
----
-
-## Export & Version Control Manual Tests in Git (Markdown Support)
-
-You can now **export your manual tests as Markdown files directly into your Git repository** and keep them under version control by using **'Export to Markdown'** feature.
-
-This allows your team to write, edit, and track changes to manual test cases just like code — with full history, branching, and collaboration benefits that Git offers.
-
-**Key benefits:**
-
-- **Export manual tests to Markdown** – keep human-readable test cases in your repository.
-- **Import manual tests via CLI** – instantly sync Markdown changes from Git into Testomat.io.
-- **Version control for manual tests** – review, revert, and track changes over time.
-- **Write and modify in your editor** – use your favorite IDE to create or update test cases.
-
-## How to Export Manual Tests to Markdown
-
-To begin managing your manual test cases as files:
-
-1. Create a directory on your computer where you want to export the tests.
-
-![Testomatio - Export to markdown](./images/Export_as_markdown_1.png)
-
-2. Open Terminal with the created project directory.
-
-![Testomatio - Export to markdown](./images/Export_as_markdown_2.png)
-
-3. Open your project in Testomat.io on **'Tests'** page.
-4. Click **'Extra menu'** button.
-5. Select **'Export to markdown'** option.
-
-![Testomatio - Export to markdown](./images/Export_as_markdown_3.png)
-
-6. Select your OS from the dropdown list.
-7. Copy the displayed pull command.
-
-![Testomatio - Export to markdown](./images/Export_as_markdown_4.png)
-
-8. Run the export command in your project directory to download tests from Testomat.io.
-
-![Testomatio - Export to markdown](./images/Export_as_markdown_5.png)
-
-Congrats! Your tests are downloaded from Testomat.io and created in Markdown format. 
-
-![Testomatio - Export to markdown](./images/Export_as_markdown_6.png)
-
-Now you can find your project in the previously created folder.
-
-![Testomatio - Export to markdown](./images/Export_as_markdown_7.png)
-
-**What Gets Exported?**
-
-- All test suites and tests from your current project.
-- Test IDs, descriptions, priorities, labels, tags and structure are preserved in the generated files.
-
-To continue working with your manual test cases and manage them locally as files, it’s highly recommended to use **Git Version Control**.
-
-In order to do this, you need:
-
-1. Open the directory with exported tests in your text editor.
-
-![Testomatio - Export as markdown](./images/Export_as_markdown_8.png)
-
-![Testomatio - Export as markdown](./images/Export_as_markdown_9.png)
-
-2. Run `git init` command in the Terminal.
-3. Go to **'Source control'** tab in your editor.
-4. Stage all changes.
-5. Click **'Commit'** button.
-
-![Testomatio - Export as markdown](./images/Export_as_markdown_10.png)
-
-6. Confirm your action to commit changes.
-
-![Testomatio - Export as markdown](./images/Export_as_markdown_11.png)
-
-![Testomatio - Export as markdown](./images/Export_as_markdown_12.png)
-
-Your tests now reside right next to your application code in Git, so you can start updating exported suites and test cases, adding new ones, or deleting irrelevant tests.
-
-![Testomatio - Export as markdown](./images/Export_as_markdown_13.png)
-
-## User Scenario for Export to Markdown
-
-Imagine you’re working on a new product release and your QA team collaborates closely with developers.
-Instead of switching back and forth between Testomat.io and your code editor, the **manual test cases** live right next to your application code in Git.
-
-- A developer spots a missing step in a test case and updates the Markdown file in their branch.
-- The change is committed, reviewed in a pull request, and merged into main.
-- The updated test case is automatically synced back into Testomat.io via CLI.
-
-This workflow makes test case management seamless, collaborative, and fully traceable — aligning your manual testing process with modern DevOps practices.
-
-## User Scenario for Mixed Projects
-
-If you are working on a Mixed project (have both manual and automation tests), with **Export to Markdown** feature you can export your manual tests to the same directory as your automation tests. This will allow you to manage all tests in one place.
-
-## Folder Naming and Normalization Rules
-
-When organizing your projects, ensure that folder names adhere to the following naming conventions to maintain compatibility during import and export processes.
-
-**In folder names, you can use:**
-**Allowed Characters**
-- Any Unicode letters (Multiple languages supported).
-- Digits (0-9).
-- Spaces.
-- Underscore `_`.
-- Hyphen `-`.
-- Dot `.`.
-
-**Prohibited Characters:** All other special characters or symbols not listed above are strictly forbidden.
-
-**Automatic Normalization**
-To ensure consistent file paths, Testomat.io applies the following normalization rules:
-- **Consolidation:** Multiple consecutive spaces, underscores, hyphens, or dots are transformed into a single entity. (Example: `...` becomes `.`).
-- **Trimming:** Any spaces, underscores, or dots at the beginning or end of a folder name are automatically removed.
-
-:::note
-
-Visit [Classical Tests Markdown Format](https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format/) page to read about the correct structure for your suites and tests in the markdown format.
-
-:::
-
-## What You Can Do with Tests Exported as Files
-
-After your project is downloaded to Markdown you can:
-
-- Create new tests and suits.
-- Update existing tests, including using **Bulk Edit** to modify multiple tests (add/change tags, labels, custom fields, assignee or priority).
-- Delete tests that are no longer relevant.
-- Change Project structure.
-- Work with Dynamic parameters.
-
-### Create New Suites/Tests
-
-Each suite is represented as a single markdown file. All metadata is written as inside comments.
-
-To create a new test in a file, you need to add:
-
-1. The **Test Header** (required)
-
-```
-<!-- test -->
-```
-
-**Test Header** elements can include:
-
-- **Email of test creator** (if not added, defaults to 'Unknown user').
-- **Priority**: low, normal, high, important, ctitical (if not set up, defaults to 'normal').
-- **Tags** (optional) - can be added in the header or test title. You can create and add new Tags, or use existing.
-- **Labels and Custom Fields** (optional) - can only be added in the header. **Important!** You can only use Labels and Custom fields that already exist 
-
-in your project.
-
-2. Test title (Starts with `#`).
-3. Test description with Requirements, Pre-conditions, Steps and Expected Results in Markdown format.
-
-:::note
-
-Don't add the ID as it will be created automatically after tests are synced into Testomat.io.
-
-:::
-
-**Example of structure for Test Case:**
-
-```
-<!-- test
-priority: high
-creator: creator_email@gmail.com
-tags: @user, @update
-labels: smoke
--->
-
-# Test Title
-
-### Requirements
-
-### Steps
-
-1. Step 1
-  **Expected Result**: For Step 1.
-
-2. Step 2
-  **Expected Result**: For Step 2.
-
-3. Step 3
-  **Expected Result**: For Step 3.
-```
-
-![Testomatio - Export as markdown](./images/Add_test_markdown_1.png)
-
-The **Header** for Suites has a similar format:
-
-```
-<!-- suite
-emoji: 
-labels:
--->
-```
-### Update Existing Suites/Tests
-
-Update the description for an existing suite/test in the markdown format.
-If you need to change/add a specific Step, Pre-condition, Priority, Tags, Labels, etc. for multiple tests, you can do this using **Bulk edit**.
-
-![Testomatio - Export as markdown](./images/Bulk_edit_test_markdown_1.gif)
-
-:::note
-
-Avoid renaming folders or suites within the directory structure, as this may disrupt the Project structure upon import. To change a suite name, edit it within the Markdown file header or directly in Testomat.io.
-
-:::
-
-![Testomatio - Export as markdown](./images/Rename_test_markdown_1.png)
-
-| **Suite Name Before**             | **Suite Name After**             |
-| --------------------------- | ------------------------------------- |
-| ![Testomatio - Export as markdown](./images/Suite_name_before.png) | ![Testomatio - Export as markdown](./images/Suite_name_after.png) |
-
-### Delete Irrelevant Tests
-
-Simply delete the irrelevant suites/tests from the file and save the changes before the import process.
-
-### Change Project Structure
-
-Project structure **cannot** be modified by moving folders or suites within the directory structure. Only **individual test cases** can be moved between suites in the Markdown file. After the import, changes will be displayed on Testomat.io side.
-
-:::note
-
-If you modify the project structure directly within Testomat.io after an initial Markdown export, clear your local directory and perform a fresh pull to ensure files remain synchronized.
-
-:::
-
-### How to Work with Dynamic Parameters
-
-To create a test case with **Dynamic Parameters** in a markdown file, you need to add them in the markdown format.
-
-1. Add an **'Example'** section at the end of your test case using the markdown format:
-```
-<!-- example -->
-```
-2. Assign headers for parameters and dynamic parameters for testing in the table structure.
-```
-| Header 1 | Header 2 |
-| --- | --- |
-| Param name 1 | Param name 2 |
-| Param name 3 | Param name 4 |
-```
-**Example of structure for Test Case with Dynamic Parameters:**
-
-![Testomatio - Export as markdown](./images/Export_dynamic_param_1.png)
-
-:::note
-
-**Character Limit:** If a parameter name exceeds 250 characters, it will be truncated on UI (only the first 247 characters will be displayed).
-
-**Parameter Order:** The order of parameters cannot be manually changed within the markdown file. On the UI, they are always displayed by the latest IDs assigned during the import from markdown to Testomat.io.
-
-**Synchronization:** While the order in the markdown file and on the UI might not match initially after an import, the order will be synchronized once you export them back from Testomat.io to a markdown file (the exported file will match the UI order).
-
-:::
-
-For more information about **Dynamic Parameters** follow the [link](https://docs.testomat.io/project/tests/test-case-creation-and-editing/#how-to-add-dynamic-parameters-to-a-test).
-
-## How to Import Manual Tests from Markdown
-
-Once you have finished updating the test cases in the file system, use the **'Import from Markdown'** feature to import all the changes into Testomat.io.
-
-:::note
-
-Before importing your tests back to Testomat.io you must:
-
-1. **Save** and **commit** your changes.
-
-2. **Pull latest changes** from Testomat.io before importing to avoid accidentally overwriting data inside Testomat.io. First, run the same command that you used for exporting tests `npx check-tests@latest pull` to pull your tests and fetch latest data from Testomat.io. Verify all changes. Then you can upload them back. In case you use Git, this would be the safest way to deal with tests. Alternatively, you can use `--force option`.
-
-:::
-
-To **'Import from Markdown'** you need:
-
-1. Open your project in Testomat.io on **'Tests'** page.
-2. Click **'Extra menu'** button.
-3. Select **'Import from markdown'** option.
-
-![Testomatio - Import from markdown](./images/Import_from_markdown_1.png)
-
-4. On the displayed **'Import Project from Source Code'** page select **'Manual tests (markdown files)'** from the **'Project Framework'** dropdown list.
-
-![Testomatio - Import from markdown](./images/Import_from_markdown_2.png)
-
-5. Select **'Markdown'** option from the **'Project Language'** dropdown list for a **Classical Project**.
-6. Select your OS from the dropdown list.
-7. Copy the displayed push command.
-
-![Testomatio - Import from markdown](./images/Import_from_markdown_3.png)
-
-8. Run the import command in your project directory to sync tests back to Testomat.io.
-
-After your tests are imported back to Testomat.io, all new tests will be automatically synced to the project without additional confirmation and all updated tests will be displayed with **'out of sync'** label and will required confirmation from your side. You can use **'Out of Sync'** filter to find all of them, so you can verify and save the changes.
-
-Each test with **'out of sync'** label should be verified manually one by one.
-
-**To check and save changes for updated tests:**
-
-1. Click on **'Out of Sync'** label.
-
-![Testomatio - Import from markdown](./images/Out_of_Sync_1.png)
-
-2. Open the test you want to check.
-3. Click **'Compare Description'**.
-
-![Testomatio - Import from markdown](./images/Out_of_Sync_2.png)
-
-4. There are 2 options on this Step:
-- Click **'Revert to Previous'** button if you want to cancel the changes.
-
-OR
-
-- Click **'Keep Current'** button if you want to save the changes.
-
-![Testomatio - Import from markdown](./images/Out_of_Sync_3.png)
-
-:::note
-
-By clicking on **'Mark as Sync'** button you can sync the test with the latest changes.
-
-![Testomatio - Import from markdown](./images/Out_of_Sync_4.png)
-
-:::
-
-### Importing Automated Tests as Manual
-
-If you maintain only automated test cases or both, manual and automated, within the same source files (e.g., in a single .feature file), but you want to import your automated tests as manual, you can use the **'Additional Settings'** during import to ensure these tests are correctly mapped and synchronized within Testomat.io.
-
-**To use this feature:**
-
-1. Go to the **Import Project from Source Code** menu: select your **Project Framework**, **Project Language** and **OS**.
-2. Click on **'Additional Settings'**.
-
-![Testomatio - Import from markdown](./images/Auto_to_manual_1.png)
-
-3. In the field **'Import automated tests as manual when a test is marked with a tag'**, enter the dedicated tag you use in your code for tests that should be imported as manual tests (e.g., `@manual`, `@smoke`, etc.).
-4. Copy the displayed import command from Testomat.io, for example:
-`TESTOMATIO=tstmt_... npx check-tests@latest codeceptjs "**/*.js"`
-
-5. Click the **'Finish'** button.
-
-![Testomatio - Import from markdown](./images/Auto_to_manual_2.png)
-
-6. Run coppied import command in the terminal.
-
-![Testomatio - Import from markdown](./images/Auto_to_manual_3.png)
-
-7. Verify the state of imported tests.
-
-| **Tests State Before = Automated**             | **Tests State After = Manual**             |
-| --------------------------- | ------------------------------------- |
-| ![Testomatio - Import from markdown](./images/Auto_to_manual_before.png) | ![Testomatio - Import from markdown](./images/Auto_to_manual_after.png) |
-
-:::note
-
-**Single State Rule:** A test can have only one state: **manual** or **automated**. It cannot hold both statuses simultaneously in Testomat.io.
-
-**Applicability:** This feature works for both **BDD** and **Classical** project types.
-
-**Scope:** The setting is applicable to both **individual tests** and **entire suites**.
-
-
-:::

package/skills/testeiya/testomatio-docs/docs/project/import-export/export-tests/export-to-obsidian.md

@@ -1,112 +0,0 @@
----
-title: Export Tests to Obsidian
-description: Export manual tests from Testomat.io as Markdown files and open them in Obsidian as a vault. Browse, search, edit test cases in Obsidian and push changes back to Testomat.io using the CLI.
-type: article
-url: https://docs.testomat.io/project/import-export/export-tests/export-to-obsidian
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/obsidian_logo.svg
-  - tag: meta
-    attrs:
-      name: og:title
-      content: Export Tests to Obsidian | Testomat.io
-  - tag: meta
-    attrs:
-      name: og:description
-      content: Export manual tests from Testomat.io as Markdown and manage them in Obsidian. Edit test cases, sync changes, and keep your test documentation in a knowledge base.
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, export tests, Obsidian, vault, Markdown, manual tests, export to markdown, knowledge base, test documentation, test management, edit tests, sync tests, CLI, check-tests
----
-
-[Obsidian](https://obsidian.md) is a powerful knowledge base application that works on top of plain Markdown files. Since Testomat.io can export manual tests as Markdown, you can use Obsidian to browse, search, and organize your test cases locally.
-
-## How to Export Tests to Obsidian
-
-### Step 1: Export Tests as Markdown
-
-First, export your manual tests from Testomat.io as Markdown files using the **Export to Markdown** feature:
-
-1. Create a directory on your computer where you want to store the tests.
-2. Open your project in Testomat.io on the **Tests** page.
-3. Click the **Extra menu** button.
-4. Select **Export to markdown**.
-5. Select your OS and copy the displayed pull command.
-6. Run the export command in your project directory.
-
-For detailed export instructions, see [Download Manual Tests as Files](../download-tests-as-files/download-manual-tests-as-files).
-
-### Step 2: Open the Folder as an Obsidian Vault
-
-Once the tests are exported, open the folder directly in Obsidian:
-
-1. Open **Obsidian**.
-2. Click the **Open another vault** button (vault icon in the bottom-left corner) or go to **File → Open vault**.
-3. Select **Open folder as vault**.
-4. Navigate to the folder containing your exported Markdown tests and click **Open**.
-
-All your test suites and test cases will appear in Obsidian immediately — no copying or importing is needed. Obsidian reads `.md` files directly from the folder.
-
-![Testomat.io tests opened in Obsidian vault](./images/obsidian_vault_tests.png)
-
-### Step 3: Browse Your Tests
-
-Once the vault is open, you can:
-
-- **Navigate the test tree** using the file explorer sidebar — folders represent suites.
-- **Search across all tests** using Obsidian's built-in search (`Ctrl+Shift+F` / `Cmd+Shift+F`).
-- **Use graph view** to visualize connections between test suites and cases.
-- **Tag filtering** — if your tests include tags, Obsidian will recognize them for filtering.
-
-## Editing Tests in Obsidian
-
-You can edit and update your test cases directly in Obsidian. Any changes you make to the Markdown files — updating steps, adding preconditions, changing tags or priorities — will be picked up when you push the changes back to Testomat.io.
-
-When editing tests, keep the existing Markdown structure intact:
-
-- **Test headers** (`<!-- test -->` comments) contain metadata like priority, tags, and labels.
-- **Test titles** start with `#`.
-- **Steps and expected results** follow the standard Markdown format.
-
-You can also create new test files or delete irrelevant ones. For details on test file structure, see [Download as Markdown Files](../download-tests-as-files/download-manual-tests-as-files).
-
-### Pushing Changes Back to Testomat.io
-
-Once you've finished editing, push your changes back to Testomat.io using the CLI. You will need your project's **TESTOMATIO** API key, which can be found in your project **Settings → API Key**.
-
-Run the following command in the directory with your tests:
-
-```bash
-TESTOMATIO={your-api-key} npx check-tests@latest push
-```
-
-:::note
-
-Before pushing, it's recommended to **pull the latest changes first** to avoid overwriting updates made in Testomat.io:
-
-```bash
-TESTOMATIO={your-api-key} npx check-tests@latest pull
-```
-
-Review any differences, then push your changes.
-
-:::
-
-After the push, new tests will be added to your project automatically. Updated tests will appear with an **'out of sync'** label in Testomat.io, where you can review and confirm each change.
-
-## Keeping Tests in Sync
-
-To update your Obsidian vault with the latest tests from Testomat.io, re-run the pull command in the same directory:
-
-```bash
-TESTOMATIO={your-api-key} npx check-tests@latest pull
-```
-
-Obsidian will automatically reflect the updated files.
-
-## Using Obsidian with Git
-
-For full version control, you can initialize a Git repository in the same folder as your Obsidian vault. This lets you track changes, review diffs, and collaborate with your team. See [Download as Markdown Files](../download-tests-as-files/download-manual-tests-as-files) for details on setting up Git with exported tests.

package/skills/testeiya/testomatio-docs/docs/project/import-export/export-tests/export-to-spreadsheet.md

@@ -1,127 +0,0 @@
----
-title: Export to Spreadsheet
-description: Learn how to export test cases and suites from Testomat.io in spreadsheet (Excel) format. This guide covers exporting all tests, entire suites, or filtered results, with options to include extra columns like steps and preconditions. It also explains using multiselection and different export modes (Only found Tests, Found Suites and Found Tests) to ensure users can efficiently download and share specific test data outside the platform.
-type: article
-url: https://docs.testomat.io/project/import-export/export-tests/export-to-spreadsheet
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, export test cases, export test suites, export data, export as spreadsheet, Excel format, download test data, test management, XLS, automated tests
----
-
-The export feature provides users with the ability to download test cases and suites in various formats, offering flexibility in how the data is exported. You can export test cases in Excel format. This functionality supports filtering by tags, labels, or specific suites, allowing users to export only the relevant test data. Depending on the export mode selected, users can choose to export individual tests, complete suites, or the entire set of tests with additional details.
-
-Below, you will find export guidelines to help you quickly get the necessary test suites and cases.
-
-## How to Export All Suites with Tests (including extra columns)
-
-1. Click on the **Tests** in the sidebar
-2. Click on the **Extra Menu**
-3. Click on **Export as Spreadsheet**
-
-![Export as Spreadsheet](./images/att1_285.png)
-
-Once the pop-up appears, optionally, you can configure your spreadsheet by adding extra columns.
-
-4. Click on the **Add extra columns**
-5. Fill out extra columns, e.g.
-
-- Preconditions
-- Steps
-- Expected results
-
-6. Click on the **Launch export** button to start the export with the applied columns
-
-![Launch export](./images/att2_285.png)
-
-The result file will be available in the **Account files** tab after it is filled out. Once the export is complete, you can download it from the provided link.
-
-![Account files and a link](./images/att3_285.png)
-
-:::note
-
-Once you select extra columns for export, Testomat.io remembers your choices, so you don’t need to configure them again next time.
-
-:::
-
-## How to Export a Suite with All Tests
-
-1. Click on the **Tests** in the sidebar
-2. Select a specific suite or a folder, you want to export
-3. Click on the **Extra Menu**
-4. Click on **Download suite with all tests**
-
-![Download suite with all tests](./images/att4_285.png)
-
-The result file will be available in the **Account files** tab after it is filled out. Once the export is complete, you can download it from the provided link.
-
-![Account files and a link](./images/att5_285.png)
-
-## How to Export Found Test Suites and Cases
-
-### Search Criteria: Export Mode – Only found Tests
-
-1. Click on the **Tests** in the sidebar
-2. Search, e.g., by tag @localisation
-
-Search criteria (e.g. @localization) are saved when switching between tabs, which ensures consistent exports.
-
-Once all exact test matches are shown:
-
-3. Click on **Download results** icon
-
-![Download results](./images/att6_285.png)
-
-4. Select **Only found Tests** in the **Export mode** dropdown
-5. Click on the **Launch export** button
-
-![Launch export](./images/att7_285.png)
-
-The result file will be available in the **Account files** tab after it is filled out. Once the export is complete, you can download it from the provided link.
-
-![Account files and a link](./images/att12_285.png)
-
-### Search Criteria: Export Mode – Found Suites and Found Tests
-
-To export both matching test suites (with their content) and individual matching test cases, follow these steps:
-
-1. Click on the **Tests** in the sidebar
-2. Search, e.g., by tag @localisation
-
-Search criteria (e.g. @localization) are saved when switching between tabs, which ensures consistent exports.
-
-Once all exact test matches are shown:
-
-3. Click on **Download results** icon
-
-![Download results](./images/att6_285-1.png)
-
-4. Select **Found Suites and found tests** in the **Export mode**
-5. Click on the **Launch export** button
-
-![Launch export](./images/att8_285.png)
-
-The result file will be available in the **Account files** tab after it is filled out. Once the export is complete, you can download it from the provided link.
-
-![Account files and a link](./images/att12_285-1.png)
-
-### Export Tests With Multiselection
-
-1. Click on the **Tests** in the sidebar
-2. Click **Multi-Select**
-3. Select specific tests or suites, you want to export
-4. Click on the **Extra Menu** at the bottom
-5. Click on the **Download** button
-
-![Download](./images/att9_285.png)
-
-6. Once the pop-up appears, click on **Launch export** or add extra columns before
-
-![Launch export](./images/att10_285.png)
-
-The result file will be available in the **Account files** tab after it is filled out. Once the export is complete, you can download it from the provided link.
-
-![Account files and a link](./images/att11_285.png)
-
-Testomat.io allows teams to export test suites and cases, making it easier to share, review and work with them outside the platform. This helps to optimize collaboration and keep all the necessary data accessible when needed.

package/skills/testeiya/testomatio-docs/docs/project/import-export/import/auto-import.md

@@ -1,63 +0,0 @@
----
-title: Auto-Import
-description: Learn how to automatically import and update your test cases in Testomat.io using GitHub Actions. This guide explains how to set up a workflow to sync automated tests with your codebase on every push to the main branch, ensuring consistency in test management. It includes commands for Playwright with TypeScript, token management, and auto-committing changes to test IDs.
-type: article
-url: https://docs.testomat.io/project/import-export/auto-import
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Test automation, GitHub Actions, CI workflows, Playwright, TypeScript, Testomat.io, test import, auto-commit, test management, automated testing, continuous integration
----
-
-It is recommended to re-import your automated tests regularely. 
-This task can be accomplished by CI. On every push to main branch you can import automated tests and update their IDs for new tests added. This will keep tests in Testomat.io and in codebase in sync.
-
-## GitHub Actions
-
-If you use GitHub Actions you can use the following workflow file to perform auto-import. 
-
-* We use `check-tests` command with Playwright with TypeScript configured but you can replace it with a framework of your choice. 
-* `TESTOMATIO` token must be passed as a [secret variable](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) into a workflow
-* Changes to tests are automatically committed via `git-auto-commit-action`
-
-```yaml
-name: Update Test IDs
-
-on:
-  push:
-    branches:
-      - main
-      - master
-
-jobs:
-  update-tests:
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v2
-
-    - name: Install Node.js
-      uses: actions/setup-node@v2
-      with:
-        node-version: '18'
-
-    - name: Import tests and update IDs
-      run: npx check-tests Playwright "**/*{.,_}{test,spec,cy}.ts" --update-ids --typescript
-      env:
-        TESTOMATIO: ${{ secrets.TESTOMATIO }}
-
-    - name: Commit and push changes
-      uses: stefanzweifel/git-auto-commit-action@v4
-      with:
-        commit_message: "Updated test IDs"
-```
-
-### GitLab
-
-*Coming soon....*
-
-### Jenkins
-
-*Coming soon...*