testeiya 0.2.1 → 0.3.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +41 -213
- package/dist/prompt/context.js +79 -0
- package/dist/prompt/context.js.map +1 -0
- package/dist/prompt/index.js +56 -0
- package/dist/prompt/index.js.map +1 -0
- package/dist/prompt/print.js +22 -0
- package/dist/prompt/print.js.map +1 -0
- package/dist/prompt/project-info.js +2 -0
- package/dist/prompt/project-info.js.map +1 -0
- package/{src/prompt/system-prompt.ts → dist/prompt/system-prompt.js} +24 -21
- package/dist/prompt/system-prompt.js.map +1 -0
- package/dist/prompt/testomatio.js +264 -0
- package/dist/prompt/testomatio.js.map +1 -0
- package/dist/prompt/tools.js +49 -0
- package/dist/prompt/tools.js.map +1 -0
- package/dist/prompt/vocab.js +8 -0
- package/dist/prompt/vocab.js.map +1 -0
- package/dist/src/args.js +72 -0
- package/dist/src/args.js.map +1 -0
- package/dist/src/cli.js +61 -0
- package/dist/src/cli.js.map +1 -0
- package/dist/src/env.js +69 -0
- package/dist/src/env.js.map +1 -0
- package/dist/src/mcp-extension.js +9 -0
- package/dist/src/mcp-extension.js.map +1 -0
- package/dist/src/mcp.js +139 -0
- package/dist/src/mcp.js.map +1 -0
- package/dist/src/model.js +66 -0
- package/dist/src/model.js.map +1 -0
- package/dist/src/result.js +41 -0
- package/dist/src/result.js.map +1 -0
- package/dist/src/run.js +199 -0
- package/dist/src/run.js.map +1 -0
- package/dist/src/session.js +77 -0
- package/dist/src/session.js.map +1 -0
- package/dist/vendor/mcp.js +14801 -0
- package/mcp-tools.json +2967 -0
- package/package.json +29 -42
- package/prompt/context.ts +101 -0
- package/prompt/index.ts +93 -0
- package/prompt/print.ts +23 -0
- package/prompt/project-info.ts +30 -0
- package/prompt/system-prompt.ts +173 -0
- package/{src/prompt → prompt}/testomatio.ts +119 -8
- package/{src/prompt → prompt}/tools.ts +30 -8
- package/prompt/vocab.ts +7 -0
- package/{skills.lock.json → skills/skills.lock.json} +11 -7
- package/skills/skills.yaml +34 -0
- package/assets/testeiya-logo-dark.svg +0 -16
- package/assets/testeiya-logo.svg +0 -15
- package/models.catalog.json +0 -6963
- package/skills/codeceptjs/ci-fix-tests/SKILL.md +0 -120
- package/skills/codeceptjs/codeceptjs-auth/SKILL.md +0 -158
- package/skills/codeceptjs/codeceptjs-exploration/SKILL.md +0 -91
- package/skills/codeceptjs/codeceptjs-fundamentals/SKILL.md +0 -158
- package/skills/codeceptjs/codeceptjs-run-analysis/SKILL.md +0 -90
- package/skills/codeceptjs/debugging-codeceptjs-tests/SKILL.md +0 -234
- package/skills/codeceptjs/migrate-codeceptjs-4/SKILL.md +0 -110
- package/skills/codeceptjs/migrate-cypress-to-codeceptjs/SKILL.md +0 -306
- package/skills/codeceptjs/migrate-protractor-to-codeceptjs/SKILL.md +0 -352
- package/skills/codeceptjs/migrate-selenium-java-to-codeceptjs/SKILL.md +0 -472
- package/skills/codeceptjs/migrate-testcafe-to-codeceptjs/SKILL.md +0 -350
- package/skills/codeceptjs/refactoring-codeceptjs-tests/SKILL.md +0 -81
- package/skills/codeceptjs/writing-codeceptjs-tests/SKILL.md +0 -206
- package/skills/playwright-best-practices-skill/LICENSE.md +0 -7
- package/skills/playwright-best-practices-skill/README.md +0 -147
- package/skills/playwright-best-practices-skill/SKILL.md +0 -303
- package/skills/playwright-best-practices-skill/advanced/authentication-flows.md +0 -360
- package/skills/playwright-best-practices-skill/advanced/authentication.md +0 -871
- package/skills/playwright-best-practices-skill/advanced/clock-mocking.md +0 -364
- package/skills/playwright-best-practices-skill/advanced/mobile-testing.md +0 -409
- package/skills/playwright-best-practices-skill/advanced/multi-context.md +0 -288
- package/skills/playwright-best-practices-skill/advanced/multi-user.md +0 -393
- package/skills/playwright-best-practices-skill/advanced/network-advanced.md +0 -452
- package/skills/playwright-best-practices-skill/advanced/third-party.md +0 -464
- package/skills/playwright-best-practices-skill/architecture/pom-vs-fixtures.md +0 -363
- package/skills/playwright-best-practices-skill/architecture/test-architecture.md +0 -369
- package/skills/playwright-best-practices-skill/architecture/when-to-mock.md +0 -383
- package/skills/playwright-best-practices-skill/browser-apis/browser-apis.md +0 -391
- package/skills/playwright-best-practices-skill/browser-apis/iframes.md +0 -403
- package/skills/playwright-best-practices-skill/browser-apis/service-workers.md +0 -504
- package/skills/playwright-best-practices-skill/browser-apis/websockets.md +0 -403
- package/skills/playwright-best-practices-skill/core/annotations.md +0 -424
- package/skills/playwright-best-practices-skill/core/assertions-waiting.md +0 -361
- package/skills/playwright-best-practices-skill/core/configuration.md +0 -452
- package/skills/playwright-best-practices-skill/core/fixtures-hooks.md +0 -417
- package/skills/playwright-best-practices-skill/core/global-setup.md +0 -434
- package/skills/playwright-best-practices-skill/core/locators.md +0 -242
- package/skills/playwright-best-practices-skill/core/page-object-model.md +0 -315
- package/skills/playwright-best-practices-skill/core/projects-dependencies.md +0 -453
- package/skills/playwright-best-practices-skill/core/test-data.md +0 -492
- package/skills/playwright-best-practices-skill/core/test-suite-structure.md +0 -361
- package/skills/playwright-best-practices-skill/core/test-tags.md +0 -298
- package/skills/playwright-best-practices-skill/debugging/console-errors.md +0 -420
- package/skills/playwright-best-practices-skill/debugging/debugging.md +0 -504
- package/skills/playwright-best-practices-skill/debugging/error-testing.md +0 -360
- package/skills/playwright-best-practices-skill/debugging/flaky-tests.md +0 -496
- package/skills/playwright-best-practices-skill/frameworks/angular.md +0 -530
- package/skills/playwright-best-practices-skill/frameworks/nextjs.md +0 -469
- package/skills/playwright-best-practices-skill/frameworks/react.md +0 -531
- package/skills/playwright-best-practices-skill/frameworks/vue.md +0 -574
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/ci-cd.md +0 -468
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/docker.md +0 -283
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/github-actions.md +0 -546
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/gitlab.md +0 -397
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/other-providers.md +0 -521
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/parallel-sharding.md +0 -371
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/performance.md +0 -453
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/reporting.md +0 -424
- package/skills/playwright-best-practices-skill/infrastructure-ci-cd/test-coverage.md +0 -497
- package/skills/playwright-best-practices-skill/testing-patterns/accessibility.md +0 -359
- package/skills/playwright-best-practices-skill/testing-patterns/api-testing.md +0 -719
- package/skills/playwright-best-practices-skill/testing-patterns/browser-extensions.md +0 -506
- package/skills/playwright-best-practices-skill/testing-patterns/canvas-webgl.md +0 -493
- package/skills/playwright-best-practices-skill/testing-patterns/component-testing.md +0 -500
- package/skills/playwright-best-practices-skill/testing-patterns/drag-drop.md +0 -576
- package/skills/playwright-best-practices-skill/testing-patterns/electron.md +0 -509
- package/skills/playwright-best-practices-skill/testing-patterns/file-operations.md +0 -377
- package/skills/playwright-best-practices-skill/testing-patterns/file-upload-download.md +0 -562
- package/skills/playwright-best-practices-skill/testing-patterns/forms-validation.md +0 -561
- package/skills/playwright-best-practices-skill/testing-patterns/graphql-testing.md +0 -331
- package/skills/playwright-best-practices-skill/testing-patterns/i18n.md +0 -508
- package/skills/playwright-best-practices-skill/testing-patterns/performance-testing.md +0 -476
- package/skills/playwright-best-practices-skill/testing-patterns/security-testing.md +0 -430
- package/skills/playwright-best-practices-skill/testing-patterns/visual-regression.md +0 -634
- package/skills/playwright-cli/SKILL.md +0 -420
- package/skills/playwright-cli/references/element-attributes.md +0 -23
- package/skills/playwright-cli/references/playwright-tests.md +0 -39
- package/skills/playwright-cli/references/request-mocking.md +0 -87
- package/skills/playwright-cli/references/running-code.md +0 -241
- package/skills/playwright-cli/references/session-management.md +0 -225
- package/skills/playwright-cli/references/storage-state.md +0 -275
- package/skills/playwright-cli/references/test-generation.md +0 -433
- package/skills/playwright-cli/references/tracing.md +0 -139
- package/skills/playwright-cli/references/video-recording.md +0 -143
- package/skills/testeiya/README.md +0 -29
- package/skills/testeiya/answer-formatting/SKILL.md +0 -30
- package/skills/testeiya/check-cucumber/SKILL.md +0 -200
- package/skills/testeiya/check-tests/SKILL.md +0 -260
- package/skills/testeiya/manual-run-assistant/SKILL.md +0 -61
- package/skills/testeiya/testomatio-docs/INDEX.md +0 -175
- package/skills/testeiya/testomatio-docs/SKILL.md +0 -102
- package/skills/testeiya/testomatio-docs/docs/advanced/ai-powered-features/ai-agents.md +0 -144
- package/skills/testeiya/testomatio-docs/docs/advanced/ai-powered-features/ai-powered-features.md +0 -531
- package/skills/testeiya/testomatio-docs/docs/advanced/ai-powered-features/ai-requirements.md +0 -437
- package/skills/testeiya/testomatio-docs/docs/advanced/api-access/index.md +0 -191
- package/skills/testeiya/testomatio-docs/docs/advanced/branches-folder/index.md +0 -277
- package/skills/testeiya/testomatio-docs/docs/advanced/bulk-edit-folder/bulk-edit-demos.mdx +0 -39
- package/skills/testeiya/testomatio-docs/docs/advanced/bulk-edit-folder/bulk-edit-on-suite-and-test-level.md +0 -122
- package/skills/testeiya/testomatio-docs/docs/advanced/bulk-edit-folder/what-is-bulk-edit.md +0 -170
- package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/branches.md +0 -53
- package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/index.mdx +0 -98
- package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/jira-issue.md +0 -151
- package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/runs-and-reports.md +0 -377
- package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/work-in-jira.md +0 -267
- package/skills/testeiya/testomatio-docs/docs/advanced/living-doc/index.md +0 -138
- package/skills/testeiya/testomatio-docs/docs/advanced/milestones/index.md +0 -220
- package/skills/testeiya/testomatio-docs/docs/advanced/shortcuts/index.md +0 -48
- package/skills/testeiya/testomatio-docs/docs/advanced/tags-labels/labels-and-custom-fields.md +0 -201
- package/skills/testeiya/testomatio-docs/docs/advanced/tags-labels/tags-or-labels.md +0 -94
- package/skills/testeiya/testomatio-docs/docs/advanced/tags-labels/tags.md +0 -243
- package/skills/testeiya/testomatio-docs/docs/advanced/test-artifacts/index.md +0 -135
- package/skills/testeiya/testomatio-docs/docs/advanced/tql/index.md +0 -394
- package/skills/testeiya/testomatio-docs/docs/getting-started/index.md +0 -290
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/azure.md +0 -96
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/bamboo.md +0 -94
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/bitbucket.md +0 -106
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/circle.md +0 -115
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/github.md +0 -120
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/gitlab.md +0 -88
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/index.mdx +0 -151
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/jenkins.md +0 -121
- package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/teamcity.md +0 -96
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/azure.md +0 -31
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/clickup.md +0 -54
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/confluence.md +0 -34
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/github.md +0 -31
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/gitlab.md +0 -93
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/index.md +0 -131
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/jira.md +0 -164
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/linear.md +0 -29
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/shortcut.md +0 -67
- package/skills/testeiya/testomatio-docs/docs/integrations/issues-management/youtrack.md +0 -94
- package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/azure-devops.md +0 -53
- package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/email.md +0 -71
- package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/jira.md +0 -52
- package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/ms-teams.md +0 -60
- package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/rules.md +0 -267
- package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/slack.md +0 -82
- package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/telegram.md +0 -73
- package/skills/testeiya/testomatio-docs/docs/integrations/scim-provisioning/index.mdx +0 -207
- package/skills/testeiya/testomatio-docs/docs/integrations/scim-provisioning/okta.md +0 -204
- package/skills/testeiya/testomatio-docs/docs/integrations/single-sign-on/azure.md +0 -95
- package/skills/testeiya/testomatio-docs/docs/integrations/single-sign-on/google.md +0 -75
- package/skills/testeiya/testomatio-docs/docs/integrations/single-sign-on/index.mdx +0 -33
- package/skills/testeiya/testomatio-docs/docs/integrations/single-sign-on/okta.md +0 -108
- package/skills/testeiya/testomatio-docs/docs/integrations/single-sign-on/saml.md +0 -66
- package/skills/testeiya/testomatio-docs/docs/legal/compliance/gdpr.md +0 -95
- package/skills/testeiya/testomatio-docs/docs/legal/compliance/index.mdx +0 -94
- package/skills/testeiya/testomatio-docs/docs/legal/compliance/privacy.md +0 -26
- package/skills/testeiya/testomatio-docs/docs/legal/compliance/terms.md +0 -32
- package/skills/testeiya/testomatio-docs/docs/legal/security/index.mdx +0 -242
- package/skills/testeiya/testomatio-docs/docs/legal/security/jira.md +0 -140
- package/skills/testeiya/testomatio-docs/docs/legal/security/subprocessors.md +0 -76
- package/skills/testeiya/testomatio-docs/docs/management/company/administration.md +0 -363
- package/skills/testeiya/testomatio-docs/docs/management/company/audit-log.md +0 -41
- package/skills/testeiya/testomatio-docs/docs/management/company/plan-features-comparison.md +0 -240
- package/skills/testeiya/testomatio-docs/docs/management/company/subscriptions.md +0 -326
- package/skills/testeiya/testomatio-docs/docs/management/company/trials.md +0 -75
- package/skills/testeiya/testomatio-docs/docs/management/company/users-and-permissions/accountant.md +0 -49
- package/skills/testeiya/testomatio-docs/docs/management/company/users-and-permissions/index.mdx +0 -285
- package/skills/testeiya/testomatio-docs/docs/management/company/users-and-permissions/read-only-user.md +0 -67
- package/skills/testeiya/testomatio-docs/docs/management/company/users-and-permissions/teams.md +0 -138
- package/skills/testeiya/testomatio-docs/docs/management/project/settings.md +0 -87
- package/skills/testeiya/testomatio-docs/docs/management/project/templates.md +0 -546
- package/skills/testeiya/testomatio-docs/docs/project/analytics/index.md +0 -326
- package/skills/testeiya/testomatio-docs/docs/project/import-export/export-tests/classical-tests-markdown-format.md +0 -386
- package/skills/testeiya/testomatio-docs/docs/project/import-export/export-tests/download-manual-tests-as-files.md +0 -378
- package/skills/testeiya/testomatio-docs/docs/project/import-export/export-tests/export-to-obsidian.md +0 -112
- package/skills/testeiya/testomatio-docs/docs/project/import-export/export-tests/export-to-spreadsheet.md +0 -127
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/auto-import.md +0 -63
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-Allure-TestOps.md +0 -49
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-QTest.md +0 -41
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-Qase.md +0 -39
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-Zephyr.md +0 -37
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-csv-xlsx.md +0 -117
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-cucumber.md +0 -93
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-qmetry.md +0 -44
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-source-code.md +0 -117
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-testcaselabs.md +0 -44
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-testmo.md +0 -47
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-testrail.md +0 -82
- package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-xray.md +0 -55
- package/skills/testeiya/testomatio-docs/docs/project/plans/index.md +0 -334
- package/skills/testeiya/testomatio-docs/docs/project/pulse/index.md +0 -104
- package/skills/testeiya/testomatio-docs/docs/project/runs/archive-runs-and-groups.md +0 -176
- package/skills/testeiya/testomatio-docs/docs/project/runs/custom-statuses.md +0 -195
- package/skills/testeiya/testomatio-docs/docs/project/runs/environments.md +0 -203
- package/skills/testeiya/testomatio-docs/docs/project/runs/managing-runs.md +0 -455
- package/skills/testeiya/testomatio-docs/docs/project/runs/merge-strategies.md +0 -137
- package/skills/testeiya/testomatio-docs/docs/project/runs/reports.md +0 -329
- package/skills/testeiya/testomatio-docs/docs/project/runs/rungroups.md +0 -342
- package/skills/testeiya/testomatio-docs/docs/project/runs/running-automated-tests.md +0 -256
- package/skills/testeiya/testomatio-docs/docs/project/runs/running-manual-and-automated-tests.md +0 -331
- package/skills/testeiya/testomatio-docs/docs/project/runs/running-tests-manually.md +0 -633
- package/skills/testeiya/testomatio-docs/docs/project/runs/temporary-tests-notes.md +0 -223
- package/skills/testeiya/testomatio-docs/docs/project/steps-snippets/snippets.md +0 -68
- package/skills/testeiya/testomatio-docs/docs/project/steps-snippets/steps.md +0 -181
- package/skills/testeiya/testomatio-docs/docs/project/tests/bdd-test-case-editor.md +0 -98
- package/skills/testeiya/testomatio-docs/docs/project/tests/classical-test-case-editor.md +0 -354
- package/skills/testeiya/testomatio-docs/docs/project/tests/classical-vs-bdd.md +0 -169
- package/skills/testeiya/testomatio-docs/docs/project/tests/copy-and-move-your-tests.md +0 -156
- package/skills/testeiya/testomatio-docs/docs/project/tests/other-features-for-test-case-design.md +0 -412
- package/skills/testeiya/testomatio-docs/docs/project/tests/test-case-creation-and-editing.md +0 -527
- package/skills/testeiya/testomatio-docs/docs/support/index.md +0 -75
- package/skills/testeiya/testomatio-docs/docs/test-reporting/artifacts.md +0 -388
- package/skills/testeiya/testomatio-docs/docs/test-reporting/cli.md +0 -215
- package/skills/testeiya/testomatio-docs/docs/test-reporting/configuration.md +0 -247
- package/skills/testeiya/testomatio-docs/docs/test-reporting/frameworks.md +0 -490
- package/skills/testeiya/testomatio-docs/docs/test-reporting/functions.md +0 -144
- package/skills/testeiya/testomatio-docs/docs/test-reporting/index.mdx +0 -48
- package/skills/testeiya/testomatio-docs/docs/test-reporting/junit.md +0 -248
- package/skills/testeiya/testomatio-docs/docs/test-reporting/logger.md +0 -138
- package/skills/testeiya/testomatio-docs/docs/test-reporting/php.md +0 -77
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/bitbucket.md +0 -72
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/csv.md +0 -23
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/debug.md +0 -18
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/github.md +0 -63
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/gitlab.md +0 -29
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/html.md +0 -80
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/index.mdx +0 -57
- package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/testomatio.md +0 -331
- package/skills/testeiya/testomatio-docs/docs/test-reporting/python.md +0 -229
- package/skills/testeiya/testomatio-docs/docs/test-reporting/workflows.md +0 -325
- package/skills/testeiya/testomatio-docs/docs/tutorials/Interacting-via-API.md +0 -159
- package/skills/testeiya/testomatio-docs/docs/tutorials/Manual-Testing-Classic.md +0 -164
- package/skills/testeiya/testomatio-docs/docs/tutorials/Set-Up-Read-Only-Access.md +0 -85
- package/skills/testeiya/testomatio-docs/docs/tutorials/Using-AI-in-Testing.md +0 -163
- package/skills/testeiya/testomatio-docs/docs/tutorials/Working-with-Jira.md +0 -125
- package/skills/testeiya/testomatio-docs/docs/tutorials/java.md +0 -478
- package/skills/testeiya/testomatio-docs/docs/tutorials/playwright.md +0 -207
- package/skills/testeiya/testomatio-docs/docs/tutorials/webdriver.md +0 -218
- package/skills/testeiya/testomatio-docs/docs.lock.json +0 -6
- package/skills/testeiya/testomatio-reporter/SKILL.md +0 -307
- package/skills/testomatio/explorbot/explorbot-fundamentals/SKILL.md +0 -88
- package/skills/testomatio/explorbot/explorbot-plan/SKILL.md +0 -95
- package/skills/testomatio/explorbot/explorbot-setup/SKILL.md +0 -334
- package/skills/testomatio/test-automation/automate-manual-test-cases/CLAUDE.md +0 -56
- package/skills/testomatio/test-automation/automate-manual-test-cases/SKILL.md +0 -242
- package/skills/testomatio/test-automation/automate-manual-test-cases/references/CODECEPTJS_BEST_PRACTICES.md +0 -182
- package/skills/testomatio/test-automation/automate-manual-test-cases/references/FINAL_SUMMARY_TEMPLATE.md +0 -22
- package/skills/testomatio/test-automation/automate-manual-test-cases/references/PLAYWRIGHT_BEST_PRACTICES.md +0 -90
- package/skills/testomatio/test-automation/automate-manual-test-cases/references/POM_BEST_PRACTICES.md +0 -53
- package/skills/testomatio/test-automation/automate-manual-test-cases/references/TEST_DATA_MANAGEMENT.md +0 -52
- package/skills/testomatio/test-automation/debug-fix-failed-flaky-autotests/SKILL.md +0 -107
- package/skills/testomatio/test-automation/debug-fix-failed-flaky-autotests/references/DEBUGGING_QUICK_REFERENCE.md +0 -113
- package/skills/testomatio/test-automation/qa-automation-test-consolidation/SKILL.md +0 -29
- package/skills/testomatio/test-automation/run-tests-with-testomatio-reporter/SKILL.md +0 -151
- package/skills/testomatio/test-automation/setup-pr-testing/SKILL.md +0 -199
- package/skills/testomatio/test-automation/testomat-allure-adapter/SKILL.md +0 -289
- package/skills/testomatio/test-management/detect-duplicate-test-cases/SKILL.md +0 -86
- package/skills/testomatio/test-management/detect-duplicate-test-cases/references/DUPLICATE_INSTRUCTIONS.md +0 -54
- package/skills/testomatio/test-management/improve-test-cases/SKILL.md +0 -114
- package/skills/testomatio/test-management/improve-test-cases/references/TESTOMAT_MARKDOWN_EXAMPLE.md +0 -66
- package/skills/testomatio/test-management/pull-request-diff-analyzer/SKILL.md +0 -141
- package/skills/testomatio/test-management/qa-e2e-tests-reporting/SKILL.md +0 -354
- package/skills/testomatio/test-management/qa-e2e-tests-reporting/references/TESTOMATIO_ARTIFACTS.md +0 -82
- package/skills/testomatio/test-management/qa-e2e-tests-reporting/references/TESTOMATIO_HTML_REPORT.md +0 -37
- package/skills/testomatio/test-management/qa-e2e-tests-reporting/references/TESTOMATIO_REPORTERS_CONFIG.md +0 -118
- package/skills/testomatio/test-management/qa-pr-requirements-analyzer/SKILL.md +0 -149
- package/skills/testomatio/test-management/qa-pr-requirements-analyzer/references/summary-example.md +0 -54
- package/skills/testomatio/test-management/qa-requirement-reviewer/SKILL.md +0 -126
- package/skills/testomatio/test-management/qa-requirement-reviewer/references/requirements_reviewer_examples.md +0 -128
- package/skills/testomatio/test-management/qa-test-code-coverage/SKILL.md +0 -174
- package/skills/testomatio/test-management/qa-test-code-coverage/references/COVERAGE_FILE_FORMAT.md +0 -138
- package/skills/testomatio/test-management/qa-test-code-coverage/references/E2E_FRAMEWORKS.md +0 -65
- package/skills/testomatio/test-management/qa-test-code-coverage/scripts/check-coverage.mjs +0 -40
- package/skills/testomatio/test-management/qa-thinking/SKILL.md +0 -36
- package/skills/testomatio/test-management/qa-write-test-cases/SKILL.md +0 -267
- package/skills/testomatio/test-management/qa-write-test-cases/references/test-case-format.md +0 -387
- package/skills/testomatio/test-management/qa-write-test-cases/references/testomat-tms-guide.md +0 -72
- package/skills/testomatio/test-management/qa-write-test-cases/references/writing-rule.md +0 -159
- package/skills/testomatio/test-management/scan-automation-project/SKILL.md +0 -152
- package/skills/testomatio/test-management/sync-test-cases-with-tms/SKILL.md +0 -107
- package/skills/testomatio/test-management/sync-test-cases-with-tms/references/TESTOMATIO_CLI.md +0 -140
- package/skills/testomatio/test-management/testomatio-mcp/SKILL.md +0 -182
- package/skills/testomatio/test-management/testomatio-mcp/references/MCP_SETUP.md +0 -169
- package/skills.yaml +0 -21
- package/src/ai-debug.ts +0 -188
- package/src/api/agent-get.ts +0 -22
- package/src/api/agent-start.ts +0 -384
- package/src/api/client-log.ts +0 -29
- package/src/api/context.ts +0 -332
- package/src/api/debug-layout.ts +0 -47
- package/src/api/debug-report.ts +0 -29
- package/src/api/debug-snapshot.ts +0 -30
- package/src/api/debug-stream.ts +0 -52
- package/src/api/files-delete.ts +0 -184
- package/src/api/files-read.ts +0 -41
- package/src/api/files-rename.ts +0 -99
- package/src/api/files-tree.ts +0 -292
- package/src/api/files-write.ts +0 -41
- package/src/api/mcp.ts +0 -603
- package/src/api/memory.ts +0 -69
- package/src/api/open-external.ts +0 -39
- package/src/api/playwright-cli.ts +0 -606
- package/src/api/providers.ts +0 -457
- package/src/api/read-env-token.ts +0 -33
- package/src/api/sessions.ts +0 -79
- package/src/api/settings.ts +0 -120
- package/src/api/skills.ts +0 -58
- package/src/api/testomatio-attachment.ts +0 -89
- package/src/api/testomatio-auth.ts +0 -284
- package/src/api/testomatio-proxy.ts +0 -197
- package/src/api/testomatio-run-stats.ts +0 -81
- package/src/api/testomatio-target.ts +0 -225
- package/src/api/testomatio-transcription.ts +0 -82
- package/src/api/workspace-search.ts +0 -96
- package/src/api/workspace-sync.ts +0 -151
- package/src/api/workspace.ts +0 -165
- package/src/app-server.ts +0 -556
- package/src/bridge.ts +0 -251
- package/src/check-tests.ts +0 -156
- package/src/cli.ts +0 -17
- package/src/commands.ts +0 -244
- package/src/config.ts +0 -183
- package/src/connection.ts +0 -658
- package/src/context-store.ts +0 -265
- package/src/debug-bus.ts +0 -405
- package/src/extensions/tool-gate.ts +0 -220
- package/src/extensions/webui/ask-channel.ts +0 -52
- package/src/extensions/webui/index.ts +0 -184
- package/src/extensions/webui/tools/ask-question.ts +0 -88
- package/src/extensions/webui/tools/query-result.ts +0 -79
- package/src/extensions/webui/tools/render-chart.ts +0 -53
- package/src/extensions/webui/tools/render-item.ts +0 -61
- package/src/extensions/webui/tools/render-list.ts +0 -170
- package/src/extensions/webui/tools/render-result.ts +0 -85
- package/src/extensions/webui/tools/render-tree.ts +0 -71
- package/src/extensions/webui/tools/ui-widget.ts +0 -54
- package/src/extensions/webui/tools/widget-result.ts +0 -13
- package/src/extensions/webui/widget-channel.ts +0 -50
- package/src/file-log.ts +0 -196
- package/src/git-tracked.ts +0 -68
- package/src/gitignore.ts +0 -53
- package/src/json-store.ts +0 -43
- package/src/load-env.ts +0 -70
- package/src/loader-style.ts +0 -96
- package/src/main.ts +0 -140
- package/src/mcp-catalog.ts +0 -96
- package/src/models-catalog.ts +0 -72
- package/src/permissions.ts +0 -120
- package/src/project-dir.ts +0 -189
- package/src/project-info.ts +0 -108
- package/src/prompt/app-ui.ts +0 -59
- package/src/prompt/browser.ts +0 -27
- package/src/prompt/index.ts +0 -62
- package/src/server-info.ts +0 -62
- package/src/session-factory.ts +0 -442
- package/src/session-store.ts +0 -115
- package/src/shell-env.ts +0 -45
- package/src/skills.ts +0 -163
- package/src/sync-snapshot.ts +0 -140
- package/src/telemetry.ts +0 -239
- package/src/testomatio-auth.ts +0 -299
- package/src/testomatio.ts +0 -98
- package/src/theme.ts +0 -30
- package/src/user-env.ts +0 -94
- package/src/welcome.ts +0 -194
- package/src/workspace/safe-path.ts +0 -85
- package/src/workspace/test-md.ts +0 -70
- package/src/workspace-model.ts +0 -440
- package/testeiya.config.json +0 -14
|
@@ -1,49 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From Allure TestOps
|
|
3
|
-
description: Learn how to import tests from Allure TestOps using a customizable migration script for more advanced, tailored imports.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-allure-testops
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, Allure TestOps, test import, migration, manual tests, automated tests, test management, custom CSV, convert tests.
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
If you have existing tests in Allure TestOps and wish to migrate to Testomat.io, you can import tests from Allure TestOps using a customizable migration script for more advanced, tailored imports.
|
|
14
|
-
|
|
15
|
-
## Where to Find a Migration Script
|
|
16
|
-
|
|
17
|
-
Use the custom migration script to convert an Allure TestOps CSV file into Testomat.io’s CSV format. This method is recommended if you need customization or want to adjust the structure of your test cases during the migration process.
|
|
18
|
-
|
|
19
|
-
Click [migration script instructions](https://github.com/testomatio/migrate-allure) to access the script and get started.
|
|
20
|
-
|
|
21
|
-
## How to Import Tests into Testomat.io
|
|
22
|
-
|
|
23
|
-
Once tests are converted and a new project is [created](https://docs.testomat.io/getting-started/#create-project),
|
|
24
|
-
|
|
25
|
-
1. Navigate to the **Tests** page
|
|
26
|
-
2. Click the **Import from Spreadsheet** button
|
|
27
|
-
|
|
28
|
-

|
|
29
|
-
|
|
30
|
-
Once redirected to the **Imports** page
|
|
31
|
-
|
|
32
|
-
3. From the dropdown menu, select the **Testomatio**
|
|
33
|
-
4. Select the file generated by the migration script
|
|
34
|
-
5. Click the **Create** button to complete the import
|
|
35
|
-
|
|
36
|
-

|
|
37
|
-
|
|
38
|
-
Or alternative way, if you're working in an existing project,
|
|
39
|
-
|
|
40
|
-
1. Navigate to the **Imports** page
|
|
41
|
-
2. Click the **Import from CSV** button
|
|
42
|
-
|
|
43
|
-

|
|
44
|
-
|
|
45
|
-
3. From the dropdown menu, select the **Testomatio**
|
|
46
|
-
4. Select the file generated by the migration script
|
|
47
|
-
5. Click the **Create** button to complete the import
|
|
48
|
-
|
|
49
|
-

|
package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-QTest.md
DELETED
|
@@ -1,41 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From QTest
|
|
3
|
-
description: Learn how to import tests from qTest using the CSV import feature in Testomat.io. This guide walks you through formatting and uploading your test cases, making it easy to migrate or bulk add tests efficiently.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-qtest
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, QTest, test import, QTest migration, manual tests, automated tests, test management, custom XLS
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
> If you have existing tests in QTest and want to migrate to Testomat.io, you can easily import them using the CSV Import feature.
|
|
14
|
-
|
|
15
|
-
## How to Import Tests from QTest to Testomat.io
|
|
16
|
-
|
|
17
|
-
1. If you're creating a brand new project, the **Import from Spreadsheet** button will be available under the Test tab.
|
|
18
|
-
|
|
19
|
-

|
|
20
|
-
|
|
21
|
-
2. If you're working in an existing project, open it in Testomat.io.
|
|
22
|
-
3. Click on the **Imports** tab.
|
|
23
|
-
4. Click the Import from CSV button.
|
|
24
|
-
|
|
25
|
-

|
|
26
|
-
|
|
27
|
-
5. From the dropdown menu, choose **QTest**.
|
|
28
|
-
6. Select the XLS file containing your exported QTest tests.
|
|
29
|
-
7. Click the **Create** button to complete the import.
|
|
30
|
-
|
|
31
|
-

|
|
32
|
-
|
|
33
|
-
## Example Files For Import
|
|
34
|
-
|
|
35
|
-
Below is a sample of the supported format:
|
|
36
|
-
|
|
37
|
-
[QTest](https://testomatio-artifacts.ams3.cdn.digitaloceanspaces.com/documentation/qtest.xls)
|
|
38
|
-
|
|
39
|
-

|
|
40
|
-
|
|
41
|
-
|
package/skills/testeiya/testomatio-docs/docs/project/import-export/import/import-tests-from-Qase.md
DELETED
|
@@ -1,39 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From Qase
|
|
3
|
-
description: Learn how to import tests from Qase using the CSV import feature in Testomat.io. This guide walks you through formatting and uploading your test cases, making it easy to migrate or bulk add tests efficiently.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-qase
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, Qase, test import, Qase migration, manual tests, automated tests, test management, custom XLS
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
> If you have existing tests in Qase and want to migrate to Testomat.io, you can easily import them using the CSV Import feature.
|
|
14
|
-
|
|
15
|
-
## How to Import Tests from Qase to Testomat.io
|
|
16
|
-
|
|
17
|
-
1. If you're creating a brand new project, the **Import from Spreadsheet** button will be available under the Test tab.
|
|
18
|
-
|
|
19
|
-

|
|
20
|
-
|
|
21
|
-
2. If you're working in an existing project, open it in Testomat.io.
|
|
22
|
-
3. Click on the **Imports** tab.
|
|
23
|
-
4. Click the Import from CSV button.
|
|
24
|
-
|
|
25
|
-

|
|
26
|
-
|
|
27
|
-
5. From the dropdown menu, choose **Qase**.
|
|
28
|
-
6. Select the CSV file containing your exported Qase tests.
|
|
29
|
-
7. Click the **Create** button to complete the import.
|
|
30
|
-
|
|
31
|
-

|
|
32
|
-
|
|
33
|
-
## Example Files For Import
|
|
34
|
-
|
|
35
|
-
Below is a sample of the supported format:
|
|
36
|
-
|
|
37
|
-
[Qase](https://testomatio-artifacts.ams3.cdn.digitaloceanspaces.com/documentation/Qase.csv)
|
|
38
|
-
|
|
39
|
-

|
|
@@ -1,37 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From Zephyr
|
|
3
|
-
description: Learn how to import tests from Zephyr using the CSV import feature in Testomat.io. This guide walks you through formatting and uploading your test cases, making it easy to migrate or bulk add tests efficiently.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-zephyr
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, Zephyr, test import, Zephyr migration, manual tests, automated tests, test management, custom XLS
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
> If you have existing tests in Zephyr and want to migrate to Testomat.io, you can easily import them using the CSV Import feature.
|
|
14
|
-
|
|
15
|
-
## How to Import Tests from Zephyr to Testomat.io
|
|
16
|
-
|
|
17
|
-
1. If you're creating a brand new project, the **Import from Spreadsheet** button will be available under the Test tab.
|
|
18
|
-
|
|
19
|
-

|
|
20
|
-
|
|
21
|
-
2. If you're working in an existing project, open it in Testomat.io.
|
|
22
|
-
3. Click on the **Imports** tab.
|
|
23
|
-
4. Click the Import from CSV button.
|
|
24
|
-
|
|
25
|
-
5. From the dropdown menu, choose **Zephyr**.
|
|
26
|
-
6. Select the XLS file containing your exported Zephyr tests.
|
|
27
|
-
7. Click the **Create** button to complete the import.
|
|
28
|
-
|
|
29
|
-

|
|
30
|
-
|
|
31
|
-
## Example Files For Import
|
|
32
|
-
|
|
33
|
-
Below is a sample of the supported format:
|
|
34
|
-
|
|
35
|
-
[Zephyr](https://testomatio-artifacts.ams3.cdn.digitaloceanspaces.com/documentation/Zephyr.xls)
|
|
36
|
-
|
|
37
|
-

|
|
@@ -1,117 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import from CSV/XLSX
|
|
3
|
-
description: Learn how to import tests from CSV or XLSX files into Testomat.io. This guide covers the process of importing test cases from systems like TestRail, Zephyr, Qase, and more. It also introduces an experimental feature to convert CSV/XLSX data into BDD scenarios, and provides instructions for creating custom XLS files for importing.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-csv-xlsx
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, XLS, XLSX, TMS, test import, BDD scenarios, TestRail, Zephyr, Qase, QTest, Testmo, XRay manual tests, automated tests, test management, custom XLS
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
Testomat.io allows you to import tests from **CSV** or **XLSX** files. This is useful if you are migrating from another Test Management System (TMS) or if you already have test cases documented in spreadsheets.
|
|
14
|
-
|
|
15
|
-
## Supported Test Management Systems
|
|
16
|
-
|
|
17
|
-
Testomat.io supports importing test cases from many popular TMS tools. There are two ways to import:
|
|
18
|
-
|
|
19
|
-
- **Direct Import** — via built-in integration
|
|
20
|
-
- **CSV/XLSX Import** — supported for selected TMS formats
|
|
21
|
-
|
|
22
|
-
### Supported For CSV/XLSX Import
|
|
23
|
-
|
|
24
|
-
- Testomatio
|
|
25
|
-
- TestRail
|
|
26
|
-
- Testmo
|
|
27
|
-
- Zephyr
|
|
28
|
-
- QTest
|
|
29
|
-
- Qase
|
|
30
|
-
|
|
31
|
-
### Direct Import Guides
|
|
32
|
-
|
|
33
|
-
Click any tool below to see step-by-step instructions:
|
|
34
|
-
|
|
35
|
-
- [Qase](https://docs.testomat.io/project/import-export/import/import-tests-from-qase/)
|
|
36
|
-
- [QTest](https://docs.testomat.io/project/import-export/import/import-tests-from-qtest/)
|
|
37
|
-
- [QMetry](https://docs.testomat.io/project/import-export/import/import-tests-from-qmetry/)
|
|
38
|
-
- [TestCaseLabs](https://docs.testomat.io/project/import-export/import/import-tests-from-testcaselabs/)
|
|
39
|
-
- [Testmo](https://docs.testomat.io/project/import-export/import/import-tests-from-testmo/)
|
|
40
|
-
- [Testomat.io](https://docs.testomat.io/project/import-export/import/import-tests-from-csvxlsx/)
|
|
41
|
-
- [TestRail](https://docs.testomat.io/project/import-export/import/import-tests-from-testrail/)
|
|
42
|
-
- [XRay](https://docs.testomat.io/project/import-export/import/import-tests-from-xray/)
|
|
43
|
-
- [Zephyr](https://docs.testomat.io/project/import-export/import/import-tests-from-zephyr/)
|
|
44
|
-
|
|
45
|
-
## How to Import Tests from CSV/XLSX in Classic Projects
|
|
46
|
-
|
|
47
|
-
Now you can import tests into your project via:
|
|
48
|
-
|
|
49
|
-
- **Imports** page — ideal when existing data is present.
|
|
50
|
-
- **Tests** page — best for new projects without data.
|
|
51
|
-
|
|
52
|
-
In a **new project**, simply click **Import from Spreadsheet** on the **Tests** page and continue from **Step 3** below.
|
|
53
|
-
|
|
54
|
-

|
|
55
|
-
|
|
56
|
-
### Steps to Import
|
|
57
|
-
|
|
58
|
-
1. Click **Imports** button in the sidebar
|
|
59
|
-
2. Click **Import from CSV** button
|
|
60
|
-
|
|
61
|
-

|
|
62
|
-
|
|
63
|
-
When the sidebar opens,
|
|
64
|
-
|
|
65
|
-
3. Select the format from which your CSV/XLSX was exported (e.g. Qase)
|
|
66
|
-
4. Click **Choose file** and select your CSV/XLSX file
|
|
67
|
-
5. Click **Create** button to start the import
|
|
68
|
-
|
|
69
|
-

|
|
70
|
-
|
|
71
|
-
Your file will be processed, and the test cases will appear in your project.
|
|
72
|
-
|
|
73
|
-
:::note
|
|
74
|
-
|
|
75
|
-
Currently, the CSV/XLSX import is an experimental feature. Some data might not be imported correctly, depending on the TMS format. Please review your imported test cases after migration.
|
|
76
|
-
|
|
77
|
-
:::
|
|
78
|
-
|
|
79
|
-
## How to Import Tests from CSV/XLSX in BDD Projects
|
|
80
|
-
|
|
81
|
-
If your project type is **BDD**, the import steps are **exactly the same** as described above for [Classic projects](https://docs.testomat.io/project/import-export/import/import-tests-from-csv-xlsx/#how-to-import-tests-from-csvxlsx-in-classic-projects).
|
|
82
|
-
|
|
83
|
-
The only difference is the appearance of a new checkbox:
|
|
84
|
-
|
|
85
|
-
- **Import as BDD** – available **only** for imports from **TestRail** and **QTest**.
|
|
86
|
-
- When checked, all rows from the CSV/XLSX file are converted into **BDD scenarios**.
|
|
87
|
-
- Mapping:
|
|
88
|
-
- Precondition → **Given**
|
|
89
|
-
- Step → **When**
|
|
90
|
-
- Expected Result → **Then**
|
|
91
|
-
- All imported tests are saved as **feature files** in your project.
|
|
92
|
-
|
|
93
|
-
:::note
|
|
94
|
-
|
|
95
|
-
Currently, the feature works for TestRail and QTest. If you need support for other systems, please [submit a request](https://testomat.nolt.io/).
|
|
96
|
-
|
|
97
|
-
:::
|
|
98
|
-
|
|
99
|
-
## How to Сreate Custom XLS for Testomat.io
|
|
100
|
-
|
|
101
|
-
You can also create your own XLS file to import tests into Testomat.io. Follow these rules when preparing a custom XLS file:
|
|
102
|
-
|
|
103
|
-
| Column name | Content |
|
|
104
|
-
| ----------- | --------------------------------------------------------------------------------------------------------------- |
|
|
105
|
-
| ID | leave it empty |
|
|
106
|
-
| Title | put the title of your test here, one title per row |
|
|
107
|
-
| Status | goes for test type manual or automated, can be blank |
|
|
108
|
-
| Folder | enter the suite name here, and use `/suite name/sub-suite name` format to create suites nesting |
|
|
109
|
-
| Emoji | can be blank |
|
|
110
|
-
| Priority | you can set priority to your test normal, important, high, critical or low, can be blank |
|
|
111
|
-
| Tags | place here any tags you need, can be blank |
|
|
112
|
-
| Owner | name of test owner, can be blank |
|
|
113
|
-
| Description | put here the description of your test, [Markdown format ](https://www.markdownguide.org/basic-syntax/)supported |
|
|
114
|
-
| Labels | place here labels and custom fields, can be blank |
|
|
115
|
-
| Issues | place here Jira key in format ABC-123 or other IMS keys, can pass multiple Jira keys separated by a comma, can be blank| |
|
|
116
|
-
|
|
117
|
-
You can download the custom Testomat.io example file [here](https://testomatiofiles.ams3.cdn.digitaloceanspaces.com/Testomat_example.xlsx).
|
|
@@ -1,93 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From Cucumber
|
|
3
|
-
description: Learn how to import tests from Cucumber into Testomat.io for better visibility and management. This guide covers steps to create a new project, select the appropriate framework, and import Cucumber feature files using specific commands. It also explains how to differentiate and manage both automated and manual BDD tests efficiently.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-cucumber
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/New_sKP42S9R_2024-07-23.CIkJt32Q_12fmGM.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: Testomat.io, Cucumber, BDD, feature files, test import, automated tests, manual tests, project setup, test management, testing framework, NodeJS, CodeceptJS
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
> If you have end-2-end tests or API or unit tests already implemented you can import them into Testomat.io
|
|
19
|
-
|
|
20
|
-
## Why Do I Need to Import My Tests?
|
|
21
|
-
|
|
22
|
-
Automated tests are hidden within the code and, as a rule, this gem is seen only by engineers. Even though the tests play an important role in product management, they are not available to the whole team involved in the project. To bring the visibility of the running tests further on and show what pieces of software are actually covered by tests, you can import your tests into Testomat.io.
|
|
23
|
-
|
|
24
|
-
Moreover, when you have hundreds and thousands of tests on your hands, some things tend to slip through the cracks and end up neglected. For example, you may need to look up certain features and map them with specifications or Jira tickets. In Testomat.io, whenever automated tests are imported, you can search with ease throughout all the tests, plan new test cases, receive reports, and much more!
|
|
25
|
-
|
|
26
|
-
## Create a New Project
|
|
27
|
-
|
|
28
|
-
Register at [app.testomat.io](https://app.testomat.io) and activate your user account. Then create a new project.
|
|
29
|
-
|
|
30
|
-

|
|
31
|
-
|
|
32
|
-
The type of your new project will influence the look of your interface, as well as its intended audience. Choose **BDD Project** if you plan to follow BDD descriptions or use the Cucumber framework in future. If you haven't decided yet, you can start with default **Classical Project**. Depending on your choice, the interface will differ, as follows:
|
|
33
|
-
|
|
34
|
-
* Within a **BDD Project**, you will have feature definitions written both in the source code (by engineers) and in Testomatio (by managers and QAs). So you will be able to track and plan Cucumber automation, as well as synchronize the actual feature files with relevant test cases. When a scenario has changed in the system, but has not been updated in the code yet, you will be notified that this certain scenario is out of date.
|
|
35
|
-
* Within a **Classical Project**, test cases will be written in free form using markdown. Automated tests will be synced up with test cases, so you will be able to see the test description in one tab and the corresponding test code in another tab. When a description of a test case undergoes changes, you will be notified that a certain test might need to be updated.
|
|
36
|
-
|
|
37
|
-
> In this section of the Guide, we discuss the issues concerning BDD Projects. If you need to import a Classical Project, go to the [Import Tests From Source Code](https://docs.testomat.io/getting-started/import-tests-from-source-code/#why-do-i-need-to-import-my-tests) section of this guide.
|
|
38
|
-
|
|
39
|
-

|
|
40
|
-
|
|
41
|
-
You can provide a URL of a repository hosted on GitHub, GitLab, BitBucket, as well as of a self-hosted one. Testomat.io will use this URL to navigate you from test cases straight to the source code. Please make sure that the URL is pointing to the *directory where the tests are located*.
|
|
42
|
-
|
|
43
|
-
> If you have set a repository URL make sure that the path matches the one in URL repository. For instance, if you have URL: "https://github.com/testomatio/examples/tree/master/cucumber/features" you should navigate to "features" within your project to import tests.
|
|
44
|
-
|
|
45
|
-
Click the **Create** button to start a new project.
|
|
46
|
-
|
|
47
|
-
## Import Tests from Feature Files
|
|
48
|
-
|
|
49
|
-
When your project is created, click the **Import from Source Code** button.
|
|
50
|
-
|
|
51
|
-

|
|
52
|
-
|
|
53
|
-
Or another case:
|
|
54
|
-
|
|
55
|
-

|
|
56
|
-
|
|
57
|
-
When the **Import Project From Source Code** screen opens, you will need to pick Cucumber as your project framework.
|
|
58
|
-
|
|
59
|
-

|
|
60
|
-
|
|
61
|
-
> If you use BDD with CodeceptJS, choose CodeceptJS as your project framework and select "Gherkin" as your project language.
|
|
62
|
-
|
|
63
|
-
Once you have chosen the framework and the language, you will be provided with a command that you need to copy and execute in a terminal. Before running this command, please note that to parse & import feature files **NodeJS 10+** with NPM is required.
|
|
64
|
-
|
|
65
|
-
Open a terminal, navigate to the project folder in your project and execute the command. By default, we assume that your features files are located in the **features** folder of your project. If you store them in a different folder, rewrite the --dir option of the command to use the folder your feature files are actually stored in:
|
|
66
|
-
|
|
67
|
-
```
|
|
68
|
-
TESTOMATIO={apiKey} npx check-cucumber@latest "**/*.feature" --dir features
|
|
69
|
-
```
|
|
70
|
-
|
|
71
|
-

|
|
72
|
-
|
|
73
|
-
Seeing a report on how many tests were found means that the import command was executed successfully. If you don't see a similar message, you might need to change the pattern to match files or the directory to scan. Open the API reference of check-cucumber command to learn how to do that.
|
|
74
|
-
|
|
75
|
-
Refresh the page and you will see all the imported test files.
|
|
76
|
-
|
|
77
|
-

|
|
78
|
-
|
|
79
|
-
## Import Manual BDD Tests from Source Code
|
|
80
|
-
|
|
81
|
-
If you have manual tests in the repository and want to import them into Testomatio you can use `.manual.feature` extension in the feature file. Tests will be imported as well as automated tests and will be marked as `manual` in Testomatio. For instance:
|
|
82
|
-
|
|
83
|
-
```
|
|
84
|
-
filename.manual.feature
|
|
85
|
-
```
|
|
86
|
-
|
|
87
|
-

|
|
88
|
-
|
|
89
|
-
Now run the command we used earlier to import the tests from the source code.
|
|
90
|
-
|
|
91
|
-

|
|
92
|
-
|
|
93
|
-
As a result, we got tests divided into automated and manual. This structure allows for more efficient and flexible testing workflows, enhancing our overall testing strategy.
|
|
@@ -1,44 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From QMetry
|
|
3
|
-
description: Learn how to import tests from QMetry using a customizable migration script for more advanced, tailored imports.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-qmetry
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, QMetry, test import, QMetry migration, manual tests, automated tests, test management, custom XLS
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
> If you have existing tests in Qmetry and wish to migrate to Testomat.io, you can import tests from QMetry using a customizable migration script for more advanced, tailored imports.
|
|
14
|
-
|
|
15
|
-
## Where to Find a Migration Script
|
|
16
|
-
|
|
17
|
-
Use the custom migration script to convert a QMetry CSV file into Testomat.io’s CSV format.
|
|
18
|
-
This method is recommended if you need customization or want to adjust the structure of your test cases during the migration process.
|
|
19
|
-
|
|
20
|
-
Click [migration script instructions](https://github.com/testomatio/migrate-qmetry) to access the script and get started.
|
|
21
|
-
|
|
22
|
-
## How to Import Tests into Testomat.io
|
|
23
|
-
|
|
24
|
-
1. If you're creating a brand new project, the **Import from Spreadsheet** button will be available under the Test tab.
|
|
25
|
-
|
|
26
|
-

|
|
27
|
-
|
|
28
|
-
2. If you're working in an existing project, open it in Testomat.io.
|
|
29
|
-
3. Click the **Imports** tab.
|
|
30
|
-
4. Click the **Import from CSV** button.
|
|
31
|
-
|
|
32
|
-

|
|
33
|
-
|
|
34
|
-
5. From the dropdown menu, choose **Testomatio**.
|
|
35
|
-
6. Select the file generated by the migration script.
|
|
36
|
-
7. Click the **Create** button to complete the import.
|
|
37
|
-
|
|
38
|
-

|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
@@ -1,117 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From Source Code
|
|
3
|
-
description: Learn how to import existing end-to-end or unit tests directly from your source code into Testomat.io. This guide covers creating a project and configuring test imports from repositories. It also shows how to sync automated tests, import them as manual if needed, and manage test visibility.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-source-code
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/New_eUYumU81_2024-07-25.Be2cERwK_Z1rkx9t.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: Testomat.io, source code, test import, automated tests, manual tests, test management, repository, GitHub, Jira, BDD, project setup, CI integration, visibility
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
> If you have end-2-end tests, API or unit tests already implemented, you can import them into Testomat.io.
|
|
19
|
-
|
|
20
|
-
## Why Do I Need to Import My Tests?
|
|
21
|
-
|
|
22
|
-
Automated tests are hidden within the code and, as a rule, this gem is seen only by engineers. Even though the tests play an important role in product management, they are not available to the whole team involved in the project. To bring the visibility of the running tests further on and show what pieces of software are actually covered by tests, you can import your tests into Testomat.io.
|
|
23
|
-
|
|
24
|
-
Moreover, when you have hundreds and thousands of tests on your hands, some things tend to slip through the cracks and end up neglected. For example, you may need to look up certain features and map them with specifications or Jira tickets. In Testomat.io, whenever automated tests are imported, you can search with ease throughout all the tests, plan new test cases, receive reports, and much more!
|
|
25
|
-
|
|
26
|
-
## Create a New Project
|
|
27
|
-
|
|
28
|
-
Register at [app.testomat.io](https://app.testomat.io) and activate your user account. Then create a new project.
|
|
29
|
-
|
|
30
|
-

|
|
31
|
-
|
|
32
|
-
The type of your new project will influence the look of your interface, as well as its intended audience. Choose **BDD Project** if you plan to follow BDD descriptions or use the Cucumber framework in future. If you haven't decided yet, you can start with default **Classical Project**. Depending on your choice, the interface will differ, as follows:
|
|
33
|
-
|
|
34
|
-
* Within a **BDD Project**, you will have feature definitions written both in the source code (by engineers) and in Testomatio (by managers and QAs). So you will be able to track and plan Cucumber automation, as well as synchronize the actual feature files with relevant test cases. When a scenario has changed in the system, but has not been updated in the code yet, you will be notified that this certain scenario is out of date.
|
|
35
|
-
* Within a **Classical Project**, test cases will be written in free form using markdown. Automated tests will be synced up with test cases, so you will be able to see the test description in one tab and the corresponding test code in another tab. When a description of a test case undergoes changes, you will be notified that a certain test might need to be updated.
|
|
36
|
-
|
|
37
|
-
> In this section of the Guide, we discuss the issues concerning Classical Projects. If you need to import a BDD Project, go to the [Import Tests From Cucumber](https://docs.testomat.io/getting-started/import-tests-from-cucumber/#why-do-i-need-to-import-my-tests) section of this guide.
|
|
38
|
-
|
|
39
|
-

|
|
40
|
-
|
|
41
|
-
You can provide a URL of a repository hosted on GitHub, GitLab, BitBucket, as well as of a self-hosted one. Testomat.io will use this URL to navigate you from test cases straight to the source code. Please make sure that the URL is pointing to the *directory where the tests are located*. In the following steps we show in detail how to import tests from that directory.
|
|
42
|
-
|
|
43
|
-
> If you fill in the **Repository URL** field, doublecheck that the given path matches the one in the URL repository. For instance, if you have URL: "https://github.com/testomatio/examples/tree/master/playwright/e2e-examples/e2e-tests", you should navigate to "e2e-tests" within your project to import tests.
|
|
44
|
-
|
|
45
|
-
Click the **Create** button to start a new project.
|
|
46
|
-
|
|
47
|
-
## Import Tests
|
|
48
|
-
|
|
49
|
-
When your project is created, click the **Import from Source Code** button.
|
|
50
|
-
|
|
51
|
-

|
|
52
|
-
|
|
53
|
-
Or another case:
|
|
54
|
-
|
|
55
|
-

|
|
56
|
-
|
|
57
|
-
In the **Import** section, you are asked to pick the framework, programming language and and operating system you are using for testing.
|
|
58
|
-
|
|
59
|
-

|
|
60
|
-
|
|
61
|
-
> If you don't see the framework you work with in this list - please contact us, and we will do our best to add support for it soon!
|
|
62
|
-
|
|
63
|
-
Once you have chosen the project parameters, you will be provided with a command that you need to copy and execute in a terminal. Before running this command, please check if your environment matches these requirements:
|
|
64
|
-
* If you run tests in NodeJS (JavaScript, TypeScript), you should have NodeJS 10+ and npm to be installed to be able to run this command.
|
|
65
|
-
* If you run tests in PHP - you will need PHP > 7.2 and Composer installed.
|
|
66
|
-
|
|
67
|
-
Open a terminal, navigate to the tests folder in your project and execute the command. Seeing a report on how many tests were found means that the import command was executed successfully:
|
|
68
|
-
|
|
69
|
-

|
|
70
|
-
|
|
71
|
-
If you don't see a similar message, this might be because our default settings do not work for you. Please check the command's API change command parameters so it could find tests. The most common issues with import are different file naming format and/or incorrect directory for import.
|
|
72
|
-
|
|
73
|
-
:::note
|
|
74
|
-
|
|
75
|
-
All nested suites will be flattened on import for better visibility. So if you have nested `describe` blocks inside the same file they will be imported as separate suites from the file
|
|
76
|
-
|
|
77
|
-
:::
|
|
78
|
-
|
|
79
|
-
When the tests are finally imported, reopen the project, and you will see that all tests with their folders and files are shown on Testomat.io.
|
|
80
|
-
|
|
81
|
-

|
|
82
|
-
|
|
83
|
-
All imported tests are marked as "Automated" by default. If you click on any of those tests, you will see its code and a link to its repository. Please, check that the link actually points to the corresponding file. Otherwise, you might want to change the repository URL in project settings.
|
|
84
|
-
|
|
85
|
-

|
|
86
|
-
|
|
87
|
-
## Import Automated Tests As Manual
|
|
88
|
-
|
|
89
|
-
If you need to import automated tests as manual, just add a tag to the test name in your code and thеn use the same tag in the import settings. In your code, the tag name must begin with the **@** symbol. For instance: `@tagname`.
|
|
90
|
-
|
|
91
|
-

|
|
92
|
-
|
|
93
|
-
The `manual` name of the tag is used as an example, you can use whatever you like.
|
|
94
|
-
|
|
95
|
-
Now, open **Import Project from Source Code** in Testomat.io and specify your project parameters. Just like we did earlier.
|
|
96
|
-
|
|
97
|
-
Before you execute the command, take some additional steps:
|
|
98
|
-
|
|
99
|
-
1. Click **Additional Settings**.
|
|
100
|
-
2. Enter a tag name, same as in the code (here without @ symbol).
|
|
101
|
-
3. Execute the command in your project and click the **Finish** button.
|
|
102
|
-
|
|
103
|
-

|
|
104
|
-
|
|
105
|
-
On the **Tests** page, the imported tests that have been tagged are listed as manual.
|
|
106
|
-
|
|
107
|
-

|
|
108
|
-
|
|
109
|
-
## What's Next?
|
|
110
|
-
|
|
111
|
-
Ok, I've just imported my tests successfully, now what?
|
|
112
|
-
|
|
113
|
-
* **Show your tests to your team**. You must be proud of your work! 🎉
|
|
114
|
-
* **Plan new tests** before automating them. Ask the manager to write test specification within Testomat.io so you could start working on them.
|
|
115
|
-
* All new tests will be marked as "manual" unless you import them from code. You can check the number of manual tests that are left, and see the whole range of what is yet to be implemented.
|
|
116
|
-
* **Receive run reports** - similarly to Importing tests, you can receive detailed reports on each test execution. Open **Runs** page and follow instructions from there.
|
|
117
|
-
* **Add import command to CI** - re-import the tests on each commit to have your project up to date with the source code.
|
|
@@ -1,44 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From TestCaseLabs
|
|
3
|
-
description: Learn how to import tests from TestCaseLabs using a customizable migration script for more advanced, tailored imports.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-testcaselabs
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, TestCaseLabs, test import, TestCaseLabs migration, manual tests, automated tests, test management, custom XLS
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
> If you have existing tests in TestCaseLabs and wish to migrate to Testomat.io, you can import tests from TestCaseLabs using a customizable migration script for more advanced, tailored imports.
|
|
14
|
-
|
|
15
|
-
## Import Tests from TestCaseLabs Using the Migration Script
|
|
16
|
-
|
|
17
|
-
Use the custom migration script to convert a TestCaseLabs CSV file into Testomat.io’s CSV format.
|
|
18
|
-
This method is recommended if you need customization or want to adjust the structure of your test cases during the migration process.
|
|
19
|
-
|
|
20
|
-
Click [migration script instructions](https://github.com/testomatio/migrate-testcaselabs) to access the script and get started.
|
|
21
|
-
|
|
22
|
-
## How to Import Tests into Testomat.io
|
|
23
|
-
|
|
24
|
-
1. If you're creating a brand new project, the **Import from Spreadsheet** button will be available under the Test tab.
|
|
25
|
-
|
|
26
|
-

|
|
27
|
-
|
|
28
|
-
2. If you're working in an existing project, open it in Testomat.io.
|
|
29
|
-
3. Click the **Imports** tab.
|
|
30
|
-
4. Click the **Import from CSV** button.
|
|
31
|
-
|
|
32
|
-

|
|
33
|
-
|
|
34
|
-
5. From the dropdown menu, choose **Testomatio**.
|
|
35
|
-
6. Select the file generated by the migration script.
|
|
36
|
-
7. Click the **Create** button to complete the import.
|
|
37
|
-
|
|
38
|
-

|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
@@ -1,47 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Import Tests From Testmo
|
|
3
|
-
description: Learn how to import tests from Testmo using two flexible methods - the built-in CSV import and a customizable migration script. This guide walks you through importing your test cases into Testomat.io, whether you’re using the native CSV feature for quick setup or the migration script for more advanced, tailored imports. Choose the method that best fits your workflow for a smooth transition from Testmo.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/project/import-export/import-tests-from-testmo
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Testomat.io, CSV, Testmo, test import, Testmo migration, manual tests, automated tests, test management
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
> If you have existing tests in Testmo and wish to migrate to Testomat.io, this guide will walk you through the process of importing your tests into Testomat.io.
|
|
14
|
-
|
|
15
|
-
Currently, Testomat.io supports two methods for importing tests from Testmo
|
|
16
|
-
|
|
17
|
-
- Import via CSV
|
|
18
|
-
- Customizable migration script
|
|
19
|
-
|
|
20
|
-
## How to Import Tests via CSV
|
|
21
|
-
|
|
22
|
-
1. Open your project in Testomat.io.
|
|
23
|
-
2. Click the **Imports** tab.
|
|
24
|
-
3. Click the **Import from CSV** button.
|
|
25
|
-
|
|
26
|
-

|
|
27
|
-
|
|
28
|
-
4. From the dropdown menu, choose **Testmo**.
|
|
29
|
-
5. Select the CSV file containing your exported Testmo tests.
|
|
30
|
-
6. Click the **Create** button to complete the import.
|
|
31
|
-
|
|
32
|
-

|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
## Convert Testmo Project Using the Migration Script
|
|
36
|
-
|
|
37
|
-
Use the custom migration script to convert a Testmo CSV file into Testomat.io’s CSV format.
|
|
38
|
-
This method is recommended if you need customization or want to adjust the structure of your test cases during the migration process.
|
|
39
|
-
|
|
40
|
-
Click [migration script instructions](https://github.com/testomatio/migrate-testmo) to access the script and get started.
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|