testeiya 0.2.0 → 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 +37 -175
- 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 -41
- 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/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 -127
- 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
package/skills/testeiya/testomatio-docs/docs/integrations/continuous-integration/teamcity.md
DELETED
|
@@ -1,96 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: TeamCity
|
|
3
|
-
description: Integrate TeamCity with Testomat.io for automated test execution and reporting. The guide details creating projects and build configurations in TeamCity, setting up access keys, defining project parameters, and adding build steps for executing tests. It ensures seamless CI/CD workflows with direct connections to Testomat.io.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/continuous-integration/teamcity
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: TeamCity, Testomat.io, CI/CD integration, CI connection, CI Integration, TeamCity project, automated testing, build configurations, Access Token, access keys, test reporting, project parameters, test management, environment variables, automated tests
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
Before configuring the TeamCity and Testomat.io integration, create a new project in your TeamCity workspace:
|
|
14
|
-
|
|
15
|
-

|
|
16
|
-
|
|
17
|
-
On the same page Create Build Configuration.
|
|
18
|
-
|
|
19
|
-
**Build configurations define how to retrieve and build sources of a project.**
|
|
20
|
-
|
|
21
|
-
Create a Access Token for the user:
|
|
22
|
-
|
|
23
|
-

|
|
24
|
-
|
|
25
|
-
Open **'Parameters'** and setup new environment variables with empty default values:
|
|
26
|
-
|
|
27
|
-
- ```run```
|
|
28
|
-
- ```testomatio```
|
|
29
|
-
- ```grep```
|
|
30
|
-
- ```testomatio_url```
|
|
31
|
-
|
|
32
|
-

|
|
33
|
-
|
|
34
|
-
Add a new Build Step: Command Line.
|
|
35
|
-
|
|
36
|
-
Script should include a step where the test runner is executed with `—grep` option and `TESTOMATIO` environment variables passed in.
|
|
37
|
-
|
|
38
|
-
For instance: ```- npx codeceptjs run-workers 2 --grep "${grep}"```
|
|
39
|
-
|
|
40
|
-

|
|
41
|
-
|
|
42
|
-
Save the build and switch to Testomat.io. To integrate TeamCity with your Testomat.io project follow the steps described below:
|
|
43
|
-
|
|
44
|
-
1. Go to **'Settings'**.
|
|
45
|
-
2. Select **'Continuous Integration'**.
|
|
46
|
-
3. Click **'Connect to CI'**.
|
|
47
|
-
|
|
48
|
-

|
|
49
|
-
|
|
50
|
-
4. Select **'TeamCity'** and enter following details on the **'Connection'** tab:
|
|
51
|
-
|
|
52
|
-
- `Teamcity Host`.
|
|
53
|
-
- `API token` - API token from TeamCity Domain Authentication.
|
|
54
|
-
- `Build Name`.
|
|
55
|
-
|
|
56
|
-

|
|
57
|
-
|
|
58
|
-
5. Switch to **'Input Variables'** tab and select checkboxes:
|
|
59
|
-
|
|
60
|
-
- Send Run ID as `run` input (required for scheduled jobs).
|
|
61
|
-
- Send Testomat.io API key as `testomatio` input.
|
|
62
|
-
- Send Testomat.io Server URL as `testomatio_url` input (if you use on-premise setup).
|
|
63
|
-
|
|
64
|
-
:::note
|
|
65
|
-
|
|
66
|
-
You can set and pass more input variables if you set them in [Environment Configuration](./index.md#environment-configuration). For example: test environment, browser, branch, etc.
|
|
67
|
-
|
|
68
|
-
:::
|
|
69
|
-
|
|
70
|
-
6. Click on **'Save'** button to save the connection.
|
|
71
|
-
|
|
72
|
-

|
|
73
|
-
|
|
74
|
-
7a. When the connection is saved, open **'Runs'** page and select `Run Automated Tests in CI` option in extra menu.
|
|
75
|
-
|
|
76
|
-

|
|
77
|
-
|
|
78
|
-
8a. Select **'TeamCity'** profile in a list, select a target ref or any other variables, if any were configured. Optionally, select a **Test Plan** or create a new one.
|
|
79
|
-
|
|
80
|
-
9a. Click on **'Launch'** button and wait for the results.
|
|
81
|
-
|
|
82
|
-

|
|
83
|
-
|
|
84
|
-
OR
|
|
85
|
-
|
|
86
|
-
7b. On **'Tests'** page select any automated suite or test case -> click **'Extra menu'** button -> select **'Run Tests'** option -> open **'Run in CI'** tab.
|
|
87
|
-
|
|
88
|
-
8b. Select **'TeamCity'** profile in a list, as well, select a target ref or any other variables, if any were configured.
|
|
89
|
-
|
|
90
|
-
9b. Click on **'Launch'** button and wait for the results.
|
|
91
|
-
|
|
92
|
-

|
|
93
|
-
|
|
94
|
-
This will start a new job in TeamCity, please check that the job was successfully triggered and completed. After the job has finished, a run report will be available on Runs page of Testomat.io.
|
|
95
|
-
|
|
96
|
-

|
|
@@ -1,31 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Azure DevOps Configuration
|
|
3
|
-
description: Integrate Azure DevOps with Testomat.io for efficient issue tracking and test management. This guide explains setting up a profile using an Azure DevOps personal access token, organization name, and project name. Once connected, users can link tests or create defects directly in Azure DevOps with all necessary test data and references.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management/azure
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Azure DevOps, Testomat.io, issue tracking, test management, personal access token, defect creation, integration setup, testing workflow
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
To connect Azure DevOps with Testomat.io you need to open **Settings (1) -> Issues Management (2)** and click on **'Connect to IMS' (3)** button.
|
|
14
|
-
|
|
15
|
-

|
|
16
|
-
|
|
17
|
-
When **'Connect to Issue Management System'** page is opened, follow the instructions below:
|
|
18
|
-
|
|
19
|
-
1. Select **'Azure DevOps'** from the list.
|
|
20
|
-
2. Change the **Profile Name** if needed.
|
|
21
|
-
3. Enter your **Private Access Token** from Azure DevOps ([learn more about how to create a PAT](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows)).
|
|
22
|
-
4. Enter your **Azure DevOps Organization** name.
|
|
23
|
-
5. Enter your **Azure DevOps Project** name.
|
|
24
|
-
6. Click **'Save'** button.
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-

|
|
28
|
-
|
|
29
|
-
Once your Issues Management System is configured you can link a test case or create a defect. As a result, Testomat.io will create a ticket in your Azure DevOps project with dedicated links and data, so you can easily look through the testing data you need. Here is an example:
|
|
30
|
-
|
|
31
|
-

|
|
@@ -1,54 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: ClickUp Configuration
|
|
3
|
-
description: Learn how to integrate ClickUp with Testomat.io for efficient issue management. This guide provides step-by-step instructions to retrieve your ClickUp API token and List ID, configure Testomat.io, and connect the two systems seamlessly.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management/clickup
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/New_fHP8LT7x_2024-10-30.B_KfZFZ0_Z1PIuCT.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: ClickUp integration, Testomat.io, issue management, API token, List ID, project management, test management tools, automated testing, manual testing, software testing
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
If you already have a workspace set up and configured in **ClickUp**, we can proceed with integrating it with Testomat.io. All you need is a **Personal Access Token** and a **List ID**. We’ll guide you step-by-step on how to retrieve this information and use it to connect with Testomat.io.
|
|
19
|
-
|
|
20
|
-

|
|
21
|
-
|
|
22
|
-
1. Click on **Workspace name** in the top-left corner
|
|
23
|
-
2. Then click on **Settings**
|
|
24
|
-
|
|
25
|
-

|
|
26
|
-
|
|
27
|
-
3. Go to **Apps**
|
|
28
|
-
4. Click on **Generate** button to create **API Token**
|
|
29
|
-
5. Copy your API Token
|
|
30
|
-
|
|
31
|
-

|
|
32
|
-
|
|
33
|
-
Keep your API Token secure, as you’ll need it for the integration with Testomat.io.
|
|
34
|
-
|
|
35
|
-
Next, we need to find the **List ID**. In ClickUp, the List ID is a unique identifier assigned to each list within a folder in a workspace. You can find the List ID **in the URL when viewing a specific list** on the ClickUp website.
|
|
36
|
-
|
|
37
|
-

|
|
38
|
-
|
|
39
|
-
After collecting all necessary data, we can move on to Testomat.io.
|
|
40
|
-
|
|
41
|
-
1. Select ClickUp from the list of available Issue Management Systems.
|
|
42
|
-
|
|
43
|
-

|
|
44
|
-
|
|
45
|
-
2. Enter a **Profile Name**
|
|
46
|
-
3. Paste ClickUp **API Token**
|
|
47
|
-
4. Paste ClickUp **List ID**
|
|
48
|
-
5. Click on **Save** button
|
|
49
|
-
|
|
50
|
-

|
|
51
|
-
|
|
52
|
-
If everything was done correctly, you will receive a confirmation message indicating that the ClickUp profile was successfully created.
|
|
53
|
-
|
|
54
|
-

|
|
@@ -1,34 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Confluence
|
|
3
|
-
description: Learn how to connect your Confluence space with Testomat.io for issue management. This guide walks you through obtaining your Project Access Token on Atlassian and configuring Testomat.io to streamline workflows.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management/confluence
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: keywords
|
|
10
|
-
content: Confluence, Testomat.io, Confluence integration, requirements management, issues management, Confluence space, Atlassian, API token, traceability, project management, test management tools, automated testing, manual testing, software testing
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
Testomat.io allows you to link your Confluence space to a Testomat.io project and use it as a source of requirements.
|
|
14
|
-
|
|
15
|
-
To connect your **Confluence space** with Testomat.io you need to open **Settings (1) -> Issues Management (2)** and click on **'Connect to IMS' (3)** button.
|
|
16
|
-
|
|
17
|
-

|
|
18
|
-
|
|
19
|
-
When **'Connect to Issue Management System'** page is opened, follow the instructions below:
|
|
20
|
-
|
|
21
|
-
1. Select **'Confluence pages'** from the list.
|
|
22
|
-
2. Change the **Profile Name** if needed.
|
|
23
|
-
3. Enter your **'Confluence server url'**.
|
|
24
|
-
4. Enter your **Confluence user email** (can be blank for private server).
|
|
25
|
-
5. Enter your **Confluence space key** (can be blank).
|
|
26
|
-
6. Enter your **Private Access Token** from Atlassian ([learn more about how to create a PAT](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token)).
|
|
27
|
-
|
|
28
|
-

|
|
29
|
-
|
|
30
|
-
7. Click **'Save'** button.
|
|
31
|
-
|
|
32
|
-

|
|
33
|
-
|
|
34
|
-
Once the connection between Confluence space and Testomat.io project is set up, the system can analyze your Confluence pages to extract requirement descriptions, assess traceability, identify edge cases, and generate relevant test suites and test cases.
|
|
@@ -1,31 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: GitHub Issues Configuration
|
|
3
|
-
description: Configure GitHub Issues integration in Testomat.io to create and manage issues directly from your test management system. This setup involves providing a GitHub username, API token, and repository details. Once configured, Testomat.io can link tests to issues or create defects, automatically generating tickets in GitHub with relevant testing data.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management/github
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/202862612-68c32b53-ed91-4e34-98cb-6125c3bccc6c.OHkajOv3_Z1TjJdJ.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: GitHub Issues, Testomat.io, issue tracking, test management, API token, workflow integration, defect creation, test reporting
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-

|
|
19
|
-
|
|
20
|
-
1. Give a name to your profile
|
|
21
|
-
4. Enter your GitHub Username
|
|
22
|
-
8. Enter your GitHub API Token with access to workflow scope and write permissions ([learn more](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token))
|
|
23
|
-

|
|
24
|
-
10. Enter your GitHub Organization/Repository
|
|
25
|
-
11. Click on Save button
|
|
26
|
-
|
|
27
|
-

|
|
28
|
-
|
|
29
|
-
Once your Issues Management System is configured you can link a test or create a defect. As a result, Testomat.io will create a ticket in your GitHub project with dedicated links and data, so you can easily look through the testing data you need. Here is an example:
|
|
30
|
-
|
|
31
|
-

|
|
@@ -1,93 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: GitLab Configuration
|
|
3
|
-
description: Learn how to integrate GitLab with Testomat.io for issue management. This guide walks you through obtaining your Group Name, Project ID, and Project Access Token, and configuring Testomat.io to streamline workflows.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management/gitlab
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/New_I3kRnywM_2024-11-12.BGcH1QIE_jiAFz.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: GitLab integration, Testomat.io, issue management, project management, access token, Group Name, Project ID, software testing, test management tools
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
If you already have a **Group** and **Project** set up and configured in **GitLab**, we can proceed with integrating it with Testomat.io. All you need is a **Group Name**, **Project ID** and a **Project Access Token**. We’ll guide you step-by-step on how to retrieve this information and use it to connect with Testomat.io.
|
|
19
|
-
|
|
20
|
-
Testomat.io now supports both GitLab SaaS and self-hosted GitLab instances. When setting up your
|
|
21
|
-
integration, you'll be able to specify which type you're using.
|
|
22
|
-
|
|
23
|
-

|
|
24
|
-
|
|
25
|
-
To get the **Group Name**:
|
|
26
|
-
|
|
27
|
-
1. Go to the **Groups** section
|
|
28
|
-
2. Select the group in which your project is located
|
|
29
|
-
|
|
30
|
-

|
|
31
|
-
|
|
32
|
-
3. The **Group Name** you need to integrate with Testomat.io is in the **URL**. Copy and save it
|
|
33
|
-
|
|
34
|
-

|
|
35
|
-
|
|
36
|
-
Next, let's find the **Project ID**.
|
|
37
|
-
|
|
38
|
-
1. On your project page, go to **Settings**
|
|
39
|
-
2. Select the **General** section
|
|
40
|
-
|
|
41
|
-

|
|
42
|
-
|
|
43
|
-
3. You will see your **Project ID** in the corresponding field. Copy and save it.
|
|
44
|
-
|
|
45
|
-

|
|
46
|
-
|
|
47
|
-
Finally, let's find the last element that we need to integrate with Testomat.io.
|
|
48
|
-
|
|
49
|
-
To create a **Project Access Token**:
|
|
50
|
-
|
|
51
|
-
1. Click on the **profile icon**
|
|
52
|
-
2. Go to the **Edit profile** page
|
|
53
|
-
|
|
54
|
-

|
|
55
|
-
|
|
56
|
-
3. Then go to the **Access token** section
|
|
57
|
-
4. Click on the **Add new token** button
|
|
58
|
-
|
|
59
|
-

|
|
60
|
-
|
|
61
|
-
5. Name your token
|
|
62
|
-
6. Select the **api** option to give the token the required access level for API operations
|
|
63
|
-
7. Click the **Create personal access token** button
|
|
64
|
-
|
|
65
|
-

|
|
66
|
-
|
|
67
|
-
8. Once the token has been created, copy it.
|
|
68
|
-
|
|
69
|
-

|
|
70
|
-
|
|
71
|
-
Keep your **Project Access Token** secure, as you’ll need it for the integration with Testomat.io.
|
|
72
|
-
|
|
73
|
-
After collecting all necessary data, we can move on to Testomat.io.
|
|
74
|
-
|
|
75
|
-
1. Select **GitLab** from the list of available Issue Management Systems.
|
|
76
|
-
|
|
77
|
-

|
|
78
|
-
|
|
79
|
-
2. Enter a **Profile Name**
|
|
80
|
-
3. Select your GitLab type:
|
|
81
|
-
**GitLab SaaS** for the cloud version
|
|
82
|
-
**Self-hosted GitLab** for your own installation
|
|
83
|
-
4. If using Self-hosted GitLab, enter your GitLab URL (e.g., https://gitlab.yourdomain.com )
|
|
84
|
-
5. Paste GitLab **Group Name**
|
|
85
|
-
6. Paste GitLab **Project Access Token**
|
|
86
|
-
7. Paste GitLab **Project ID**
|
|
87
|
-
8. Click on **Save** button
|
|
88
|
-
|
|
89
|
-

|
|
90
|
-
|
|
91
|
-
If everything was done correctly, you will receive a confirmation message indicating that the GitLab profile was successfully created.
|
|
92
|
-
|
|
93
|
-

|
|
@@ -1,131 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Issues Management Systems
|
|
3
|
-
description: Learn how to integrate issues management systems like Jira, GitHub, Azure DevOps with Testomat.io. This guide covers configuring connections to these systems, creating issues from test results, and linking tests to tickets. Streamline defect management by reporting failed tests directly from the test management platform, improving traceability and issue resolution.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/221125834-31a351a7-48ee-472c-a8b2-1f2bfaaef39d.Cfh-wOie_Z1LVMN4.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: Testomat.io, issues management, Jira integration, GitHub issues, Azure DevOps, Linear, defect management, QA tools, test tracking, issue linking, automation, test defects, failed test
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
import DirectoryLinks from /src/components/DirectoryLinks.astro;
|
|
19
|
-
|
|
20
|
-
Quality assurance is closely connected to Issue management, which means the process of identifying and addressing any problems that occur over the course of a project. This involves documenting the issues and resolving them through review and consideration of all relevant information. Testomat.io provides Issues Management Systems integration to meet this need and link your testing data to your Issue Management System.
|
|
21
|
-
|
|
22
|
-
Namely, you can link tests and suites to your tickets (helps to provide tests coverage) and create defects for failed tests from run reports or ongoing manual runs.
|
|
23
|
-
|
|
24
|
-
Testomat.io provides integration for Issues Management Systems:
|
|
25
|
-
|
|
26
|
-
<DirectoryLinks directory="integrations/issues-management" />
|
|
27
|
-
|
|
28
|
-
See how to connect your Issues Management System and how to link your tests to issues below.
|
|
29
|
-
|
|
30
|
-
## How to Connect to IMS
|
|
31
|
-
|
|
32
|
-
1. Go to Settings
|
|
33
|
-
2. Click on the Issues Management Button
|
|
34
|
-
3. Click on Connect to IMS button
|
|
35
|
-
|
|
36
|
-

|
|
37
|
-
|
|
38
|
-
4. Pick the Issues Management profile
|
|
39
|
-
5. Set up the Issues Management profile
|
|
40
|
-
6. Create tickets directly from Testomat.io
|
|
41
|
-
|
|
42
|
-
## How to Link Issue to Test with IMS Connection
|
|
43
|
-
|
|
44
|
-
You can link issues to:
|
|
45
|
-
|
|
46
|
-
- Tests
|
|
47
|
-
- Suites
|
|
48
|
-
- Runs
|
|
49
|
-
- Failed Test Runs
|
|
50
|
-
|
|
51
|
-
Linking issues connects testing activities with development work. It helps teams understand why a test exists, what functionality or defect it relates to, and which tests should be executed to validate changes or verify bug fixes.
|
|
52
|
-
|
|
53
|
-
1. Navigate to the **Tests** page
|
|
54
|
-
2. Open any existing test or suite
|
|
55
|
-
3. Click the **...** extra menu
|
|
56
|
-
4. Select the **Link to Issue**
|
|
57
|
-
|
|
58
|
-

|
|
59
|
-
|
|
60
|
-
5. Click the **Create new issue** button
|
|
61
|
-
|
|
62
|
-
- Or insert a link / Jira ID for the existing ticket (optional)
|
|
63
|
-
|
|
64
|
-

|
|
65
|
-
|
|
66
|
-
6. Select the **Issue Management System** profile
|
|
67
|
-
7. Enter title for your ticket
|
|
68
|
-
8. Enter description (optional)
|
|
69
|
-
9. Click the **Create Issue** button
|
|
70
|
-
|
|
71
|
-

|
|
72
|
-
|
|
73
|
-
The linked issue will appear in the UI:
|
|
74
|
-
|
|
75
|
-

|
|
76
|
-
|
|
77
|
-
## How to Link Issue to Test without Connecting to IMS
|
|
78
|
-
|
|
79
|
-
You can link external issues to a Test, Suite, Failed Test Runs, or Run Report even without configuring an Issues Management System integration.
|
|
80
|
-
|
|
81
|
-
This is useful when you want to reference related work — such as bug reports, support tickets, or external tracking tools — while keeping testing context centralized in Testomat.io.
|
|
82
|
-
|
|
83
|
-
1. Navigate to the **Tests** page
|
|
84
|
-
2. Open any existing test or suite
|
|
85
|
-
3. Click the **...** extra menu
|
|
86
|
-
4. Select the **Link to Issue**
|
|
87
|
-
|
|
88
|
-

|
|
89
|
-
|
|
90
|
-
5. Paste the issue URL
|
|
91
|
-
6. Click **Link Issue** button
|
|
92
|
-
|
|
93
|
-

|
|
94
|
-
|
|
95
|
-
The linked reference will appear in the UI and remain attached to the selected item.
|
|
96
|
-
|
|
97
|
-
## How to Create Defect For Failed Test
|
|
98
|
-
|
|
99
|
-
Defects can be created directly from failed tests, ensuring issues are reported while context is still fresh. This improves accuracy and speeds up the feedback loop with developers.
|
|
100
|
-
|
|
101
|
-
### Method 1 — From a Run Report
|
|
102
|
-
|
|
103
|
-
1. Navigate to the **Runs** page
|
|
104
|
-
2. Open a **Run Report**
|
|
105
|
-
3. Hover over the failed test and click the **Link Issue** button
|
|
106
|
-
|
|
107
|
-

|
|
108
|
-
|
|
109
|
-
4. Create a new defect or link an existing issue
|
|
110
|
-
|
|
111
|
-

|
|
112
|
-
|
|
113
|
-
### Method 2 — From an Ongoing Manual Run
|
|
114
|
-
|
|
115
|
-
1. Navigate to the **Runs** page
|
|
116
|
-
2. Open an ongoing run
|
|
117
|
-
3. Click the **...** extra menu
|
|
118
|
-
4. Click the **Link Defect** option
|
|
119
|
-
|
|
120
|
-

|
|
121
|
-
|
|
122
|
-
5. Create a new defect or link an existing issue
|
|
123
|
-
|
|
124
|
-

|
|
125
|
-
|
|
126
|
-
**Why this matters:**
|
|
127
|
-
|
|
128
|
-
- **Preserves execution context:** All relevant information—steps, environment, screenshots, and logs—is automatically attached to the defect, making it easier for developers to reproduce and fix the issue.
|
|
129
|
-
- **Reduces forgotten or duplicate bug reports:** By creating defects directly from failed tests, QA teams avoid missing issues or accidentally reporting the same bug multiple times.
|
|
130
|
-
- **Provides immediate traceability:** Links between test failures and IMS issues ensure you can quickly see which tests verify a fix and which features are impacted.
|
|
131
|
-
- **Speeds up regression verification:** Developers and QA can quickly re-run linked tests to confirm fixes, improving efficiency in release cycles.
|
|
@@ -1,164 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Jira
|
|
3
|
-
description: The Jira integration for Testomat.io allows two-way synchronization of test cases and issues. By connecting a Testomat.io project to a Jira project, users can manage test cases, execute tests, and link them to Jira issues. The setup involves installing the Testomat.io plugin and providing connection details, such as an API token or password, to enable seamless integration.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management/jira
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/191561367-9e4be6fc-2f06-414d-a590-5ae85ee2d26b.DDEoSJfA_1OC1KS.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: Jira integration, Testomat.io, test management, issue tracking, API token, two-way sync, test cases, Jira Cloud, Jira Server, plugin installation, Testomat.io Jira plugin, Jira test management integration, connect Testomat.io to Jira
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
The Testomat.io Plugin for Jira is an integration tool that allows QA engineers, developers, and product teams to manage tests directly inside Jira. With this plugin you can link test cases, report execution results, and track testing progress without leaving your Jira workspace.
|
|
19
|
-
|
|
20
|
-
- Bridge the gap between test management and issue tracking
|
|
21
|
-
- Simplify QA and development collaboration
|
|
22
|
-
- Ensure full traceability between Jira issues and Testomat.io test cases
|
|
23
|
-
|
|
24
|
-
## Requirements
|
|
25
|
-
|
|
26
|
-
Before starting integration, ensure you have:
|
|
27
|
-
|
|
28
|
-
- Jira Cloud or Jira Server access
|
|
29
|
-
- Administrator rights in Jira workspace
|
|
30
|
-
- Project Manager or Owner role in Testomat.io project
|
|
31
|
-
|
|
32
|
-
## How to Install Testomat.io Plugin in Jira
|
|
33
|
-
|
|
34
|
-
- **Cloud:** Install [Testomat.io Plugin from Atlassian Marketplace](https://marketplace.atlassian.com/apps/1224120/testomatio?hosting=cloud&tab=overview)
|
|
35
|
-
- **Jira Server**: Contact [Testomat.io Team](https://docs.testomat.io/support/)
|
|
36
|
-
|
|
37
|
-
## Jira Connection Types
|
|
38
|
-
|
|
39
|
-
When connecting your Jira project to Testomat.io, you can use either an **Administrator’s account** or a **Regular account**. The connection type determines who in Jira can review linked tests, suites, and results.
|
|
40
|
-
|
|
41
|
-
### Connect Jira with an Administrator’s Account
|
|
42
|
-
|
|
43
|
-
This option grants **read-only visibility** to all Jira users, even if they don’t have a Testomat.io account.
|
|
44
|
-
|
|
45
|
-
- Linked tests, suites, and run results are visible to all Jira users via the plugin
|
|
46
|
-
- Test Coverage visibility is enabled to all Jira users via the plugin
|
|
47
|
-
- Editing test cases or executing runs is available only to logged-in Testomat.io users with proper permissions
|
|
48
|
-
- Requires Jira admin rights to install webhooks and write data to Jira as properties
|
|
49
|
-
|
|
50
|
-
Use this setup if you want all Jira users to see testing data, but only authorized Testomat.io users can modify it.
|
|
51
|
-
|
|
52
|
-

|
|
53
|
-
|
|
54
|
-
### Connect Jira with a Regular Account
|
|
55
|
-
|
|
56
|
-
This option limits plugin visibility to only **authorized Testomat.io users**.
|
|
57
|
-
|
|
58
|
-
- Linked tests and run results in the Jira plugin are visible only to users who are logged in to Testomat.io
|
|
59
|
-
- Editing or executing tests also requires a Testomat.io login and proper permissions
|
|
60
|
-
- Requires permissions to create and link issues
|
|
61
|
-
|
|
62
|
-
Use this setup if you need to restrict access to test data.
|
|
63
|
-
|
|
64
|
-

|
|
65
|
-
|
|
66
|
-
## How to Connect to Jira Project
|
|
67
|
-
|
|
68
|
-
:::note
|
|
69
|
-
|
|
70
|
-
Connecting a Jira project requires Jira **administrator rights** to enable two-way integration features, such as editing test cases or executing tests directly in Jira.
|
|
71
|
-
The user who configures the integration in Project Settings → Jira Integration must have Jira admin rights; otherwise, the Testomat.io project cannot be connected.
|
|
72
|
-
|
|
73
|
-
:::
|
|
74
|
-
|
|
75
|
-
You can connect your Testomat.io project to Jira to enable linking between tests and Jira issues. Follow the steps below to set up the integration.
|
|
76
|
-
|
|
77
|
-
1. Navigate to **Settings** in the sidebar
|
|
78
|
-
2. Click on **JIRA integration**
|
|
79
|
-
3. Click **Add Jira project** button
|
|
80
|
-
|
|
81
|
-

|
|
82
|
-
|
|
83
|
-
Once **New Jira project** window opens in the sidebar, fill in details:
|
|
84
|
-
|
|
85
|
-
At this stage, select the appropriate [Jira connection type](https://docs.testomat.io/integrations/issues-management/jira/#jira-connection-types)
|
|
86
|
-
based on the level of access you want to grant.
|
|
87
|
-
|
|
88
|
-
4. **Email (Cloud)** or **Username (On Premise)** (required)
|
|
89
|
-
5. **API Token (Cloud)** or **Password (On Premise)** (required)
|
|
90
|
-
6. **Jira URL** (required)
|
|
91
|
-
7. **Project ID** (required)
|
|
92
|
-
8. **Context Path** (optional, for Jira On Premise only)
|
|
93
|
-
9. Click **Save** button
|
|
94
|
-
|
|
95
|
-

|
|
96
|
-
|
|
97
|
-
Once the project is connected you will see your integration listed on the **Jira integration** page.
|
|
98
|
-
|
|
99
|
-
10. Open the Jira integration again and click the **Test Connection** button to ensure that it is connected properly
|
|
100
|
-
|
|
101
|
-

|
|
102
|
-
|
|
103
|
-
11. Click the **Install Webhook** button to enable automatic unlinking of items when a related Jira issue is deleted
|
|
104
|
-
|
|
105
|
-

|
|
106
|
-
|
|
107
|
-
:::note
|
|
108
|
-
|
|
109
|
-
Webhook installation requires **Jira administrator permissions**. If you don’t have **admin rights**, you can use the **Synchronize with Jira** option in the Jira Settings menu to manually sync test cases and issues.
|
|
110
|
-
|
|
111
|
-
:::
|
|
112
|
-
|
|
113
|
-
## Supported Jira Field Types
|
|
114
|
-
|
|
115
|
-
Testomat.io integrates with Jira and supports the following field types when creating or editing issues:
|
|
116
|
-
|
|
117
|
-
### Basic Field Types
|
|
118
|
-
|
|
119
|
-
- **Text fields** — for entering single-line or multi-line text
|
|
120
|
-
- **Number fields** — for entering numeric values
|
|
121
|
-
- **Date fields** — for selecting dates and times
|
|
122
|
-
- **Dropdown menus** — for selecting a single option from a list
|
|
123
|
-
- **Priority fields** — for setting issue priority levels
|
|
124
|
-
|
|
125
|
-
### Advanced Field Types
|
|
126
|
-
|
|
127
|
-
- **Checkboxes** — for selecting multiple options from a set of checkboxes
|
|
128
|
-
- **Multi-select fields** — for choosing multiple values from dropdown lists
|
|
129
|
-
- **Custom fields (single, multiple, cascading)** — for selecting single, multiple, or nested values from Jira custom select lists
|
|
130
|
-
- **Issue links** — for connecting to other Jira issues
|
|
131
|
-
|
|
132
|
-
### Special Handling
|
|
133
|
-
|
|
134
|
-
- **Text arrays** — multiple text values can be entered, separated by commas
|
|
135
|
-
- **Default values** — the system respects default values set in Jira
|
|
136
|
-
|
|
137
|
-
### Not Supported
|
|
138
|
-
|
|
139
|
-
Some Jira fields are not currently supported in our integration:
|
|
140
|
-
|
|
141
|
-
- Attachments
|
|
142
|
-
- Assignee and Reporter fields
|
|
143
|
-
- Description (handled separately in our interface)
|
|
144
|
-
- Issue type (selected elsewhere in our interface)
|
|
145
|
-
- Project field (selected elsewhere in our interface)
|
|
146
|
-
- Labels (not currently supported)
|
|
147
|
-
- Fields named **Flagged** or **Sprint**
|
|
148
|
-
|
|
149
|
-
You can connect multiple Jira projects to a single Testomat.io project by following the same steps for each additional connection.
|
|
150
|
-
|
|
151
|
-

|
|
152
|
-
|
|
153
|
-
## FAQ & Troubleshooting
|
|
154
|
-
|
|
155
|
-
**Q: Why do I see the message: 'Oops! No project is linked.' in Jira?**
|
|
156
|
-
|
|
157
|
-
A: This message appears when the Jira Plugin cannot access the linked project:
|
|
158
|
-
|
|
159
|
-
- You don’t have access to the project in Testomat.io and cannot view it in Jira.
|
|
160
|
-
- Or the integration was set up using a Regular Account, and you are not logged in to Testomat.io.
|
|
161
|
-
|
|
162
|
-
**Q: Why do I get a "Forbidden" message when linking a Jira project?**
|
|
163
|
-
|
|
164
|
-
A: Your Jira instance may require adding Testomat.io’s IP addresses to the IP allowlist. Please contact your admin for assistance. The Testomat.io IPs are: 142.132.185.19, 5.75.250.20 and 88.99.148.154.
|
|
@@ -1,29 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Linear Configuration
|
|
3
|
-
description: Integrate Linear with Testomat.io to streamline issue tracking directly from your test management system. This setup involves configuring a profile with your Linear Personal Access Token and team name. Once integrated, you can link tests or create defects, automatically generating tickets in Linear with testing data for easy tracking.
|
|
4
|
-
type: article
|
|
5
|
-
url: https://docs.testomat.io/integrations/issues-management/linear
|
|
6
|
-
head:
|
|
7
|
-
- tag: meta
|
|
8
|
-
attrs:
|
|
9
|
-
name: og:image
|
|
10
|
-
content: https://docs.testomat.io/_astro/221125834-31a351a7-48ee-472c-a8b2-1f2bfaaef39d.Cfh-wOie_Z1LVMN4.webp
|
|
11
|
-
|
|
12
|
-
- tag: meta
|
|
13
|
-
attrs:
|
|
14
|
-
name: keywords
|
|
15
|
-
content: Linear integration, Testomat.io, issue tracking, Personal Access Token, defect creation, test management, team configuration, testing workflows
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-

|
|
19
|
-
|
|
20
|
-
1. Give a name to your profile
|
|
21
|
-
2. Enter your Personal Access Token from Linear ([learn more](https://linear.app/testomat-workspace/settings/api))
|
|
22
|
-
3. Enter your Team name ([more details on Linear Teams](https://linear.app/docs/teams))
|
|
23
|
-
4. Click on Save button
|
|
24
|
-
|
|
25
|
-

|
|
26
|
-
|
|
27
|
-
Once your Issues Management System is configured you can link a test or create a defect. As a result, Testomat.io will create a ticket in your Linear Team with dedicated links and data, so you can easily look through the testing data you need. Here is an example:
|
|
28
|
-
|
|
29
|
-

|