From 2ae466954cfa1e2ccb3d363e4021f675bb797c46 Mon Sep 17 00:00:00 2001 From: Bharath Krishna <118433150+bharathk08@users.noreply.github.com> Date: Tue, 18 Aug 2026 18:51:28 +0530 Subject: [PATCH 1/3] Revert "udpated arcus slug instead of test-management (#144)" This reverts commit 0817595dcae7e7d3f2cc340ff113b4f28749f0e9. --- gatsby-node.js | 10 +- src/left-nav-title.json | 178 +++++++-------- .../arcus/introduction/getting-started.md | 47 ---- src/pages/docs/arcus/introduction/overview.md | 117 ---------- src/pages/docs/arcus/qi-home/overview.md | 194 ----------------- .../arcus/qi-home/plugins/connect-codex.md | 199 ----------------- .../arcus/qi-home/plugins/connect-cursor.md | 198 ----------------- .../qi-home/plugins/connect-github-copilot.md | 202 ------------------ .../api-reference/modules.md | 12 +- .../api-reference/overview.md | 0 .../ci-cd-integrations/azure-devops.md | 18 +- .../ci-cd-integrations/circleci.md | 18 +- .../ci-cd-integrations/github.md | 16 +- .../ci-cd-integrations/gitlab.md | 18 +- .../ci-cd-integrations/jenkins.md | 20 +- .../ci-cd-integrations/travis-ci.md | 18 +- .../data-sets/manage-data-sets.md | 10 +- .../imports-and-exports/browserstack.md | 10 +- .../imports-and-exports/csv-file.md | 8 +- .../imports-and-exports/export-tests.md | 6 +- .../imports-and-exports/testrail.md | 8 +- .../imports-and-exports/zephyr.md | 10 +- .../docs/{arcus => test-management}/index.jsx | 0 .../integrations/azure-devops.md | 12 +- .../manage-test-cases-in-azure-devops.md | 16 +- .../manage-test-runs-in-azure-devops.md | 18 +- ...stsigma-integration-app-for-azuredevops.md | 12 +- .../integrations/clickup.md | 8 +- .../integrations/confluence.md | 8 +- .../integrations/figma.md | 6 +- .../install-and-connect-testsigma.md | 18 +- .../manage-test-cases-in-jira.md | 16 +- .../manage-test-runs-in-jira.md | 18 +- .../integrations/jira.md | 8 +- .../integrations/linear.md | 8 +- .../introduction/getting-started.md | 61 ++++++ .../test-management/introduction/overview.md | 49 +++++ .../manage-users/invite-users.md | 10 +- .../projects/manage-projects.md | 8 +- .../projects/project-settings.md | 10 +- .../qi-home/ad-hoc/attach-context-sources.md | 16 +- .../qi-home/ad-hoc/generate-test-cases.md | 28 +-- .../qi-home/ad-hoc/write-effective-prompts.md | 16 +- .../learn-test-case-live-cloud.md | 18 +- .../learn-test-case-live-local.md | 8 +- .../live-learning-controls.md | 28 +-- .../run-automated-test-case-with-copilot.md | 4 +- .../copilot/execute-test-case-in-cloud.md | 4 +- .../copilot/execute-test-case-in-local.md | 4 +- .../copilot/execution-controls-in-copilot.md | 0 .../context-mapping}/connect-claude-code.md | 90 +------- .../qi-home/context-mapping/connect-codex.md | 117 ++++++++++ .../qi-home/context-mapping/connect-cursor.md | 116 ++++++++++ .../context-mapping/connect-github-copilot.md | 120 +++++++++++ .../context-mapping}/connect-github.md | 8 +- .../context-mapping}/map-developer-context.md | 20 +- .../qi-home/context-mapping}/map-github.md | 14 +- .../qi-home/context-mapping}/overview.md | 40 ++-- .../qi-home/coverage-and-gaps.md | 12 +- .../qi-home/faqs.md | 34 +-- .../docs/test-management/qi-home/overview.md | 194 +++++++++++++++++ .../qi-home/quality-intelligence-metrics.md | 6 +- .../qi-home/review-and-accept-test-cases.md | 12 +- .../qi-home/sprints/generate-test-cases.md | 40 ++-- .../qi-home/test-plans.md | 26 +-- .../qi-home/use-playground.md | 16 +- .../reports/create-report.md | 6 +- .../reports/dashboard-reports.md | 4 +- .../requirement-traceability-report.md | 4 +- .../reports/view-reports.md | 6 +- .../settings/api-keys.md | 4 +- .../settings/audit-logs.md | 10 +- .../settings/custom-fields.md | 6 +- .../settings/labels.md | 8 +- .../settings/manage-access.md | 4 +- .../settings/manage-properties.md | 4 +- .../settings/notifications/email.md | 6 +- .../settings/notifications/microsoft-teams.md | 2 +- .../settings/notifications/overview.md | 6 +- .../settings/notifications/slack.md | 2 +- .../settings/smtp-configuration.md | 8 +- .../step-groups/create-step-groups.md | 8 +- .../step-groups/manage-step-groups.md | 6 +- .../test-capture/capture-logs.md | 0 .../test-capture/install-and-configure.md | 16 +- .../test-capture/overview.md | 6 +- .../test-cases/clone-test-cases.md | 8 +- .../test-cases/comment-in-test-cases.md | 4 +- .../customize-test-case-list-view.md | 8 +- .../test-cases/filter-test-cases.md | 6 +- .../test-cases/folders.md | 8 +- .../test-cases/manage-test-cases.md | 6 +- .../test-cases/review-management.md | 10 +- .../test-cases/run-history.md | 6 +- .../test-cases/test-case-templates.md | 8 +- .../test-cases/versions.md | 4 +- .../test-plans/manage-test-plans.md | 6 +- .../test-plans/share-test-plans.md | 4 +- .../test-runs/create-test-runs.md | 8 +- .../test-runs/manage-test-runs.md | 8 +- .../test-runs/share-test-runs.md | 4 +- .../test-runs/test-run-properties.md | 6 +- .../automate-manual-test-cases.md | 10 +- .../connect-testsigma.md | 24 +-- .../create-and-sync-test-cases.md | 12 +- .../execute-test-plans.md | 28 +-- .../link-test-cases.md | 18 +- .../link-test-plans.md | 18 +- .../manage-user.md | 22 +- 109 files changed, 1283 insertions(+), 1663 deletions(-) delete mode 100644 src/pages/docs/arcus/introduction/getting-started.md delete mode 100644 src/pages/docs/arcus/introduction/overview.md delete mode 100644 src/pages/docs/arcus/qi-home/overview.md delete mode 100644 src/pages/docs/arcus/qi-home/plugins/connect-codex.md delete mode 100644 src/pages/docs/arcus/qi-home/plugins/connect-cursor.md delete mode 100644 src/pages/docs/arcus/qi-home/plugins/connect-github-copilot.md rename src/pages/docs/{arcus => test-management}/api-reference/modules.md (93%) rename src/pages/docs/{arcus => test-management}/api-reference/overview.md (100%) rename src/pages/docs/{arcus => test-management}/ci-cd-integrations/azure-devops.md (74%) rename src/pages/docs/{arcus => test-management}/ci-cd-integrations/circleci.md (77%) rename src/pages/docs/{arcus => test-management}/ci-cd-integrations/github.md (77%) rename src/pages/docs/{arcus => test-management}/ci-cd-integrations/gitlab.md (74%) rename src/pages/docs/{arcus => test-management}/ci-cd-integrations/jenkins.md (76%) rename src/pages/docs/{arcus => test-management}/ci-cd-integrations/travis-ci.md (73%) rename src/pages/docs/{arcus => test-management}/data-sets/manage-data-sets.md (91%) rename src/pages/docs/{arcus => test-management}/imports-and-exports/browserstack.md (80%) rename src/pages/docs/{arcus => test-management}/imports-and-exports/csv-file.md (87%) rename src/pages/docs/{arcus => test-management}/imports-and-exports/export-tests.md (89%) rename src/pages/docs/{arcus => test-management}/imports-and-exports/testrail.md (78%) rename src/pages/docs/{arcus => test-management}/imports-and-exports/zephyr.md (77%) rename src/pages/docs/{arcus => test-management}/index.jsx (100%) rename src/pages/docs/{arcus => test-management}/integrations/azure-devops.md (76%) rename src/pages/docs/{arcus => test-management}/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md (85%) rename src/pages/docs/{arcus => test-management}/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md (80%) rename src/pages/docs/{arcus => test-management}/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md (87%) rename src/pages/docs/{arcus => test-management}/integrations/clickup.md (84%) rename src/pages/docs/{arcus => test-management}/integrations/confluence.md (87%) rename src/pages/docs/{arcus => test-management}/integrations/figma.md (91%) rename src/pages/docs/{arcus => test-management}/integrations/jira-two-way-integration/install-and-connect-testsigma.md (70%) rename src/pages/docs/{arcus => test-management}/integrations/jira-two-way-integration/manage-test-cases-in-jira.md (83%) rename src/pages/docs/{arcus => test-management}/integrations/jira-two-way-integration/manage-test-runs-in-jira.md (79%) rename src/pages/docs/{arcus => test-management}/integrations/jira.md (84%) rename src/pages/docs/{arcus => test-management}/integrations/linear.md (84%) create mode 100644 src/pages/docs/test-management/introduction/getting-started.md create mode 100644 src/pages/docs/test-management/introduction/overview.md rename src/pages/docs/{arcus => test-management}/manage-users/invite-users.md (74%) rename src/pages/docs/{arcus => test-management}/projects/manage-projects.md (79%) rename src/pages/docs/{arcus => test-management}/projects/project-settings.md (79%) rename src/pages/docs/{arcus => test-management}/qi-home/ad-hoc/attach-context-sources.md (88%) rename src/pages/docs/{arcus => test-management}/qi-home/ad-hoc/generate-test-cases.md (57%) rename src/pages/docs/{arcus => test-management}/qi-home/ad-hoc/write-effective-prompts.md (89%) rename src/pages/docs/{arcus => test-management}/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md (72%) rename src/pages/docs/{arcus => test-management}/qi-home/automation/agentic-learning/learn-test-case-live-local.md (82%) rename src/pages/docs/{arcus => test-management}/qi-home/automation/agentic-learning/live-learning-controls.md (62%) rename src/pages/docs/{arcus => test-management}/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md (89%) rename src/pages/docs/{arcus => test-management}/qi-home/automation/copilot/execute-test-case-in-cloud.md (93%) rename src/pages/docs/{arcus => test-management}/qi-home/automation/copilot/execute-test-case-in-local.md (94%) rename src/pages/docs/{arcus => test-management}/qi-home/automation/copilot/execution-controls-in-copilot.md (100%) rename src/pages/docs/{arcus/qi-home/plugins => test-management/qi-home/context-mapping}/connect-claude-code.md (51%) create mode 100644 src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md create mode 100644 src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md create mode 100644 src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md rename src/pages/docs/{arcus/qi-home/plugins => test-management/qi-home/context-mapping}/connect-github.md (84%) rename src/pages/docs/{arcus/qi-home/plugins => test-management/qi-home/context-mapping}/map-developer-context.md (71%) rename src/pages/docs/{arcus/qi-home/plugins => test-management/qi-home/context-mapping}/map-github.md (79%) rename src/pages/docs/{arcus/qi-home/plugins => test-management/qi-home/context-mapping}/overview.md (62%) rename src/pages/docs/{arcus => test-management}/qi-home/coverage-and-gaps.md (83%) rename src/pages/docs/{arcus => test-management}/qi-home/faqs.md (63%) create mode 100644 src/pages/docs/test-management/qi-home/overview.md rename src/pages/docs/{arcus => test-management}/qi-home/quality-intelligence-metrics.md (91%) rename src/pages/docs/{arcus => test-management}/qi-home/review-and-accept-test-cases.md (79%) rename src/pages/docs/{arcus => test-management}/qi-home/sprints/generate-test-cases.md (56%) rename src/pages/docs/{arcus => test-management}/qi-home/test-plans.md (71%) rename src/pages/docs/{arcus => test-management}/qi-home/use-playground.md (76%) rename src/pages/docs/{arcus => test-management}/reports/create-report.md (88%) rename src/pages/docs/{arcus => test-management}/reports/dashboard-reports.md (95%) rename src/pages/docs/{arcus => test-management}/reports/requirement-traceability-report.md (95%) rename src/pages/docs/{arcus => test-management}/reports/view-reports.md (86%) rename src/pages/docs/{arcus => test-management}/settings/api-keys.md (64%) rename src/pages/docs/{arcus => test-management}/settings/audit-logs.md (76%) rename src/pages/docs/{arcus => test-management}/settings/custom-fields.md (74%) rename src/pages/docs/{arcus => test-management}/settings/labels.md (77%) rename src/pages/docs/{arcus => test-management}/settings/manage-access.md (83%) rename src/pages/docs/{arcus => test-management}/settings/manage-properties.md (91%) rename src/pages/docs/{arcus => test-management}/settings/notifications/email.md (88%) rename src/pages/docs/{arcus => test-management}/settings/notifications/microsoft-teams.md (92%) rename src/pages/docs/{arcus => test-management}/settings/notifications/overview.md (76%) rename src/pages/docs/{arcus => test-management}/settings/notifications/slack.md (92%) rename src/pages/docs/{arcus => test-management}/settings/smtp-configuration.md (89%) rename src/pages/docs/{arcus => test-management}/step-groups/create-step-groups.md (80%) rename src/pages/docs/{arcus => test-management}/step-groups/manage-step-groups.md (83%) rename src/pages/docs/{arcus => test-management}/test-capture/capture-logs.md (100%) rename src/pages/docs/{arcus => test-management}/test-capture/install-and-configure.md (91%) rename src/pages/docs/{arcus => test-management}/test-capture/overview.md (81%) rename src/pages/docs/{arcus => test-management}/test-cases/clone-test-cases.md (92%) rename src/pages/docs/{arcus => test-management}/test-cases/comment-in-test-cases.md (95%) rename src/pages/docs/{arcus => test-management}/test-cases/customize-test-case-list-view.md (66%) rename src/pages/docs/{arcus => test-management}/test-cases/filter-test-cases.md (90%) rename src/pages/docs/{arcus => test-management}/test-cases/folders.md (77%) rename src/pages/docs/{arcus => test-management}/test-cases/manage-test-cases.md (94%) rename src/pages/docs/{arcus => test-management}/test-cases/review-management.md (83%) rename src/pages/docs/{arcus => test-management}/test-cases/run-history.md (89%) rename src/pages/docs/{arcus => test-management}/test-cases/test-case-templates.md (87%) rename src/pages/docs/{arcus => test-management}/test-cases/versions.md (95%) rename src/pages/docs/{arcus => test-management}/test-plans/manage-test-plans.md (89%) rename src/pages/docs/{arcus => test-management}/test-plans/share-test-plans.md (91%) rename src/pages/docs/{arcus => test-management}/test-runs/create-test-runs.md (92%) rename src/pages/docs/{arcus => test-management}/test-runs/manage-test-runs.md (88%) rename src/pages/docs/{arcus => test-management}/test-runs/share-test-runs.md (91%) rename src/pages/docs/{arcus => test-management}/test-runs/test-run-properties.md (80%) rename src/pages/docs/{arcus => test-management}/testsigma-two-way-integration/automate-manual-test-cases.md (74%) rename src/pages/docs/{arcus => test-management}/testsigma-two-way-integration/connect-testsigma.md (61%) rename src/pages/docs/{arcus => test-management}/testsigma-two-way-integration/create-and-sync-test-cases.md (76%) rename src/pages/docs/{arcus => test-management}/testsigma-two-way-integration/execute-test-plans.md (64%) rename src/pages/docs/{arcus => test-management}/testsigma-two-way-integration/link-test-cases.md (78%) rename src/pages/docs/{arcus => test-management}/testsigma-two-way-integration/link-test-plans.md (70%) rename src/pages/docs/{arcus => test-management}/testsigma-two-way-integration/manage-user.md (64%) diff --git a/gatsby-node.js b/gatsby-node.js index 4f2664d..fd91dfc 100644 --- a/gatsby-node.js +++ b/gatsby-node.js @@ -205,9 +205,9 @@ const writeLlmsTxt = (entries, outPath) => { ); const lines = [ - '# Arcus by Testsigma', + '# Test Management by Testsigma', '', - '> Documentation for Arcus by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto.', + '> Documentation for Test Management by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto.', '', ]; for (const name of sortedGroupNames) { @@ -225,12 +225,12 @@ const writeLlmsTxt = (entries, outPath) => { }; const TM_HOME_MD = `--- -title: 'Arcus by Testsigma' +title: 'Test Management by Testsigma' canonical: 'https://testsigma.com/docs/test-management/' --- -# Arcus by Testsigma — Documentation +# Test Management by Testsigma — Documentation -The complete documentation for Arcus by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto. +The complete documentation for Test Management by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto. See [llms.txt](https://testsigma.com/docs/test-management/llms.txt) for the full document index, or browse top sections: diff --git a/src/left-nav-title.json b/src/left-nav-title.json index 8b03e44..e629ce0 100644 --- a/src/left-nav-title.json +++ b/src/left-nav-title.json @@ -1,267 +1,267 @@ { "introduction": { - "/docs/arcus/introduction/": "Introduction" + "/docs/test-management/introduction/": "Introduction" }, "projects": { - "/docs/arcus/projects/": "Projects" + "/docs/test-management/projects/": "Projects" }, "manage-projects": { - "/docs/arcus/projects/manage-projects/": "Manage Projects" + "/docs/test-management/projects/manage-projects/": "Manage Projects" }, "project-settings": { - "/docs/arcus/projects/project-settings/": "Project Settings" + "/docs/test-management/projects/project-settings/": "Project Settings" }, "folders": { - "/docs/arcus/test-cases/folders/": "Organize Test Cases in Folder" + "/docs/test-management/test-cases/folders/": "Organize Test Cases in Folder" }, "test-cases": { - "/docs/arcus/test-cases/": "Test Cases" + "/docs/test-management/test-cases/": "Test Cases" }, "manage-test-cases": { - "/docs/arcus/test-cases/manage-test-cases": "Manage Test Cases" + "/docs/test-management/test-cases/manage-test-cases": "Manage Test Cases" }, "imports-and-exports": { - "/docs/arcus/imports-and-exports/": "Imports and Exports" + "/docs/test-management/imports-and-exports/": "Imports and Exports" }, "overview": { - "/docs/arcus/introduction/overview/": "Overview" + "/docs/test-management/introduction/overview/": "Overview" }, "getting-started": { - "/docs/arcus/introduction/getting-started/": "Getting Started" + "/docs/test-management/introduction/getting-started/": "Getting Started" }, "test-case-templates": { - "/docs/arcus/test-cases/test-case-templates/": "Test Case Templates" + "/docs/test-management/test-cases/test-case-templates/": "Test Case Templates" }, "csv-file": { - "/docs/arcus/imports-and-exports/csv-file/": "Import Test Data from CSV Files" + "/docs/test-management/imports-and-exports/csv-file/": "Import Test Data from CSV Files" }, "zephyr": { - "/docs/arcus/imports-and-exports/zephyr/": "Import Test Data from Zephyr" + "/docs/test-management/imports-and-exports/zephyr/": "Import Test Data from Zephyr" }, "testrail": { - "/docs/arcus/imports-and-exports/testrail/": "Import Test Data from Testrail" + "/docs/test-management/imports-and-exports/testrail/": "Import Test Data from Testrail" }, "browserstack": { - "/docs/arcus/imports-and-exports/browserstack/": "Import Test Data from Browserstack" + "/docs/test-management/imports-and-exports/browserstack/": "Import Test Data from Browserstack" }, "export-tests": { - "/docs/arcus/imports-and-exports/export-tests/": "Export Test Data" + "/docs/test-management/imports-and-exports/export-tests/": "Export Test Data" }, "step-groups": { - "/docs/arcus/step-groups/create-step-groups/": "Creating Step Groups" + "/docs/test-management/step-groups/create-step-groups/": "Creating Step Groups" }, "step-groups": { - "/docs/arcus/step-groups/": "Step Groups" + "/docs/test-management/step-groups/": "Step Groups" }, "test-runs": { - "/docs/arcus/test-runs/": "Test Runs" + "/docs/test-management/test-runs/": "Test Runs" }, "test-plans": { - "/docs/arcus/test-plans/": "Test Plans" + "/docs/test-management/test-plans/": "Test Plans" }, "integrations": { - "/docs/arcus/integrations": "Integrations" + "/docs/test-management/integrations": "Integrations" }, "jira": { - "/docs/arcus/integrations/jira": "Jira Integration" + "/docs/test-management/integrations/jira": "Jira Integration" }, "figma": { - "/docs/arcus/integrations/figma": "Figma Integration" + "/docs/test-management/integrations/figma": "Figma Integration" }, "settings": { - "/docs/arcus/settings/": "Settings" + "/docs/test-management/settings/": "Settings" }, "global-settings": { - "/docs/arcus/settings/global-settings/": "Arcus Settings" + "/docs/test-management/settings/global-settings/": "Test Management Settings" }, "manage-users": { - "/docs/arcus/manage-users/": "Manage Users" + "/docs/test-management/manage-users/": "Manage Users" }, "atto": { - "/docs/arcus/atto/": "Atto (Agentic AI ✨)" + "/docs/test-management/atto/": "Atto (Agentic AI ✨)" }, "generator-agent": { - "/docs/arcus/atto/generator-agent/": "Generator Agent" + "/docs/test-management/atto/generator-agent/": "Generator Agent" }, "executor-agent": { - "/docs/arcus/atto/executor-agent/": "Executor Agent" + "/docs/test-management/atto/executor-agent/": "Executor Agent" }, "manage-properties": { - "/docs/arcus/settings/manage-properties/": "Test Properties" + "/docs/test-management/settings/manage-properties/": "Test Properties" }, "custom-fields": { - "/docs/arcus/settings/custom-fields/": "Custom Fields" + "/docs/test-management/settings/custom-fields/": "Custom Fields" }, "labels": { - "/docs/arcus/settings/labels/": "Labels" + "/docs/test-management/settings/labels/": "Labels" }, "api-keys": { - "/docs/arcus/settings/api-keys/": "API Keys" + "/docs/test-management/settings/api-keys/": "API Keys" }, "manage-access": { - "/docs/arcus/settings/manage-access/": "Manage Access" + "/docs/test-management/settings/manage-access/": "Manage Access" }, "bug-reporter-agent": { - "/docs/arcus/atto/bug-reporter-agent/": "Bug Reporter Agent" + "/docs/test-management/atto/bug-reporter-agent/": "Bug Reporter Agent" }, "reports": { - "/docs/arcus/reports/": "Reports & Analytics" + "/docs/test-management/reports/": "Reports & Analytics" }, "manage-sprints": { - "/docs/arcus/atto/sprint-planner/manage-sprints/": "Manage Jira Sprints" + "/docs/test-management/atto/sprint-planner/manage-sprints/": "Manage Jira Sprints" }, "api-reference": { - "/docs/arcus/api-reference": "API Reference" + "/docs/test-management/api-reference": "API Reference" }, "modules": { - "/docs/arcus/api-reference/modules": "API Modules" + "/docs/test-management/api-reference/modules": "API Modules" }, "jenkins": { - "/docs/arcus/ci-cd-integrations/jenkins/": "Jenkins" + "/docs/test-management/ci-cd-integrations/jenkins/": "Jenkins" }, "ci-cd-integrations": { - "/docs/arcus/ci-cd-integrations/": "CI/CD Integrations" + "/docs/test-management/ci-cd-integrations/": "CI/CD Integrations" }, "github": { - "/docs/arcus/ci-cd-integrations/github": "GitHub" + "/docs/test-management/ci-cd-integrations/github": "GitHub" }, "travis-ci": { - "/docs/arcus/ci-cd-integrations/travis-ci": "Travis CI" + "/docs/test-management/ci-cd-integrations/travis-ci": "Travis CI" }, "circleci": { - "/docs/arcus/ci-cd-integrations/circleci": "CircleCI" + "/docs/test-management/ci-cd-integrations/circleci": "CircleCI" }, "versions": { - "/docs/arcus/test-cases/versions/": "Versions" + "/docs/test-management/test-cases/versions/": "Versions" }, "sprint-planner": { - "/docs/arcus/atto/sprint-planner/": "Sprint Planner Agent" + "/docs/test-management/atto/sprint-planner/": "Sprint Planner Agent" }, "jira-two-way-integration": { - "/docs/arcus/integrations/jira-two-way-integration/": "Jira Two-way Integration" + "/docs/test-management/integrations/jira-two-way-integration/": "Jira Two-way Integration" }, "generating-test-cases": { - "/docs/arcus/atto/best-practices/generating-test-cases/": "Generating Test Cases" + "/docs/test-management/atto/best-practices/generating-test-cases/": "Generating Test Cases" }, "writing-best-prompts": { - "/docs/arcus/atto/best-practices/writing-best-prompts/": "Writing Effective Prompts" + "/docs/test-management/atto/best-practices/writing-best-prompts/": "Writing Effective Prompts" }, "best-practices": { - "/docs/arcus/atto/best-practices/": "Best Practices" + "/docs/test-management/atto/best-practices/": "Best Practices" }, "manage-linear-cycles": { - "/docs/arcus/atto/sprint-planner/manage-linear-cycles/": "Manage Linear Cycles" + "/docs/test-management/atto/sprint-planner/manage-linear-cycles/": "Manage Linear Cycles" }, "linear": { - "/docs/arcus/integrations/linear/": "Linear Integration" + "/docs/test-management/integrations/linear/": "Linear Integration" }, "audit-logs": { - "/docs/arcus/settings/audit-logs/": "Audit Logs" + "/docs/test-management/settings/audit-logs/": "Audit Logs" }, "generate-tests-from-clickup": { - "/docs/arcus/atto/generator-agent/generate-tests-from-clickup/": "Generate Test Cases from ClickUp" + "/docs/test-management/atto/generator-agent/generate-tests-from-clickup/": "Generate Test Cases from ClickUp" }, "clickup": { - "/docs/arcus/integrations/clickup/": "ClickUp Integration" + "/docs/test-management/integrations/clickup/": "ClickUp Integration" }, "manage-clickup-tasks": { - "/docs/arcus/atto/sprint-planner/manage-clickup-tasks/": "Manage ClickUp Tasks" + "/docs/test-management/atto/sprint-planner/manage-clickup-tasks/": "Manage ClickUp Tasks" }, "gitlab": { - "/docs/arcus/ci-cd-integrations/gitlab/": "GitLab" + "/docs/test-management/ci-cd-integrations/gitlab/": "GitLab" }, "testsigma-two-way-integration": { - "/docs/arcus/testsigma-two-way-integration/": "Testsigma Two-way Integration" + "/docs/test-management/testsigma-two-way-integration/": "Testsigma Two-way Integration" }, "connect-testsigma": { - "/docs/arcus/testsigma-two-way-integration/connect-testsigma/": "Connect Testsigma" + "/docs/test-management/testsigma-two-way-integration/connect-testsigma/": "Connect Testsigma" }, "link-test-cases": { - "/docs/arcus/testsigma-two-way-integration/link-test-cases/": "Link Test Cases" + "/docs/test-management/testsigma-two-way-integration/link-test-cases/": "Link Test Cases" }, "manage-user": { - "/docs/arcus/testsigma-two-way-integration/manage-user/": "Manage Users" + "/docs/test-management/testsigma-two-way-integration/manage-user/": "Manage Users" }, "link-test-plans": { - "/docs/arcus/testsigma-two-way-integration/link-test-plans/": "Link Test Plans" + "/docs/test-management/testsigma-two-way-integration/link-test-plans/": "Link Test Plans" }, "execute-test-plans": { - "/docs/arcus/testsigma-two-way-integration/execute-test-plans/": "Execute Test Plans" + "/docs/test-management/testsigma-two-way-integration/execute-test-plans/": "Execute Test Plans" }, "automate-manual-test-cases": { - "/docs/arcus/testsigma-two-way-integration/automate-manual-test-cases/": "Automate Manual Tests" + "/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases/": "Automate Manual Tests" }, "create-and-sync-test-cases": { - "/docs/arcus/testsigma-two-way-integration/create-and-sync-test-cases/": "Create & Sync Test Cases" + "/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases/": "Create & Sync Test Cases" }, "notifications": { - "/docs/arcus/settings/notifications": "Notifications 🔔" + "/docs/test-management/settings/notifications": "Notifications 🔔" }, "smtp-configuration": { - "/docs/arcus/settings/smtp-configuration/": "SMTP Configuration" + "/docs/test-management/settings/smtp-configuration/": "SMTP Configuration" }, "email": { - "/docs/arcus/settings/notifications/email": "Email" + "/docs/test-management/settings/notifications/email": "Email" }, "slack": { - "/docs/arcus/settings/notifications/slack": "Slack" + "/docs/test-management/settings/notifications/slack": "Slack" }, "microsoft-teams": { - "/docs/arcus/settings/notifications/microsoft-teams": "MS Teams" + "/docs/test-management/settings/notifications/microsoft-teams": "MS Teams" }, "review-management": { - "/docs/arcus/test-cases/review-management": "Review Management" + "/docs/test-management/test-cases/review-management": "Review Management" }, "clone-test-cases": { - "/docs/arcus/test-cases/clone-test-cases": "Clone Test Cases" + "/docs/test-management/test-cases/clone-test-cases": "Clone Test Cases" }, "comment-in-test-cases": { - "/docs/arcus/test-cases/comment-in-test-cases": "Comment in Test Cases" + "/docs/test-management/test-cases/comment-in-test-cases": "Comment in Test Cases" }, "confluence": { - "/docs/arcus/integrations/confluence/": "Confluence Integration" + "/docs/test-management/integrations/confluence/": "Confluence Integration" }, "generate-tests-from-confluence": { - "/docs/arcus/atto/generator-agent/generate-tests-from-confluence/": "Generate Test Cases from Confluence" + "/docs/test-management/atto/generator-agent/generate-tests-from-confluence/": "Generate Test Cases from Confluence" }, "run-history": { - "/docs/arcus/test-cases/run-history/": "View Run History" + "/docs/test-management/test-cases/run-history/": "View Run History" }, "data-sets": { - "/docs/arcus/data-sets/": "Data Sets" + "/docs/test-management/data-sets/": "Data Sets" }, "manage-data-sets": { - "/docs/arcus/data-sets/manage-data-sets/": "Manage Data Sets" + "/docs/test-management/data-sets/manage-data-sets/": "Manage Data Sets" }, "azure-two-way-integration": { - "/docs/arcus/integrations/azure-two-way-integration/": "Azure DevOps Two-way Integration" + "/docs/test-management/integrations/azure-two-way-integration/": "Azure DevOps Two-way Integration" }, "azure-devops": { - "/docs/arcus/integrations/azure-devops": "Azure DevOps Integration", - "/docs/arcus/ci-cd-integrations/azure-devops/":"Azure DevOps" + "/docs/test-management/integrations/azure-devops": "Azure DevOps Integration", + "/docs/test-management/ci-cd-integrations/azure-devops/":"Azure DevOps" }, "manage-azure-devops-work-items": { - "/docs/arcus/atto/sprint-planner/manage-azure-devops-work-items/": "Manage Azure DevOps Work Items" + "/docs/test-management/atto/sprint-planner/manage-azure-devops-work-items/": "Manage Azure DevOps Work Items" }, "qi-home": { - "/docs/arcus/qi-home/": "QI Home" + "/docs/test-management/qi-home/": "QI Home" }, "ad-hoc": { - "/docs/arcus/qi-home/ad-hoc/": "Ad-Hoc" + "/docs/test-management/qi-home/ad-hoc/": "Ad-Hoc" }, "sprints": { - "/docs/arcus/qi-home/sprints/": "Sprints" + "/docs/test-management/qi-home/sprints/": "Sprints" }, "automation": { - "/docs/arcus/qi-home/automation/": "Automation" + "/docs/test-management/qi-home/automation/": "Automation" }, "agentic-learning": { - "/docs/arcus/qi-home/automation/agentic-learning/": "Agentic Learning" + "/docs/test-management/qi-home/automation/agentic-learning/": "Agentic Learning" }, "copilot": { - "/docs/arcus/qi-home/automation/copilot/": "Copilot" + "/docs/test-management/qi-home/automation/copilot/": "Copilot" }, "dev-session-mapping": { - "/docs/arcus/qi-home/dev-session-mapping/": "Dev Session Mapping" + "/docs/test-management/qi-home/dev-session-mapping/": "Dev Session Mapping" } } \ No newline at end of file diff --git a/src/pages/docs/arcus/introduction/getting-started.md b/src/pages/docs/arcus/introduction/getting-started.md deleted file mode 100644 index 20a1bfc..0000000 --- a/src/pages/docs/arcus/introduction/getting-started.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: 'Getting Started: Arcus by Testsigma' -page_title: 'Getting Started with Arcus by Testsigma' -metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' -noindex: false -order: 1.2 -page_id: 'getting-started-testsigma-test-management' -warning: false -contextual_links: - - type: section - name: 'Contents' - - type: link - name: 'Steps to Access Arcus by Testsigma' - url: '#steps-to-access-testsigma-test-management' ---- - ---- - -Get started with our platform and streamline how you manage and analyze test cases, plans, and runs. This article discusses steps to set up your Test Management with Testsigma. - -[[info | **NOTE**:]] -| If you're an existing Testsigma user, contact **support@testsigma.com** to connect your account with the Arcus by Testsigma tool. - ---- - -> ## **Prerequisites** -> -> Before you begin, ensure you have an active Testsigma account. If you don’t have one, go to the Testsigma signup page to create an account. - ---- - -## **Steps to Access Arcus by Testsigma** - -1. Navigate to Arcus by Testsigma Login Page. - -2. Sign in with your credentials. If you don't have an account, sign up. - -3. In your **User Profile Settings**, select **Arcus**. - -4. You'll be redirected to **Arcus by Testsigma** application. - -5. On the **Dashboard**, click the **Candy Box** icon and select **+ New Project** to get started. - -[[info | **NOTE**:]] -| When you log in for the first time, you're automatically redirected to the project creation page. For more information, see **Projects**. - ---- diff --git a/src/pages/docs/arcus/introduction/overview.md b/src/pages/docs/arcus/introduction/overview.md deleted file mode 100644 index 5571fd6..0000000 --- a/src/pages/docs/arcus/introduction/overview.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -title: "Overview: Arcus by Testsigma" -page_title: "Overview of Arcus by Testsigma" -metadesc: 'Arcus by Testsigma is a quality intelligence test management platform. Keep test cases, plans, and runs in one place, and use AI to generate, automate, and track them.' -noindex: false -order: 1.1 -page_id: 'overview-arcus-by-testsigma' -warning: false -contextual_links: - - type: section - name: 'Contents' - - type: link - name: 'How Arcus Is Organized' - url: '#how-arcus-is-organized' - - type: link - name: 'Core Test Management' - url: '#core-test-management' - - type: link - name: 'QI Home' - url: '#qi-home' - - type: link - name: 'Integrations' - url: '#integrations' - - type: link - name: 'Administration' - url: '#administration' - - type: link - name: 'Get Started' - url: '#get-started' - - type: link - name: 'Getting Help' - url: '#getting-help' ---- - -
- -**Arcus keeps your test cases, test plans, and test runs in one place, and uses AI to generate, automate, and track them for you.** - ---- - -Arcus by Testsigma is a quality intelligence test management platform for QA teams. It gives you a structured home for test cases, test plans, test runs, and reports, so your team is not maintaining spreadsheets or switching between disconnected tools. - -AI works on top of that foundation. In QI Home, Arcus generates test cases from your requirements, tracks coverage against your modules, builds test plans, automates execution, and captures developer activity from GitHub and CLI coding tools so your coverage stays current with what your team is building. - -You can use Arcus fully manually, fully through AI, or anywhere in between. Everything the AI generates lands in the same library your team manages by hand. - ---- - -## **How Arcus Is Organized** - -Arcus has two layers. - -**Core test management** is where you create and organize projects, test cases, test plans, and test runs, and where results and reports live. This layer works the same whether test cases are written manually or generated by AI. - -**QI Home** is the AI workspace. You provide context, such as user stories, PRDs, designs, documents, or developer activity, and Arcus generates test cases mapped to your modules. You review and accept the cases, and coverage, test plans, and Quality Intelligence Metrics update as you go. - ---- - -## **QI Home** - -[QI Home](https://testsigma.com/docs/arcus/qi-home/overview/) is where Arcus generates test cases, tracks coverage, and automates execution using AI. - -There are two ways to start test generation. In **Ad-Hoc**, you attach context sources yourself, such as Jira, Azure DevOps, Linear, or ClickUp stories, Confluence pages, Figma designs, files, or video recordings, and trigger generation on demand. In **Sprints**, Arcus detects a sprint start in your connected project management tool and begins generation from the linked stories automatically. - -After generation, you review and accept test cases, and QI Home tracks the results. Coverage and Gaps shows how much of each module is covered. Test plans are generated automatically in four types: Smoke, Feature, Regression, and Deep Regression. Five Quality Intelligence Metrics in the session header, Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate, tell you how confident you can be in the current build. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for how each metric is calculated. - -**Automation** turns accepted test cases into automated ones without scripts. Agentic Learning walks through a test case on your live application, in the cloud or on your local device, and generates automated steps. Copilot executes those steps in a browser with live controls to pause, edit, and save as it runs. - -**Developer Context Mapping** connects the tools your developers already use to test generation. When developers work in Claude Code, Cursor, GitHub Copilot, or Codex, or open pull requests in GitHub, Arcus captures that context and surfaces it in the **Unmapped Context** view. You review the AI-generated suggestion for where each entry belongs and map it, and Arcus generates or updates test cases from the captured changes. See [Overview: Developer Context Mapping](https://testsigma.com/docs/arcus/qi-home/context-mapping/overview/) for how the mapping model works. - ---- - -## **Core Test Management** - -- [Projects](https://testsigma.com/docs/arcus/projects/manage-projects/) organize your testing work; each project holds its own test cases, plans, runs, and settings. - -- [Test Cases](https://testsigma.com/docs/arcus/test-cases/manage-test-cases/) are the building blocks of your library, with steps, expected results, custom fields, and version history. - -- [Step Groups](https://testsigma.com/docs/arcus/step-groups/create-step-groups/) let you reuse a common sequence of steps across multiple test cases. - -- [Data Sets](https://testsigma.com/docs/arcus/data-sets/manage-data-sets/) hold the input values your test cases run against. - -- [Test Plans](https://testsigma.com/docs/arcus/test-plans/manage-test-plans/) group test cases into a scope you intend to run, such as a release or a regression cycle. - -- [Test Runs](https://testsigma.com/docs/arcus/test-runs/create-test-runs/) record execution: who ran what, the result of each case, and any defects logged. - -- [Test Capture](https://testsigma.com/docs/arcus/test-capture/overview/) is a browser extension that records your actions, logs, and screenshots while you test, and turns them into test cases or bug reports. - -- [Reports](https://testsigma.com/docs/arcus/reports/view-reports/) show execution results, requirement traceability, and dashboards across your project. - - ---- - -## **Integrations** - -- [Integrations](https://testsigma.com/docs/arcus/integrations/jira/) connect Arcus to Jira, Azure DevOps, Linear, ClickUp, Confluence, and Figma for requirements, defect tracking, and context sources. Jira and Azure DevOps also support two-way sync, so test cases and runs can be managed from either side. - -- [Imports and Exports](https://testsigma.com/docs/arcus/imports-and-exports/csv-file/) bring your existing test cases in from TestRail, Zephyr, BrowserStack, or CSV files, and export your library out. - -- [CI/CD Integrations](https://testsigma.com/docs/arcus/ci-cd-integrations/jenkins/) connect Arcus to Jenkins, GitHub Actions, GitLab, Azure DevOps, CircleCI, and Travis CI. - -- [API Reference](https://testsigma.com/docs/arcus/api-reference/overview/) lets you read and manage Arcus data programmatically. - - ---- - -## **Get Started** - -New to Arcus? Start with [Getting Started](https://testsigma.com/docs/arcus/introduction/getting-started/) to set up your account and first project. If you want AI to generate your first test cases, go straight to [Overview: QI Home](https://testsigma.com/docs/arcus/qi-home/overview/). - ---- - -## **Getting Help** - -For questions or support, reach out to the Testsigma team at **support@testsigma.com**. - ---- diff --git a/src/pages/docs/arcus/qi-home/overview.md b/src/pages/docs/arcus/qi-home/overview.md deleted file mode 100644 index 90142ed..0000000 --- a/src/pages/docs/arcus/qi-home/overview.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -title: "Overview: QI Home" -page_title: "Overview of QI Home" -metadesc: 'QI Home is where the Generator Agent creates test cases from your requirements, the Coverage Agent tracks gaps, and the Runner Agent builds test plans and automates test execution in Arcus by Testsigma.' -description: 'An overview of QI Home, where the Generator Agent creates test cases, the Coverage Agent tracks coverage, and the Runner Agent builds test plans and automates test execution.' -noindex: false -order: 13.20 -page_id: 'qi-home-overview' -warning: false -contextual_links: - - type: section - name: 'Contents' - - type: link - name: 'Two Ways to Start Test Generation' - url: '#two-ways-to-start-test-generation' - - type: link - name: 'After Test Cases Are Generated' - url: '#after-test-cases-are-generated' - - type: link - name: 'Automation' - url: '#automation' - - type: link - name: 'Developer Context Mapping' - url: '#developer-context-mapping' - - type: link - name: 'Overview: Developer Context Mapping' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/overview/' - - type: link - name: 'Connect GitHub' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/' - - type: link - name: 'Connect Claude Code' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/' - - type: link - name: 'Connect Cursor' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/' - - type: link - name: 'Connect GitHub Copilot' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/' - - type: link - name: 'Connect Codex' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/' - - type: link - name: 'Map GitHub Context' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/map-github/' - - type: link - name: 'Map Developer Context' - url: 'https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/' - - type: link - name: "What's in This Section" - url: '#whats-in-this-section' - - type: link - name: 'Getting Help' - url: '#getting-help' ---- - -
- -**QI Home is where you generate test cases, track coverage, and automate with AI.** - ---- - -QI Home is where Arcus's AI agents keep your test suite in sync with what your team builds. The **Generator Agent** creates test cases from your requirements, the **Coverage Agent** tracks coverage against your modules and flags what's changed but untested, including developer activity from connected Claude Code, Cursor, GitHub Copilot, and Codex context and GitHub pull requests, and the **Runner Agent** builds test plans and automates test execution. - -You do not write test cases from scratch. You give the Generator Agent the context it needs, and it generates test cases for you. You review what was generated, accept the cases that are accurate, and save them to your library. Coverage, test plans, and quality metrics update as you go. - -There are two ways to start: Ad-Hoc, where you attach context manually and trigger generation yourself, and Sprints, where the Generator Agent detects a sprint start and begins generation automatically. Everything after generation works the same for both. - ---- - -## **Two Ways to Start Test Generation** - -QI Home gives you two starting points depending on how your team works. The generation trigger is different for each, but the rest of the workflow is identical. - -### **Ad-Hoc** - -Ad-Hoc lets you generate test cases on demand by attaching your own context sources, without tying them to a sprint. You open a new session, attach context sources, write a prompt, and click Generate. The Generator Agent reads what you have provided and generates test cases mapped to your features. - -Context sources you can attach include: - -- **Jira, Azure DevOps, Linear, or ClickUp** for user stories and requirements (requires the respective integration to be connected) -- **Confluence** for PRDs and specification documents (requires Confluence integration) -- **Figma** for UI designs and flows (requires Figma integration) -- **Files and Documents** such as PDFs, Word docs, or text files -- **Video Recording** for walkthroughs or recorded user flows - -Use Ad-Hoc when: - -- You are generating test cases outside a sprint cycle -- You want to control exactly what context the Generator Agent uses -- You are exploring coverage for a new feature, release, or exploratory session - -### **Sprints** - -Sprints mode generates test coverage automatically at the start of each sprint, pulling context straight from your linked stories. When a sprint starts in your connected project management tool, the Generator Agent detects it and shows a notification. You confirm generation, and it pulls in the context linked to the sprint stories, including Figma designs, Confluence pages, PRDs, and relevant pull requests, and begins generating test cases. - -Use Sprints when: - -- Your team works in agile sprints -- You want test coverage to start as soon as a sprint kicks off, without manually attaching anything -- You want the Generator Agent to use your Jira, Linear, ClickUp, or Azure DevOps stories as the primary source of truth - ---- - -## **After Test Cases Are Generated** - -Whether you use **Ad-Hoc** or **Sprints**, the next steps are the same. You review the test cases the Generator Agent produced, accept the ones that are accurate, and save them to your library. Coverage, test plans, and quality metrics update as you go. - -[**Review and Accept Test Cases**](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/) allows you to browse the generated test cases grouped by scenario, view step-by-step details for each case, and accept or reject them individually or in bulk. Test cases you save go into your library. Test cases you do not accept are tracked as gaps. - -[**Coverage and Gaps**](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/) shows you the coverage percentage per module, tracked by the Coverage Agent. Coverage is calculated as accepted test cases divided by accepted plus pending test cases, and rejected cases are excluded. Gaps are pending test cases that have not been accepted yet. They are your signal that certain areas of the application are not yet covered. - -[**Test Plans**](https://testsigma.com/docs/arcus/qi-home/test-plans/) are generated automatically by the Runner Agent in four types: Smoke, Feature, Regression, and Deep Regression. Each type is a superset of the previous one. Smoke is always included in Feature, Feature in Regression, and Regression in Deep Regression. Plans are ready to run as soon as you have accepted test cases. - -[**Quality Intelligence Metrics**](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) are five metrics shown in the session header that together tell you how confident you can be in the current build. The metrics are Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate. They update as test cases are accepted and test runs are executed. - ---- - -## **Automation** - -Once a test case exists in your library, the Runner Agent can automate it without you writing any code or scripts. - -**Agentic Learning** opens a browser, either on Testsigma Lab in the cloud or on your local device, and walks through the test case steps on your live application. The Runner Agent observes how the application behaves at each step, learns the element interactions, and generates automated steps. You review the output and save it to your library. The test case moves from manual to automated in a few minutes. - -**Copilot** takes those automated steps and executes them in a browser with a live panel showing each step as it runs. You can pause the execution, add new steps mid-run, switch between manual and automated steps, and save the results when done. Copilot also works without Agentic Learning for running any test case interactively, which is useful for quick sanity checks or exploratory runs. - ---- - -## **Developer Context Mapping** - -Developer Context Mapping keeps your test coverage aligned with what your team is actually building. - -When your developers work in Claude Code, Cursor, GitHub Copilot, or Codex, or open pull requests in GitHub, the Coverage Agent detects that context and surfaces it in the **Unmapped Context** view in QI Home. Each context entry includes an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks. Once mapped, the Generator Agent creates new test cases or updates existing ones based on the code changes or development activity captured. - -See [Overview: Developer Context Mapping](https://testsigma.com/docs/arcus/qi-home/plugins/overview/) for how the Unmapped Context model works, when to use GitHub versus a CLI tool, and what happens when a developer raises a PR for work already captured as CLI context. - ---- - -## **What's in This Section** - -**Ad-Hoc** - -- [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/) -- [Write Effective Prompts](https://testsigma.com/docs/arcus/qi-home/ad-hoc/write-effective-prompts/) -- [Generate Test Cases](https://testsigma.com/docs/arcus/qi-home/ad-hoc/generate-test-cases/) - -**Sprints** - -- [Generate Test Cases](https://testsigma.com/docs/arcus/qi-home/sprints/generate-test-cases/) - -**Shared Workflows** - -- [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/) -- [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/) -- [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/) -- [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) -- [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) - -**Automation** - -- [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) -- [Learn Test Case Live (Local)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local/) -- [Live Learning Controls](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls/) -- [Run Automated Test Case with Copilot](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot/) -- [Execute Test Case in Cloud](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud/) -- [Execute Test Case in Local](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-local/) -- [Execution Controls in Copilot](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot/) - -**Developer Context Mapping** - -- [Overview](https://testsigma.com/docs/arcus/qi-home/plugins/overview/) -- [Connect GitHub](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/) -- [Connect Claude Code](https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/) -- [Connect Cursor](https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/) -- [Connect GitHub Copilot](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/) -- [Connect Codex](https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/) -- [Map GitHub Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-github/) -- [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/) - -**Others** - -- Best Practices -- [FAQs](https://testsigma.com/docs/arcus/qi-home/faqs/) - -[[info | **NOTE**:]] -| QI Home requires an active project in Arcus by Testsigma. To attach context from Jira, Azure DevOps, Linear, ClickUp, Confluence, or Figma in Ad-Hoc, you need the respective integration connected to your project. Files, documents, and video recordings can be attached without any external integration. For Sprints, connect your project to a supported project management tool. For Developer Context Mapping, connect your Claude or GitHub account. - ---- - -## **Getting Help** - -For questions or support, reach out to the Testsigma team at **support@testsigma.com**. - ---- diff --git a/src/pages/docs/arcus/qi-home/plugins/connect-codex.md b/src/pages/docs/arcus/qi-home/plugins/connect-codex.md deleted file mode 100644 index ebba35d..0000000 --- a/src/pages/docs/arcus/qi-home/plugins/connect-codex.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -title: 'Connect Codex' -page_title: 'Connect Codex' -metadesc: 'How to install and connect the Arcus plugin for Codex so your coding context is captured and sent to QI Home for test generation.' -description: 'How to install and connect the Arcus plugin for Codex so your coding context is captured and sent to QI Home for test generation.' -noindex: false -order: 13.45 -page_id: 'qi-home-connect-codex' -warning: false -contextual_links: - - type: section - name: 'Contents' - - type: link - name: 'Overview' - url: '#overview' - - type: link - name: 'Why Arcus' - url: '#why-arcus' - - type: link - name: 'Prerequisites' - url: '#prerequisites' - - type: link - name: 'Install the Plugin' - url: '#install-the-plugin' - - type: link - name: 'Log In and Connect Your Project' - url: '#log-in-and-connect-your-project' - - type: link - name: 'How the Quality Intelligence Loop Works' - url: '#how-the-quality-intelligence-loop-works' - - type: link - name: 'Map Your Context to a Sprint' - url: '#map-your-context-to-a-sprint' - - type: link - name: 'Push Your Context' - url: '#push-your-context' - - type: link - name: "Who It's For" - url: '#who-its-for' - - type: link - name: 'Commands Reference' - url: '#commands-reference' - - type: link - name: 'If You Also Use GitHub' - url: '#if-you-also-use-github' ---- - -**Install the Arcus plugin for Codex so that your coding context is captured and sent to QI Home for test generation.** - -When the plugin is installed and connected to a project, it captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and the Generator Agent creates test cases from your development activity. - ---- - -## **Overview** - -At a glance, Arcus: - -* **Generates test cases from what you actually built**, with no manual authoring. -* **Finds the gaps** between what changed and what's tested, with a reason for each. -* **Plans and runs** those tests across Smoke, Feature, Regression, and Deep Regression suites. -* **Decides with a single Release Readiness score** and a GO / CONDITIONAL GO / NO-GO verdict. - ---- - -## **Why Arcus** - -AI coding agents have made it trivial to ship large changes fast. The bottleneck has moved: it's no longer writing the code, it's trusting it. Teams using Codex routinely merge features, refactors, and fixes faster than their QA process can keep up, and the gap between "the code is written" and "we know it works" keeps widening. - -The traditional answer, writing tests by hand after the fact, is slow, always behind, and never tells you with confidence how much of what you just built is actually covered. - -Arcus closes that gap by treating your Codex session as the source of truth for what changed. It captures the session automatically, turns it into tests you review rather than write, keeps a live map of what's covered, and rolls everything up into an evidence-backed release signal. - ---- - -> ## **Prerequisites** -> -> Before you begin, ensure that: -> * Codex is installed. -> * You have an active project in Arcus by Testsigma. - ---- - -## **Install the Plugin** - -[[info | **NOTE**:]] -| The install command for the Codex Arcus plugin is pending confirmation from the dev team. This step will be updated before publication. - ---- - -## **Log In and Connect Your Project** - -1. In Codex, run **/arcus:login**. - -2. Complete the login flow in the browser. Return to Codex when prompted. - -3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**. To see your available projects, run **/arcus:project** without an argument. - -4. Start coding. The plugin begins capturing your context in the background. - -[[info | **NOTE**:]] -| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload. - ---- - -## **How the Quality Intelligence Loop Works** - -Once you push a session, Arcus runs that context through the Quality Intelligence loop: a continuous cycle that keeps your tests and your release signal in sync with the code. - -**1. Generate** - -The **Generator Agent** reads the captured session, code changes, the prompts you gave Codex, the tools it ran, and drafts test cases for the behavior you actually built. You review each one and accept, edit, or reject it; accepted cases join your test suite. Nothing is auto-merged behind your back. - -**2. Find gaps** - -The **Coverage Agent** answers the question manual QA can never keep up with: what did we change that we haven't tested yet? It re-runs whenever context changes, a new Codex session or a pull request, or whenever you accept a case, and surfaces untested areas with a reason for each gap. - -**3. Plan and execute** - -Accepted cases roll up into auto-generated test plans, nested by scope: - -| Plan | Scope | -|------|-------| -| Smoke | Critical-path sanity checks, fast feedback | -| Feature | Cases tied to the current feature or session | -| Regression | Existing behavior that shouldn't have broken | -| Deep Regression | Broad, exhaustive run across the product | - -The **Runner Agent** executes these plans, automated runs against your configured machines and environments, or manual runs for cases that still need a human. See [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) for how the nested plan hierarchy works. - -**4. Measure and decide** - -Execution results feed the Quality Intelligence metrics, which build on each other up to a single verdict: - -| Metric | Question It Answers | -|--------|----------------------| -| Coverage | Of what should be tested, how much is approved and tested? | -| Pass Rate | Of the tests that ran, how many passed? | -| Confidence | How trustworthy are the results? | -| Release Readiness | On a 0 to 100 scale, how shippable is this sprint? | -| Release Gate | The verdict: GO / CONDITIONAL GO / NO-GO | - -See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for the full formulas and thresholds behind each metric. - ---- - -## **Map Your Context to a Sprint** - -Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. Replace **<ticket-key>** with the Jira ticket ID for the work you are doing. - -``` -/arcus:map PROJ-123 -``` - -Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint, and the test cases generated from it trace back to that ticket. QA does not need to route it manually from Unmapped Context. - -[[info | **NOTE**:]] -| You can push without mapping. The context lands in Unmapped Context and waits there with its generated tests until you resolve it, either to a sprint or to an Ad-Hoc session. See [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/). - ---- - -## **Push Your Context** - -1. When you are done, run **/arcus:push** to upload the captured context to QI Home. - -The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did). - ---- - -## **Who It's For** - -* **Developers** shipping with Codex who want their changes tested without breaking flow to write tests by hand. -* **QA and test engineers** who want generated cases to review and refine, plus a coverage map that updates itself instead of a stale spreadsheet. -* **Engineering leads and release managers** who need an objective, evidence-backed answer to "is this sprint safe to ship?" rather than a status-meeting guess. - ---- - -## **Commands Reference** - -| Command | What it does | -|---------|-------------| -| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it | -| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation | -| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine | -| /arcus:project | Shows your Arcus projects and sets one as the active project | -| /arcus:map | Links a ticket key to the current context so it routes to the right sprint | -| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them | -| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them | -| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped | - ---- - -## **If You Also Use GitHub** - -If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Arcus connects the two automatically: - -* **Context still unmapped**: Arcus converts it into a GitHub context. The Codex context and the pull request are unified as a single entry in Unmapped Context. -* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. - ---- diff --git a/src/pages/docs/arcus/qi-home/plugins/connect-cursor.md b/src/pages/docs/arcus/qi-home/plugins/connect-cursor.md deleted file mode 100644 index 7cb245b..0000000 --- a/src/pages/docs/arcus/qi-home/plugins/connect-cursor.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -title: 'Connect Cursor' -page_title: 'Connect Cursor' -metadesc: 'How to install and connect the Arcus plugin for Cursor so your coding context is captured and sent to QI Home for test generation.' -description: 'How to install and connect the Arcus plugin for Cursor so your coding context is captured and sent to QI Home for test generation.' -noindex: false -order: 13.43 -page_id: 'qi-home-connect-cursor' -warning: false -contextual_links: - - type: section - name: 'Contents' - - type: link - name: 'Overview' - url: '#overview' - - type: link - name: 'Why Arcus' - url: '#why-arcus' - - type: link - name: 'Prerequisites' - url: '#prerequisites' - - type: link - name: 'Install the Plugin' - url: '#install-the-plugin' - - type: link - name: 'Log In and Connect Your Project' - url: '#log-in-and-connect-your-project' - - type: link - name: 'How the Quality Intelligence Loop Works' - url: '#how-the-quality-intelligence-loop-works' - - type: link - name: 'Map Your Context to a Sprint' - url: '#map-your-context-to-a-sprint' - - type: link - name: 'Push Your Context' - url: '#push-your-context' - - type: link - name: "Who It's For" - url: '#who-its-for' - - type: link - name: 'Commands Reference' - url: '#commands-reference' - - type: link - name: 'If You Also Use GitHub' - url: '#if-you-also-use-github' ---- - -**Install the Arcus plugin for Cursor so that your coding context is captured and sent to QI Home for test generation.** - -When the plugin is installed and connected to a project, it captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and the Generator Agent creates test cases from your development activity. - ---- - -## **Overview** - -At a glance, Arcus: - -* **Generates test cases from what you actually built**, with no manual authoring. -* **Finds the gaps** between what changed and what's tested, with a reason for each. -* **Plans and runs** those tests across Smoke, Feature, Regression, and Deep Regression suites. -* **Decides with a single Release Readiness score** and a GO / CONDITIONAL GO / NO-GO verdict. - ---- - -## **Why Arcus** - -AI coding agents have made it trivial to ship large changes fast. The bottleneck has moved: it's no longer writing the code, it's trusting it. Teams using Cursor routinely merge features, refactors, and fixes faster than their QA process can keep up, and the gap between "the code is written" and "we know it works" keeps widening. - -The traditional answer, writing tests by hand after the fact, is slow, always behind, and never tells you with confidence how much of what you just built is actually covered. - -Arcus closes that gap by treating your Cursor session as the source of truth for what changed. It captures the session automatically, turns it into tests you review rather than write, keeps a live map of what's covered, and rolls everything up into an evidence-backed release signal. - ---- - -> ## **Prerequisites** -> -> Before you begin, ensure that: -> * Cursor is installed. -> * You have an active project in Arcus by Testsigma. - ---- - -## **Install the Plugin** - -Install the Arcus plugin from the Cursor marketplace. - ---- - -## **Log In and Connect Your Project** - -1. In Cursor, run **/arcus:login**. - -2. Complete the login flow in the browser. Return to Cursor when prompted. - -3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**. To see your available projects, run **/arcus:project** without an argument. - -4. Start coding. The plugin begins capturing your context in the background. - -[[info | **NOTE**:]] -| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload. - ---- - -## **How the Quality Intelligence Loop Works** - -Once you push a session, Arcus runs that context through the Quality Intelligence loop: a continuous cycle that keeps your tests and your release signal in sync with the code. - -**1. Generate** - -The **Generator Agent** reads the captured session, code changes, the prompts you gave Cursor, the tools it ran, and drafts test cases for the behavior you actually built. You review each one and accept, edit, or reject it; accepted cases join your test suite. Nothing is auto-merged behind your back. - -**2. Find gaps** - -The **Coverage Agent** answers the question manual QA can never keep up with: what did we change that we haven't tested yet? It re-runs whenever context changes, a new Cursor session or a pull request, or whenever you accept a case, and surfaces untested areas with a reason for each gap. - -**3. Plan and execute** - -Accepted cases roll up into auto-generated test plans, nested by scope: - -| Plan | Scope | -|------|-------| -| Smoke | Critical-path sanity checks, fast feedback | -| Feature | Cases tied to the current feature or session | -| Regression | Existing behavior that shouldn't have broken | -| Deep Regression | Broad, exhaustive run across the product | - -The **Runner Agent** executes these plans, automated runs against your configured machines and environments, or manual runs for cases that still need a human. See [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) for how the nested plan hierarchy works. - -**4. Measure and decide** - -Execution results feed the Quality Intelligence metrics, which build on each other up to a single verdict: - -| Metric | Question It Answers | -|--------|----------------------| -| Coverage | Of what should be tested, how much is approved and tested? | -| Pass Rate | Of the tests that ran, how many passed? | -| Confidence | How trustworthy are the results? | -| Release Readiness | On a 0 to 100 scale, how shippable is this sprint? | -| Release Gate | The verdict: GO / CONDITIONAL GO / NO-GO | - -See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for the full formulas and thresholds behind each metric. - ---- - -## **Map Your Context to a Sprint** - -Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. Replace **<ticket-key>** with the Jira ticket ID for the work you are doing. - -``` -/arcus:map PROJ-123 -``` - -Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint, and the test cases generated from it trace back to that ticket. QA does not need to route it manually from Unmapped Context. - -[[info | **NOTE**:]] -| You can push without mapping. The context lands in Unmapped Context and waits there with its generated tests until you resolve it, either to a sprint or to an Ad-Hoc session. See [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/). - ---- - -## **Push Your Context** - -1. When you are done, run **/arcus:push** to upload the captured context to QI Home. - -The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did). - ---- - -## **Who It's For** - -* **Developers** shipping with Cursor who want their changes tested without breaking flow to write tests by hand. -* **QA and test engineers** who want generated cases to review and refine, plus a coverage map that updates itself instead of a stale spreadsheet. -* **Engineering leads and release managers** who need an objective, evidence-backed answer to "is this sprint safe to ship?" rather than a status-meeting guess. - ---- - -## **Commands Reference** - -| Command | What it does | -|---------|-------------| -| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it | -| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation | -| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine | -| /arcus:project | Shows your Arcus projects and sets one as the active project | -| /arcus:map | Links a ticket key to the current context so it routes to the right sprint | -| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them | -| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them | -| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped | - ---- - -## **If You Also Use GitHub** - -If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Arcus connects the two automatically: - -* **Context still unmapped**: Arcus converts it into a GitHub context. The Cursor context and the pull request are unified as a single entry in Unmapped Context. -* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. - ---- diff --git a/src/pages/docs/arcus/qi-home/plugins/connect-github-copilot.md b/src/pages/docs/arcus/qi-home/plugins/connect-github-copilot.md deleted file mode 100644 index eb278de..0000000 --- a/src/pages/docs/arcus/qi-home/plugins/connect-github-copilot.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -title: 'Connect GitHub Copilot' -page_title: 'Connect GitHub Copilot' -metadesc: 'How to install and connect the Arcus plugin for GitHub Copilot so your coding context is captured and sent to QI Home for test generation.' -description: 'How to install and connect the Arcus plugin for GitHub Copilot so your coding context is captured and sent to QI Home for test generation.' -noindex: false -order: 13.44 -page_id: 'qi-home-connect-github-copilot' -warning: false -contextual_links: - - type: section - name: 'Contents' - - type: link - name: 'Overview' - url: '#overview' - - type: link - name: 'Why Arcus' - url: '#why-arcus' - - type: link - name: 'Prerequisites' - url: '#prerequisites' - - type: link - name: 'Install the Plugin' - url: '#install-the-plugin' - - type: link - name: 'Log In and Connect Your Project' - url: '#log-in-and-connect-your-project' - - type: link - name: 'How the Quality Intelligence Loop Works' - url: '#how-the-quality-intelligence-loop-works' - - type: link - name: 'Map Your Context to a Sprint' - url: '#map-your-context-to-a-sprint' - - type: link - name: 'Push Your Context' - url: '#push-your-context' - - type: link - name: "Who It's For" - url: '#who-its-for' - - type: link - name: 'Commands Reference' - url: '#commands-reference' - - type: link - name: 'If You Also Use GitHub' - url: '#if-you-also-use-github' ---- - -**Install the Arcus plugin for GitHub Copilot so that your coding context is captured and sent to QI Home for test generation.** - -When the plugin is installed and connected to a project, it captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and the Generator Agent creates test cases from your development activity. - -[[info | **NOTE**:]] -| This doc refers to the GitHub Copilot CLI plugin for Arcus, not Testsigma Copilot (the test execution feature). They are separate tools. - ---- - -## **Overview** - -At a glance, Arcus: - -* **Generates test cases from what you actually built**, with no manual authoring. -* **Finds the gaps** between what changed and what's tested, with a reason for each. -* **Plans and runs** those tests across Smoke, Feature, Regression, and Deep Regression suites. -* **Decides with a single Release Readiness score** and a GO / CONDITIONAL GO / NO-GO verdict. - ---- - -## **Why Arcus** - -AI coding agents have made it trivial to ship large changes fast. The bottleneck has moved: it's no longer writing the code, it's trusting it. Teams using GitHub Copilot routinely merge features, refactors, and fixes faster than their QA process can keep up, and the gap between "the code is written" and "we know it works" keeps widening. - -The traditional answer, writing tests by hand after the fact, is slow, always behind, and never tells you with confidence how much of what you just built is actually covered. - -Arcus closes that gap by treating your GitHub Copilot session as the source of truth for what changed. It captures the session automatically, turns it into tests you review rather than write, keeps a live map of what's covered, and rolls everything up into an evidence-backed release signal. - ---- - -> ## **Prerequisites** -> -> Before you begin, ensure that: -> * GitHub Copilot is installed. -> * You have an active project in Arcus by Testsigma. - ---- - -## **Install the Plugin** - -[[info | **NOTE**:]] -| The install command for the GitHub Copilot Arcus plugin is pending confirmation from the dev team. This step will be updated before publication. - ---- - -## **Log In and Connect Your Project** - -1. In GitHub Copilot, run **/arcus:login**. - -2. Complete the login flow in the browser. Return to GitHub Copilot when prompted. - -3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**. To see your available projects, run **/arcus:project** without an argument. - -4. Start coding. The plugin begins capturing your context in the background. - -[[info | **NOTE**:]] -| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload. - ---- - -## **How the Quality Intelligence Loop Works** - -Once you push a session, Arcus runs that context through the Quality Intelligence loop: a continuous cycle that keeps your tests and your release signal in sync with the code. - -**1. Generate** - -The **Generator Agent** reads the captured session, code changes, the prompts you gave Copilot, the tools it ran, and drafts test cases for the behavior you actually built. You review each one and accept, edit, or reject it; accepted cases join your test suite. Nothing is auto-merged behind your back. - -**2. Find gaps** - -The **Coverage Agent** answers the question manual QA can never keep up with: what did we change that we haven't tested yet? It re-runs whenever context changes, a new GitHub Copilot session or a pull request, or whenever you accept a case, and surfaces untested areas with a reason for each gap. - -**3. Plan and execute** - -Accepted cases roll up into auto-generated test plans, nested by scope: - -| Plan | Scope | -|------|-------| -| Smoke | Critical-path sanity checks, fast feedback | -| Feature | Cases tied to the current feature or session | -| Regression | Existing behavior that shouldn't have broken | -| Deep Regression | Broad, exhaustive run across the product | - -The **Runner Agent** executes these plans, automated runs against your configured machines and environments, or manual runs for cases that still need a human. See [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) for how the nested plan hierarchy works. - -**4. Measure and decide** - -Execution results feed the Quality Intelligence metrics, which build on each other up to a single verdict: - -| Metric | Question It Answers | -|--------|----------------------| -| Coverage | Of what should be tested, how much is approved and tested? | -| Pass Rate | Of the tests that ran, how many passed? | -| Confidence | How trustworthy are the results? | -| Release Readiness | On a 0 to 100 scale, how shippable is this sprint? | -| Release Gate | The verdict: GO / CONDITIONAL GO / NO-GO | - -See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for the full formulas and thresholds behind each metric. - ---- - -## **Map Your Context to a Sprint** - -Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. Replace **<ticket-key>** with the Jira ticket ID for the work you are doing. - -``` -/arcus:map PROJ-123 -``` - -Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint, and the test cases generated from it trace back to that ticket. QA does not need to route it manually from Unmapped Context. - -[[info | **NOTE**:]] -| You can push without mapping. The context lands in Unmapped Context and waits there with its generated tests until you resolve it, either to a sprint or to an Ad-Hoc session. See [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/). - ---- - -## **Push Your Context** - -1. When you are done, run **/arcus:push** to upload the captured context to QI Home. - -The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did). - ---- - -## **Who It's For** - -* **Developers** shipping with GitHub Copilot who want their changes tested without breaking flow to write tests by hand. -* **QA and test engineers** who want generated cases to review and refine, plus a coverage map that updates itself instead of a stale spreadsheet. -* **Engineering leads and release managers** who need an objective, evidence-backed answer to "is this sprint safe to ship?" rather than a status-meeting guess. - ---- - -## **Commands Reference** - -| Command | What it does | -|---------|-------------| -| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it | -| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation | -| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine | -| /arcus:project | Shows your Arcus projects and sets one as the active project | -| /arcus:map | Links a ticket key to the current context so it routes to the right sprint | -| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them | -| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them | -| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped | - ---- - -## **If You Also Use GitHub** - -If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Arcus connects the two automatically: - -* **Context still unmapped**: Arcus converts it into a GitHub context. The GitHub Copilot context and the pull request are unified as a single entry in Unmapped Context. -* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. - ---- diff --git a/src/pages/docs/arcus/api-reference/modules.md b/src/pages/docs/test-management/api-reference/modules.md similarity index 93% rename from src/pages/docs/arcus/api-reference/modules.md rename to src/pages/docs/test-management/api-reference/modules.md index 2d46d38..310f1e6 100644 --- a/src/pages/docs/arcus/api-reference/modules.md +++ b/src/pages/docs/test-management/api-reference/modules.md @@ -1,10 +1,10 @@ --- -title: 'API Modules for Arcus by Testsigma' -page_title: 'API Modules for Arcus by Testsigma' -metadesc: 'Use API Reference for Arcus by Testsigma to manage all modules like projects, test cases, test runs, test plans, folders, step groups, & settings' +title: 'API Modules for Test Management by Testsigma' +page_title: 'API Modules for Test Management by Testsigma' +metadesc: 'Use API Reference for Test Management by Testsigma to manage all modules like projects, test cases, test runs, test plans, folders, step groups, & settings' noindex: false order: 16.2 -page_id: 'api-modules-for-arcus-by-testsigma' +page_id: 'api-modules-for-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -23,7 +23,7 @@ contextual_links: --- -You can now use API Reference for Arcus by Testsigma to manage all modules of test management like projects, test cases, test runs, test plans, folders, step groups, and custom fields. These APIs support automation workflows and integration with CI/CD pipelines. +You can now use API Reference for Test Management by Testsigma to manage all modules of test management like projects, test cases, test runs, test plans, folders, step groups, and custom fields. These APIs support automation workflows and integration with CI/CD pipelines. Each module includes a set of RESTful endpoints that support standard CRUD operations, status updates, and data retrieval. Authentication is managed via Bearer tokens, which must be included in each request. @@ -31,7 +31,7 @@ Each module includes a set of RESTful endpoints that support standard CRUD opera > ## **Prerequisites** > -> Before you begin, ensure you have API Token from Arcus by Testsigma. +> Before you begin, ensure you have API Token from Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/api-reference/overview.md b/src/pages/docs/test-management/api-reference/overview.md similarity index 100% rename from src/pages/docs/arcus/api-reference/overview.md rename to src/pages/docs/test-management/api-reference/overview.md diff --git a/src/pages/docs/arcus/ci-cd-integrations/azure-devops.md b/src/pages/docs/test-management/ci-cd-integrations/azure-devops.md similarity index 74% rename from src/pages/docs/arcus/ci-cd-integrations/azure-devops.md rename to src/pages/docs/test-management/ci-cd-integrations/azure-devops.md index 755ea84..b37c840 100644 --- a/src/pages/docs/arcus/ci-cd-integrations/azure-devops.md +++ b/src/pages/docs/test-management/ci-cd-integrations/azure-devops.md @@ -1,10 +1,10 @@ --- -title: 'Azure DevOps Integration with Arcus by Testsigma' -page_title: 'Azure DevOps Integration with Arcus by Testsigma' +title: 'Azure DevOps Integration with Test Management by Testsigma' +page_title: 'Azure DevOps Integration with Test Management by Testsigma' metadesc: 'Integrate Azure DevOps with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | Azure DevOps Integration with TMS by Testsigma' noindex: false order: 17.2 -page_id: 'azure-devOps-integration-with-arcus-by-testsigma' +page_id: 'azure-devOps-integration-with-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -22,19 +22,19 @@ contextual_links:
-**Integrate Azure DevOps with Arcus by Testsigma and automate your test runs and generate test reports.** +**Integrate Azure DevOps with Test Management by Testsigma and automate your test runs and generate test reports.** --- -Integrate Azure DevOps with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Azure DevOps with Arcus by Testsigma. +Integrate Azure DevOps with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Azure DevOps with Test Management by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. -> - You have an API token from Arcus by Testsigma. +> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. +> - You have an API token from Test Management by Testsigma. > - You have an **Azure DevOps** account. --- @@ -85,7 +85,7 @@ Integrate Azure DevOps with Arcus by Testsigma to automate test executions and g [[info | **NOTE**:]] | Before triggering this build, make the following updates: -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Replace `` with the actual path to your JUnit XML report file. You can find this in your surefire-reports directory. @@ -95,6 +95,6 @@ Integrate Azure DevOps with Arcus by Testsigma to automate test executions and g 1. In your **Azure DevOps** pipeline, click **Run pipeline**. -2. After the build completes, the test run in Arcus by Testsigma is automatically updated with the test execution results. +2. After the build completes, the test run in Test Management by Testsigma is automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/arcus/ci-cd-integrations/circleci.md b/src/pages/docs/test-management/ci-cd-integrations/circleci.md similarity index 77% rename from src/pages/docs/arcus/ci-cd-integrations/circleci.md rename to src/pages/docs/test-management/ci-cd-integrations/circleci.md index d0cbd53..b3b4f0c 100644 --- a/src/pages/docs/arcus/ci-cd-integrations/circleci.md +++ b/src/pages/docs/test-management/ci-cd-integrations/circleci.md @@ -1,10 +1,10 @@ --- -title: 'CircleCI Integration with Arcus by Testsigma' -page_title: 'CircleCI Integration with Arcus by Testsigma' +title: 'CircleCI Integration with Test Management by Testsigma' +page_title: 'CircleCI Integration with Test Management by Testsigma' metadesc: 'Integrate CircleCI with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | CircleCI Integration with TMS by Testsigma' noindex: false order: 17.5 -page_id: 'circle-ci-integration-with-arcus-by-testsigma' +page_id: 'circle-ci-integration-with-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -25,19 +25,19 @@ contextual_links:
-**Integrate CircleCI with Arcus by Testsigma and automate your test runs and generate test reports.** +**Integrate CircleCI with Test Management by Testsigma and automate your test runs and generate test reports.** --- -Integrate CircleCI with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating CircleCI with Arcus by Testsigma. +Integrate CircleCI with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating CircleCI with Test Management by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. -> - You have an API token from Arcus by Testsigma. +> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. +> - You have an API token from Test Management by Testsigma. > - You have a **CircleCI** account. @@ -107,7 +107,7 @@ Integrate CircleCI with Arcus by Testsigma to automate test executions and gener [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Ensure the path to the JUnit report points to the actual XML file generated by Maven. @@ -122,7 +122,7 @@ Integrate CircleCI with Arcus by Testsigma to automate test executions and gener 2. **CircleCI** will run the workflow. -3. After completion, the corresponding test run in Arcus by Testsigma will be automatically updated with the test execution results. +3. After completion, the corresponding test run in Test Management by Testsigma will be automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/arcus/ci-cd-integrations/github.md b/src/pages/docs/test-management/ci-cd-integrations/github.md similarity index 77% rename from src/pages/docs/arcus/ci-cd-integrations/github.md rename to src/pages/docs/test-management/ci-cd-integrations/github.md index b3ff59a..e6ea28f 100644 --- a/src/pages/docs/arcus/ci-cd-integrations/github.md +++ b/src/pages/docs/test-management/ci-cd-integrations/github.md @@ -1,10 +1,10 @@ --- -title: 'GitHub Integration with Arcus by Testsigma' -page_title: 'GitHub Integration with Arcus by Testsigma' +title: 'GitHub Integration with Test Management by Testsigma' +page_title: 'GitHub Integration with Test Management by Testsigma' metadesc: 'Integrate GitHub with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | GitHub Integration with TMS by Testsigma' noindex: false order: 17.3 -page_id: 'github-integration-with-arcus-by-testsigma' +page_id: 'github-integration-with-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -22,19 +22,19 @@ contextual_links:
-**Integrate GitHub with Arcus by Testsigma and automate your test runs and generate test reports.** +**Integrate GitHub with Test Management by Testsigma and automate your test runs and generate test reports.** --- -Integrate GitHub with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitHub with Arcus by Testsigma. +Integrate GitHub with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitHub with Test Management by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. -> - You have an API token from Arcus by Testsigma. +> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. +> - You have an API token from Test Management by Testsigma. > - You have a **GitHub** account. @@ -84,7 +84,7 @@ Integrate GitHub with Arcus by Testsigma to automate test executions and generat ``` [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Ensure the path to the JUnit report points to the actual XML file generated by Maven. diff --git a/src/pages/docs/arcus/ci-cd-integrations/gitlab.md b/src/pages/docs/test-management/ci-cd-integrations/gitlab.md similarity index 74% rename from src/pages/docs/arcus/ci-cd-integrations/gitlab.md rename to src/pages/docs/test-management/ci-cd-integrations/gitlab.md index c9ba6f4..8693fc2 100644 --- a/src/pages/docs/arcus/ci-cd-integrations/gitlab.md +++ b/src/pages/docs/test-management/ci-cd-integrations/gitlab.md @@ -1,10 +1,10 @@ --- -title: 'GitLab Integration with Arcus by Testsigma' -page_title: 'GitLab Integration with Arcus by Testsigma' -metadesc: 'Integrate GitLab with Arcus by Testsigma to automate test executions & generate test reports through CI/CD pipelines | GitLab Integration with TMS by Testsigma' +title: 'GitLab Integration with Test Management by Testsigma' +page_title: 'GitLab Integration with Test Management by Testsigma' +metadesc: 'Integrate GitLab with Test Management by Testsigma to automate test executions & generate test reports through CI/CD pipelines | GitLab Integration with TMS by Testsigma' noindex: false order: 17.6 -page_id: 'Gitlab-ci-integration-with-arcus-by-testsigma' +page_id: 'Gitlab-ci-integration-with-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -25,19 +25,19 @@ contextual_links:
-**Integrate GitLab with Arcus by Testsigma and automate your test runs and generate test reports.** +**Integrate GitLab with Test Management by Testsigma and automate your test runs and generate test reports.** --- -Integrate GitLab with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitLab with Arcus by Testsigma. +Integrate GitLab with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitLab with Test Management by Testsigma. --- > ## **Prerequisites** > Before you begin, ensure the following: > - You have a **GitLab** account and a connected project repository. -> - A project and at least one test run exist in Arcus by Testsigma. -> - You have an API token from Arcus by Testsigma. +> - A project and at least one test run exist in Test Management by Testsigma. +> - You have an API token from Test Management by Testsigma. > - Your test results are generated in JUnit XML format (for example, reports/junit.xml) --- @@ -103,6 +103,6 @@ This configuration performs the following actions: 2. GitLab will run the workflow. -3. After completion, the corresponding test run in Arcus by Testsigma will be automatically updated with the test execution results. +3. After completion, the corresponding test run in Test Management by Testsigma will be automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/arcus/ci-cd-integrations/jenkins.md b/src/pages/docs/test-management/ci-cd-integrations/jenkins.md similarity index 76% rename from src/pages/docs/arcus/ci-cd-integrations/jenkins.md rename to src/pages/docs/test-management/ci-cd-integrations/jenkins.md index 9b5f980..1fac8a5 100644 --- a/src/pages/docs/arcus/ci-cd-integrations/jenkins.md +++ b/src/pages/docs/test-management/ci-cd-integrations/jenkins.md @@ -1,10 +1,10 @@ --- -title: 'Jenkins Integration with Arcus by Testsigma' -page_title: 'Jenkins Integration with Arcus by Testsigma' +title: 'Jenkins Integration with Test Management by Testsigma' +page_title: 'Jenkins Integration with Test Management by Testsigma' metadesc: 'Integrate Jenkins with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | Jenkins Integration with TMS by Testsigma' noindex: false order: 17.1 -page_id: 'jenkins-integration-with-arcus-by-testsigma' +page_id: 'jenkins-integration-with-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -25,19 +25,19 @@ contextual_links:
-**Integrate Jenkins with Arcus by Testsigma and automate your test runs and generate test reports.** +**Integrate Jenkins with Test Management by Testsigma and automate your test runs and generate test reports.** --- -Integrate Jenkins with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Jenkins with Arcus by Testsigma. +Integrate Jenkins with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Jenkins with Test Management by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. -> - You have an API token from Arcus by Testsigma. +> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. +> - You have an API token from Test Management by Testsigma. > - You have a **Jenkins** account. --- @@ -54,7 +54,7 @@ Integrate Jenkins with Arcus by Testsigma to automate test executions and genera 5. In the **Kind** dropdown menu, select **Secret text**. -6. In the **Secret** box, enter your API Token from Arcus by Testsigma. +6. In the **Secret** box, enter your API Token from Test Management by Testsigma. 7. In the **ID** box, enter `TESTSIGMA_API_TOKEN`. @@ -105,7 +105,7 @@ Integrate Jenkins with Arcus by Testsigma to automate test executions and genera [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ 7. Click **Apply**, and then click **Save**. @@ -118,6 +118,6 @@ Integrate Jenkins with Arcus by Testsigma to automate test executions and genera 2. In the left navigation bar, click **Build Now**. -3. Once the build completes successfully, the test case statuses in the associated test run are updated automatically in Arcus by Testsigma. +3. Once the build completes successfully, the test case statuses in the associated test run are updated automatically in Test Management by Testsigma. --- \ No newline at end of file diff --git a/src/pages/docs/arcus/ci-cd-integrations/travis-ci.md b/src/pages/docs/test-management/ci-cd-integrations/travis-ci.md similarity index 73% rename from src/pages/docs/arcus/ci-cd-integrations/travis-ci.md rename to src/pages/docs/test-management/ci-cd-integrations/travis-ci.md index 346499f..43d54b5 100644 --- a/src/pages/docs/arcus/ci-cd-integrations/travis-ci.md +++ b/src/pages/docs/test-management/ci-cd-integrations/travis-ci.md @@ -1,10 +1,10 @@ --- -title: 'Travis CI Integration with Arcus by Testsigma' -page_title: 'Travis CI Integration with Arcus by Testsigma' +title: 'Travis CI Integration with Test Management by Testsigma' +page_title: 'Travis CI Integration with Test Management by Testsigma' metadesc: 'Integrate Travis CI with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | Travis CI Integration with TMS by Testsigma' noindex: false order: 17.4 -page_id: 'travis-integration-with-arcus-by-testsigma' +page_id: 'travis-integration-with-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -25,19 +25,19 @@ contextual_links:
-**Integrate Travis CI with Arcus by Testsigma and automate your test runs and generate test reports.** +**Integrate Travis CI with Test Management by Testsigma and automate your test runs and generate test reports.** --- -Integrate Travis CI with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Travis CI with Arcus by Testsigma. +Integrate Travis CI with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Travis CI with Test Management by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. -> - You have an API token from Arcus by Testsigma. +> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. +> - You have an API token from Test Management by Testsigma. > - You have a **Travis CI** account. @@ -89,7 +89,7 @@ Integrate Travis CI with Arcus by Testsigma to automate test executions and gene ``` [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Ensure the path to the JUnit report points to the actual XML file generated by Maven. @@ -104,7 +104,7 @@ Integrate Travis CI with Arcus by Testsigma to automate test executions and gene 2. **Travis CI** will run the workflow. -3. After completion, the corresponding test run in Arcus by Testsigma will be automatically updated with the test execution results. +3. After completion, the corresponding test run in Test Management by Testsigma will be automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/arcus/data-sets/manage-data-sets.md b/src/pages/docs/test-management/data-sets/manage-data-sets.md similarity index 91% rename from src/pages/docs/arcus/data-sets/manage-data-sets.md rename to src/pages/docs/test-management/data-sets/manage-data-sets.md index d1c6c19..668ad0b 100644 --- a/src/pages/docs/arcus/data-sets/manage-data-sets.md +++ b/src/pages/docs/test-management/data-sets/manage-data-sets.md @@ -1,6 +1,6 @@ --- -title: 'Manage Data Sets in Arcus by Testsigma' -page_title: 'Manage Data Sets in Arcus by Testsigma' +title: 'Manage Data Sets in Test Management by Testsigma' +page_title: 'Manage Data Sets in Test Management by Testsigma' metadesc: '' noindex: false order: 4.1 @@ -38,13 +38,13 @@ contextual_links: --- -Test Data Sets let you store reusable data for use across multiple test cases. They reduce manual entry, minimize errors, and help generate diverse test scenarios for better coverage. This article discusses managing Data Sets in Arcus by Testsigma. +Test Data Sets let you store reusable data for use across multiple test cases. They reduce manual entry, minimize errors, and help generate diverse test scenarios for better coverage. This article discusses managing Data Sets in Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that you have an active account in Arcus by Testsigma. +> Before you begin, ensure that you have an active account in Test Management by Testsigma. --- @@ -113,7 +113,7 @@ Test Data Sets let you store reusable data for use across multiple test cases. T --- ## **Add Multiple Data Sets to Test Case** -Follow the “**Add Data Set to Test Case**” steps to add the first data set. Repeat to add more. Arcus by Testsigma generates unique test scenarios via Cartesian product (all row combinations across data sets). +Follow the “**Add Data Set to Test Case**” steps to add the first data set. Repeat to add more. Test Management by Testsigma generates unique test scenarios via Cartesian product (all row combinations across data sets). For Example, let’s say you have two data sets, Dataset A & Dataset B. diff --git a/src/pages/docs/arcus/imports-and-exports/browserstack.md b/src/pages/docs/test-management/imports-and-exports/browserstack.md similarity index 80% rename from src/pages/docs/arcus/imports-and-exports/browserstack.md rename to src/pages/docs/test-management/imports-and-exports/browserstack.md index f57fae6..014ba91 100644 --- a/src/pages/docs/arcus/imports-and-exports/browserstack.md +++ b/src/pages/docs/test-management/imports-and-exports/browserstack.md @@ -1,6 +1,6 @@ --- title: 'Importing Test Data from Browserstack' -page_title: 'Getting Started with Arcus by Testsigma' +page_title: 'Getting Started with Test Management by Testsigma' metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' noindex: false order: 5.4 @@ -22,13 +22,13 @@ contextual_links:
-**Learn how to export test cases from Browserstack and import them into Arcus by Testsigma.** +**Learn how to export test cases from Browserstack and import them into Test Management by Testsigma.** --- -You can export test cases from Testrail and import them into Arcus by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Arcus by Testsigma. +You can export test cases from Testrail and import them into Test Management by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Test Management by Testsigma. -Note: Currently, only test cases created using the Plain Text template can be imported into Arcus by Testsigma. +Note: Currently, only test cases created using the Plain Text template can be imported into Test Management by Testsigma. --- @@ -59,6 +59,6 @@ Note: Currently, only test cases created using the Plain Text template can be im 3. Click **Upload File** and select file to import. [[info | **NOTE**:]] -| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Arcus by Testsigma. +| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/imports-and-exports/csv-file.md b/src/pages/docs/test-management/imports-and-exports/csv-file.md similarity index 87% rename from src/pages/docs/arcus/imports-and-exports/csv-file.md rename to src/pages/docs/test-management/imports-and-exports/csv-file.md index 6837d64..2f100a3 100644 --- a/src/pages/docs/arcus/imports-and-exports/csv-file.md +++ b/src/pages/docs/test-management/imports-and-exports/csv-file.md @@ -1,7 +1,7 @@ --- title: 'Import Test Data from CSV Files' page_title: 'Import Test Data from CSV Files' -metadesc: 'Arcus by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature streamlines test case migration and bulk additions' +metadesc: 'Test Management by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature streamlines test case migration and bulk additions' noindex: false order: 5.1 page_id: 'import-test-data-from-csv-files' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to quickly import test cases in bulk using CSV files in Arcus by Testsigma for easy migration.** +**Learn how to quickly import test cases in bulk using CSV files in Test Management by Testsigma for easy migration.** --- -Arcus by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature simplifies the migration process from other tools by enabling bulk test case imports. This article discusses how to import test cases using a CSV file. +Test Management by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature simplifies the migration process from other tools by enabling bulk test case imports. This article discusses how to import test cases using a CSV file. --- @@ -78,7 +78,7 @@ Arcus by Testsigma allows you to quickly import test cases in CSV files into an - **Map Properties** to map CSV columns - **Test Case Preview** to validate mapped data -4. Atto automatically maps CSV columns to the corresponding fields in Arcus by Testsigma. +4. Atto automatically maps CSV columns to the corresponding fields in Test Management by Testsigma. 5. Review the mapped fields. If any fields are missing or incorrectly mapped, update them manually. diff --git a/src/pages/docs/arcus/imports-and-exports/export-tests.md b/src/pages/docs/test-management/imports-and-exports/export-tests.md similarity index 89% rename from src/pages/docs/arcus/imports-and-exports/export-tests.md rename to src/pages/docs/test-management/imports-and-exports/export-tests.md index 8c2b30a..76e3129 100644 --- a/src/pages/docs/arcus/imports-and-exports/export-tests.md +++ b/src/pages/docs/test-management/imports-and-exports/export-tests.md @@ -1,7 +1,7 @@ --- title: 'Export Test Data' page_title: 'Export Test Data' -metadesc: 'Arcus by Testsigma allows you to quickly export test cases/step groups in excel format. This feature streamlines quick migration of test cases/step groups' +metadesc: 'Test Management by Testsigma allows you to quickly export test cases/step groups in excel format. This feature streamlines quick migration of test cases/step groups' noindex: false order: 5.5 page_id: 'export-test-data-from-testsigma' @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to export test cases and step groups in Excel format from Arcus by Testsigma.** +**Learn how to export test cases and step groups in Excel format from Test Management by Testsigma.** --- -Testsigma allows you to export test cases and step groups in excel file format, with all the associated information. This feature helps you backup, migrate, or review your test data outside the platform. This document discusses exporting test cases and step groups from Arcus by Testsigma. +Testsigma allows you to export test cases and step groups in excel file format, with all the associated information. This feature helps you backup, migrate, or review your test data outside the platform. This document discusses exporting test cases and step groups from Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/imports-and-exports/testrail.md b/src/pages/docs/test-management/imports-and-exports/testrail.md similarity index 78% rename from src/pages/docs/arcus/imports-and-exports/testrail.md rename to src/pages/docs/test-management/imports-and-exports/testrail.md index ad2170a..26fcd19 100644 --- a/src/pages/docs/arcus/imports-and-exports/testrail.md +++ b/src/pages/docs/test-management/imports-and-exports/testrail.md @@ -1,7 +1,7 @@ --- title: 'Import Test Data from Testrail' page_title: 'Import Test Data from Testrail' -metadesc: 'Arcus by Testsigma allows you to quickly import test cases from Testrail into an existing project. This feature streamlines test case migration and bulk additions' +metadesc: 'Test Management by Testsigma allows you to quickly import test cases from Testrail into an existing project. This feature streamlines test case migration and bulk additions' noindex: false order: 5.3 page_id: 'import-test-data-from-testrail' @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to export test cases from Testrail and import them into Arcus by Testsigma.** +**Learn how to export test cases from Testrail and import them into Test Management by Testsigma.** --- -You can export test cases from Testrail and import them into Arcus by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Arcus by Testsigma. +You can export test cases from Testrail and import them into Test Management by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Test Management by Testsigma. --- @@ -62,6 +62,6 @@ You can export test cases from Testrail and import them into Arcus by Testsigma. 3. Click **Upload File** and select file to import. [[info | **NOTE**:]] -| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Arcus by Testsigma. +| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/imports-and-exports/zephyr.md b/src/pages/docs/test-management/imports-and-exports/zephyr.md similarity index 77% rename from src/pages/docs/arcus/imports-and-exports/zephyr.md rename to src/pages/docs/test-management/imports-and-exports/zephyr.md index e4cfc83..4ead12c 100644 --- a/src/pages/docs/arcus/imports-and-exports/zephyr.md +++ b/src/pages/docs/test-management/imports-and-exports/zephyr.md @@ -1,7 +1,7 @@ --- title: 'Import Test Data from Zephyr' page_title: 'Import Test Data from Zephyr' -metadesc: 'Arcus by Testsigma allows you to quickly import test cases Zephyr into an existing project. This feature streamlines test case migration and bulk additions' +metadesc: 'Test Management by Testsigma allows you to quickly import test cases Zephyr into an existing project. This feature streamlines test case migration and bulk additions' noindex: false order: 5.2 page_id: 'import-test-data-from-zephyr' @@ -22,14 +22,14 @@ contextual_links:
-**Learn how to export test cases from Zephyr and import them into Arcus by Testsigma.** +**Learn how to export test cases from Zephyr and import them into Test Management by Testsigma.** --- -You can export test cases from Zephyr and import them into Arcus by Testsigma. This article discusses the steps to export test cases from Zephyr and import them into Arcus by Testsigma. +You can export test cases from Zephyr and import them into Test Management by Testsigma. This article discusses the steps to export test cases from Zephyr and import them into Test Management by Testsigma. [[info | **NOTE**:]] -| Currently, only test cases created using the Plain Text template can be imported into Arcus by Testsigma. +| Currently, only test cases created using the Plain Text template can be imported into Test Management by Testsigma. --- @@ -65,6 +65,6 @@ You can export test cases from Zephyr and import them into Arcus by Testsigma. T 3. Click **Upload File** and select file to import. [[info | **NOTE**:]] -| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Arcus by Testsigma. +| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/index.jsx b/src/pages/docs/test-management/index.jsx similarity index 100% rename from src/pages/docs/arcus/index.jsx rename to src/pages/docs/test-management/index.jsx diff --git a/src/pages/docs/arcus/integrations/azure-devops.md b/src/pages/docs/test-management/integrations/azure-devops.md similarity index 76% rename from src/pages/docs/arcus/integrations/azure-devops.md rename to src/pages/docs/test-management/integrations/azure-devops.md index fcfe8e1..e8cf2bc 100644 --- a/src/pages/docs/arcus/integrations/azure-devops.md +++ b/src/pages/docs/test-management/integrations/azure-devops.md @@ -1,10 +1,10 @@ --- -title: 'Azure DevOps Integration with Arcus by Testsigma' -page_title: 'Azure DevOps Integration with Arcus by Testsigma' -metadesc: 'Arcus by Testsigma integrates with Azure DevOps to link test defects to work items, improving traceability and collaboration.' +title: 'Azure DevOps Integration with Test Management by Testsigma' +page_title: 'Azure DevOps Integration with Test Management by Testsigma' +metadesc: 'Test Management by Testsigma integrates with Azure DevOps to link test defects to work items, improving traceability and collaboration.' noindex: false order: 10.8 -page_id: 'azure-devops-integration-with-arcus-by-testsigma' +page_id: 'azure-devops-integration-with-test-management-by-testsigma' warning: false contextual_links: - type: section @@ -29,11 +29,11 @@ contextual_links:
-**Integrate Azure DevOps with Arcus by Testsigma to seamlessly link defects to Azure DevOps work items.** +**Integrate Azure DevOps with Test Management by Testsigma to seamlessly link defects to Azure DevOps work items.** --- -Arcus by Testsigma allows seamless integration with Azure DevOps, enabling you to link test defects directly to Azure DevOps work items. This improves traceability, streamlines defect management, and enhances collaboration between QA and development teams. +Test Management by Testsigma allows seamless integration with Azure DevOps, enabling you to link test defects directly to Azure DevOps work items. This improves traceability, streamlines defect management, and enhances collaboration between QA and development teams. --- diff --git a/src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md similarity index 85% rename from src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md rename to src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md index e02297f..1992654 100644 --- a/src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md +++ b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Cases in Azure DevOps' page_title: 'Manage Test Cases in Azure DevOps' -metadesc: 'Arcus by Testsigma lets you create and manage tests directly in Azure DevOps, and edit or unlink them from linked work items.' +metadesc: 'Test Management by Testsigma lets you create and manage tests directly in Azure DevOps, and edit or unlink them from linked work items.' noindex: false order: 10.22 page_id: 'manage-tests-in-azure-devops' @@ -29,11 +29,11 @@ contextual_links:
-**Learn how to create, edit, and manage test cases directly within Azure DevOps using Arcus by Testsigma app.** +**Learn how to create, edit, and manage test cases directly within Azure DevOps using Test Management by Testsigma app.** --- -The Arcus by Testsigma simplifies your workflow by allowing you to create and manage test cases directly in Azure DevOps. You can also edit or unlink test cases from the associated work item. +The Test Management by Testsigma simplifies your workflow by allowing you to create and manage test cases directly in Azure DevOps. You can also edit or unlink test cases from the associated work item. --- @@ -41,7 +41,7 @@ The Arcus by Testsigma simplifies your workflow by allowing you to create and ma > > Before you begin, ensure that: > -> - Your **Azure DevOps** project is linked to a Arcus by Testsigma project. +> - Your **Azure DevOps** project is linked to a Test Management by Testsigma project. > > - The **Testsigma for Azure DevOps** extension is installed and authorized. @@ -57,7 +57,7 @@ The Arcus by Testsigma simplifies your workflow by allowing you to create and ma 3. Open the required work item. ![required work item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_2.png) -4. In the work item details page, click the **Arcus by Testsigma** tab. +4. In the work item details page, click the **Test Management by Testsigma** tab. ![TMS tab](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_3.png) 5. View the linked test cases associated with the work item. @@ -70,7 +70,7 @@ The Arcus by Testsigma simplifies your workflow by allowing you to create and ma ## **Create a New Test Case from Azure DevOps** -1. In the **Azure DevOps** issue, go to the **Arcus by Testsigma > Linked Test Cases**. +1. In the **Azure DevOps** issue, go to the **Test Management by Testsigma > Linked Test Cases**. ![work items](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_4.png) 2. Click **Create**. This opens the **Create Test Case** dialog. @@ -97,7 +97,7 @@ The Arcus by Testsigma simplifies your workflow by allowing you to create and ma ## **Link Test Cases from Azure DevOps** -1. In the **Azure DevOps** issue, go to the **Arcus by Testsigma > Linked Test Runs**. +1. In the **Azure DevOps** issue, go to the **Test Management by Testsigma > Linked Test Runs**. ![work items](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_4.png) 2. Click **Link**. This will open the **Add Test Cases** dialog. @@ -113,7 +113,7 @@ The Arcus by Testsigma simplifies your workflow by allowing you to create and ma ## **Edit a Test Case from Azure DevOps** -1. In the **Azure DevOps** issue, go to the **Arcus by Testsigma > Linked Test Cases**. +1. In the **Azure DevOps** issue, go to the **Test Management by Testsigma > Linked Test Cases**. ![work items](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_4.png) 2. Click the **meatballs menu (⋯)** next to the test case, and select **Edit** from the dropdown. diff --git a/src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md similarity index 80% rename from src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md rename to src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md index 0051958..112fd77 100644 --- a/src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md +++ b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Runs in Azure DevOps' page_title: 'Manage Test Runs in Azure DevOps' -metadesc: 'The Arcus by Testsigma app simplifies your workflow by enabling you to manage test runs and test case results directly within Azure DevOps.' +metadesc: 'The Test Management by Testsigma app simplifies your workflow by enabling you to manage test runs and test case results directly within Azure DevOps.' noindex: false order: 10.23 page_id: 'manage-test-runs-in-azure-devops' @@ -29,17 +29,17 @@ contextual_links:
-**Learn how to manage test runs and update test case status directly within DevOps using Arcus by Testsigma.** +**Learn how to manage test runs and update test case status directly within DevOps using Test Management by Testsigma.** --- -The Arcus by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Azure DevOps. You can update test results, add or link defects, and manage linked test cases from within the Azure DevOps issue view. +The Test Management by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Azure DevOps. You can update test results, add or link defects, and manage linked test cases from within the Azure DevOps issue view. --- > ## **Prerequisites** > -> Before you begin, ensure that your Testsigma project is connected to an Azure DevOps project in Arcus by Testsigma. +> Before you begin, ensure that your Testsigma project is connected to an Azure DevOps project in Test Management by Testsigma. --- @@ -53,7 +53,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te 3. Open the required work item. ![required work item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_2.png) -4. In the work item details page, click the **Arcus by Testsigma** tab. +4. In the work item details page, click the **Test Management by Testsigma** tab. ![TMS tab](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_3.png) 5. View the linked test runs associated with the work item. @@ -66,7 +66,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te ## **Update Test Case Results from Azure DevOps** -1. In the **Azure DevOps** issue, go to **Arcus by Testsigma > Linked Test Runs**. +1. In the **Azure DevOps** issue, go to **Test Management by Testsigma > Linked Test Runs**. ![Work Item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_test_runs_1.png) 2. Expand the test run. @@ -77,13 +77,13 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te 4. Refresh the page to view the updated status in **Linked Test Cases**. [[info | **NOTE**:]] -| - The test case status will also be updated in Arcus by Testsigma. +| - The test case status will also be updated in Test Management by Testsigma. --- ## **Add Defects from Azure DevOps** -1. In the **Azure DevOps** issue, go to **Arcus by Testsigma > Linked Test Runs**. +1. In the **Azure DevOps** issue, go to **Test Management by Testsigma > Linked Test Runs**. ![Work Item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_test_runs_1.png) 2. Expand the test run. @@ -100,7 +100,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te ## **Link Defects to Existing Issues** -1. In the Azure DevOps issue, go to **Arcus by Testsigma > Linked Test Runs**. +1. In the Azure DevOps issue, go to **Test Management by Testsigma > Linked Test Runs**. ![Work Item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_test_runs_1.png) 2. Expand the test run. diff --git a/src/pages/docs/arcus/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md similarity index 87% rename from src/pages/docs/arcus/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md rename to src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md index eaffca0..a7d05b1 100644 --- a/src/pages/docs/arcus/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md +++ b/src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md @@ -29,11 +29,11 @@ contextual_links:
-**You can create, run, and manage your tests inside Azure DevOps. Just like you do in Arcus by Testsigma.** +**You can create, run, and manage your tests inside Azure DevOps. Just like you do in Test Management by Testsigma.** --- -The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capabilities to include native test management. This enables teams to create, manage, and track test cases and test runs directly within the Azure DevOps environment, without switching to Arcus by Testsigma. You can associate test results with work items, streamline pipelines, and maintain end-to-end traceability within Azure Boards and Repos. The integration accelerates testing cycles and enhances collaboration between QA and development teams from a unified workspace. +The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capabilities to include native test management. This enables teams to create, manage, and track test cases and test runs directly within the Azure DevOps environment, without switching to Test Management by Testsigma. You can associate test results with work items, streamline pipelines, and maintain end-to-end traceability within Azure Boards and Repos. The integration accelerates testing cycles and enhances collaboration between QA and development teams from a unified workspace. --- @@ -45,7 +45,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab ## **Connect TMS to Azure DevOps** -1. Log in to your Arcus by Testsigma account. +1. Log in to your Test Management by Testsigma account. 2. From the left navigation bar, navigate to **Settings > Integrations**. ![Integrations](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_1.png) @@ -53,7 +53,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab 3. In the Integrations screen, click **Setup Integration** against **Azure DevOps**. ![Azure DevOps](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_2.png) -4. Follow the OAuth-based authorization steps to connect Azure DevOps with Arcus by Testsigma. +4. Follow the OAuth-based authorization steps to connect Azure DevOps with Test Management by Testsigma. --- @@ -61,7 +61,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab 1. Open the [Azure DevOps Marketplace](https://marketplace.visualstudio.com/items?itemName=testsigma.testsigma-azure-devops). -2. Search for **Arcus by Testsigma**. +2. Search for **Test Management by Testsigma**. 3. Install the extension in your Azure DevOps organization. ![Install TMS by Testsigma](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_3.png) @@ -79,7 +79,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab 3. Click **Testsigma for Azure DevOps**. ![Testsigma for Azure Devops](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_6.png) -4. Click **Authorize Azure DevOps Extension** and complete the authorization with Arcus by Testsigma. +4. Click **Authorize Azure DevOps Extension** and complete the authorization with Test Management by Testsigma. ![Authorize Azure DevOps Extension](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_7.png) --- diff --git a/src/pages/docs/arcus/integrations/clickup.md b/src/pages/docs/test-management/integrations/clickup.md similarity index 84% rename from src/pages/docs/arcus/integrations/clickup.md rename to src/pages/docs/test-management/integrations/clickup.md index 55e30db..5a262e7 100644 --- a/src/pages/docs/arcus/integrations/clickup.md +++ b/src/pages/docs/test-management/integrations/clickup.md @@ -1,7 +1,7 @@ --- -title: 'ClickUp Integration with Arcus by Testsigma' +title: 'ClickUp Integration with Test Management by Testsigma' page_title: 'ClickUp Integration with Testsigma' -metadesc: 'Integrate Arcus by Testsigma with ClickUp to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' +metadesc: 'Integrate Test Management by Testsigma with ClickUp to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' noindex: false order: 10.6 page_id: 'clickup-integration-with-testsigma-test-management' @@ -31,11 +31,11 @@ contextual_links:
-**Integrate ClickUp with Arcus by Testsigma to seamlessly link defects to ClickUp tasks.** +**Integrate ClickUp with Test Management by Testsigma to seamlessly link defects to ClickUp tasks.** --- -Arcus by Testsigma allows seamless integration with ClickUp, which enables you to link test defects directly to ClickUp tasks. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. +Test Management by Testsigma allows seamless integration with ClickUp, which enables you to link test defects directly to ClickUp tasks. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. --- diff --git a/src/pages/docs/arcus/integrations/confluence.md b/src/pages/docs/test-management/integrations/confluence.md similarity index 87% rename from src/pages/docs/arcus/integrations/confluence.md rename to src/pages/docs/test-management/integrations/confluence.md index 54802bb..933fac2 100644 --- a/src/pages/docs/arcus/integrations/confluence.md +++ b/src/pages/docs/test-management/integrations/confluence.md @@ -1,7 +1,7 @@ --- -title: 'Confluence Integration with Arcus by Testsigma' +title: 'Confluence Integration with Test Management by Testsigma' page_title: 'Confluence Integration with Testsigma' -metadesc: 'The Confluence integration enables users to generate test cases directly from a Confluence page | Learn how to integrate Confluence with Arcus by Testsigma' +metadesc: 'The Confluence integration enables users to generate test cases directly from a Confluence page | Learn how to integrate Confluence with Test Management by Testsigma' noindex: false order: 10.7 page_id: 'confluence-integration-with-testsigma-test-management' @@ -22,11 +22,11 @@ contextual_links:
-**Configure the Confluence integration in Arcus by Testsigma.** +**Configure the Confluence integration in Test Management by Testsigma.** --- -Confluence is a team collaboration and knowledge management platform used to create, organize, and share documentation. The Confluence integration enables users to generate structured test cases directly from a Confluence page in Arcus by Testsigma. +Confluence is a team collaboration and knowledge management platform used to create, organize, and share documentation. The Confluence integration enables users to generate structured test cases directly from a Confluence page in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/integrations/figma.md b/src/pages/docs/test-management/integrations/figma.md similarity index 91% rename from src/pages/docs/arcus/integrations/figma.md rename to src/pages/docs/test-management/integrations/figma.md index beea9f8..a55f123 100644 --- a/src/pages/docs/arcus/integrations/figma.md +++ b/src/pages/docs/test-management/integrations/figma.md @@ -1,5 +1,5 @@ --- -title: 'Figma Integration with Arcus by Testsigma' +title: 'Figma Integration with Test Management by Testsigma' page_title: 'Figma Integration with Testsigma' metadesc: 'Generate test cases directly from Figma designs in Testsigma | Ensure design-to-test alignment and accelerate test creation by converting UI elements into test steps' noindex: false @@ -25,7 +25,7 @@ contextual_links:
-**Integrate Figma with Arcus by Testsigma to generate test cases from your designs.** +**Integrate Figma with Test Management by Testsigma to generate test cases from your designs.** --- @@ -35,7 +35,7 @@ Testsigma lets you generate test cases directly from your Figma designs. This he > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Arcus by Testsigma and have integrated your Figma account. +> Before you begin, ensure you have a project created in Test Management by Testsigma and have integrated your Figma account. --- diff --git a/src/pages/docs/arcus/integrations/jira-two-way-integration/install-and-connect-testsigma.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md similarity index 70% rename from src/pages/docs/arcus/integrations/jira-two-way-integration/install-and-connect-testsigma.md rename to src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md index 8254068..774fbb0 100644 --- a/src/pages/docs/arcus/integrations/jira-two-way-integration/install-and-connect-testsigma.md +++ b/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md @@ -13,8 +13,8 @@ contextual_links: name: 'Prerequisites' url: '#prerequisites' - type: link - name: 'Install the Arcus by Testsigma app' - url: '#install-the-arcus-by-testsigma-app' + name: 'Install the Test Management by Testsigma app' + url: '#install-the-test-management-by-testsigma-app' - type: link name: 'Connect Testsigma and Jira' url: '#connect-testsigma-and-jira' @@ -22,11 +22,11 @@ contextual_links:
-**You can create, run, and manage your tests inside Jira. Just like you do in Arcus by Testsigma.** +**You can create, run, and manage your tests inside Jira. Just like you do in Test Management by Testsigma.** --- -The Testsigma Integration for Jira app seamlessly extends Jira’s core capabilities to include native test management. This allows teams to create, manage, and track test cases and test runs directly from the Jira environment, without switching to Arcus by Testsigma. You can add test results to stories, streamline workflows, and maintain testing continuity within Jira. The integration enhances issue tracking, accelerates testing cycles, and improves collaboration between QA and development teams from a unified workspace. +The Testsigma Integration for Jira app seamlessly extends Jira’s core capabilities to include native test management. This allows teams to create, manage, and track test cases and test runs directly from the Jira environment, without switching to Test Management by Testsigma. You can add test results to stories, streamline workflows, and maintain testing continuity within Jira. The integration enhances issue tracking, accelerates testing cycles, and improves collaboration between QA and development teams from a unified workspace. --- @@ -36,19 +36,19 @@ The Testsigma Integration for Jira app seamlessly extends Jira’s core capabili --- -## **Install the Arcus by Testsigma App** +## **Install the Test Management by Testsigma App** -1. Navigate to the Atlassian Marketplace and search for **Arcus by Testsigma**. +1. Navigate to the Atlassian Marketplace and search for **Test Management by Testsigma**. -2. Install **Arcus by Testsigma** in your Jira instance. +2. Install **Test Management by Testsigma** in your Jira instance. -3. In Jira, go to **Apps > Manage apps** and confirm **Arcus by Testsigma** is installed. +3. In Jira, go to **Apps > Manage apps** and confirm **Test Management by Testsigma** is installed. ![Testsigma App for Jira Cloud](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/testsigma_app_for_jira.png) --- ## **Connect Testsigma and Jira** -1. In the left panel under **Apps**, click **Arcus by Testsigma**. This opens the authorization page. +1. In the left panel under **Apps**, click **Test Management by Testsigma**. This opens the authorization page. 2. On the **Connect Testsigma to Jira** page, click **Authorize to Jira Marketplace App** Integration. ![Connect Testsigma to Jira](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Connect_Testsigma_App.png) diff --git a/src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-cases-in-jira.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md similarity index 83% rename from src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-cases-in-jira.md rename to src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md index 6a3a467..d466810 100644 --- a/src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-cases-in-jira.md +++ b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Cases in Jira App' page_title: 'Manage Test Cases in Jira' -metadesc: 'The Arcus by Testsigma app simplifies your workflow by allowing you to create & manage tests directly in Jira. You can also edit, or unlink tests from the linked Jira issue.' +metadesc: 'The Test Management by Testsigma app simplifies your workflow by allowing you to create & manage tests directly in Jira. You can also edit, or unlink tests from the linked Jira issue.' noindex: false order: 10.12 page_id: 'manage-tests-in-jira-app' @@ -28,17 +28,17 @@ contextual_links:
-**Learn how to create, edit, and manage test cases directly within Jira using Arcus by Testsigma app.** +**Learn how to create, edit, and manage test cases directly within Jira using Test Management by Testsigma app.** --- -The Arcus by Testsigma app simplifies your workflow by allowing you to create and manage test cases directly in Jira. You can also edit, or unlink test cases from the associated Jira issue. +The Test Management by Testsigma app simplifies your workflow by allowing you to create and manage test cases directly in Jira. You can also edit, or unlink test cases from the associated Jira issue. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project and that it's connected to a Jira project in Arcus by Testsigma. +> Before you begin, ensure you have a project and that it's connected to a Jira project in Test Management by Testsigma. --- @@ -46,7 +46,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to create an 1. Open the Jira issue in a linked Jira project. -2. Click **Jira App Actions** and then select **Arcus by Testsigma**. +2. Click **Jira App Actions** and then select **Test Management by Testsigma**. ![Testsigma App Connection](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Connect_Testsigma_to_Issue.png) [[info | **NOTE**:]] @@ -56,7 +56,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to create an ## **Create a New Test Case from Jira** -1. In the Jira issue, go to the **Arcus by Testsigma > Linked Test Cases**. +1. In the Jira issue, go to the **Test Management by Testsigma > Linked Test Cases**. ![Linked Cases](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Cases_in_Jira.png) 2. Click **Create**. This opens the **Create Test Case** dialog. @@ -83,7 +83,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to create an ## **Link Test Cases from Jira** -1. In the Jira issue, go to the **Arcus by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to the **Test Management by Testsigma > Linked Test Runs**. 2. Click **Link**. This will open the **Add Test Cases** dialog. ![Link](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Link_Test_From_Jira.png) @@ -98,7 +98,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to create an **Edit a Test Case from Jira App** -1. In the Jira issue, go to the **Arcus by Testsigma > Linked Test Cases**. +1. In the Jira issue, go to the **Test Management by Testsigma > Linked Test Cases**. 2. Click the **meatballs menu (⋯)** next to the test case, and select **Edit** from dropdown. ![Edit Test Case](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Edit_Test_from_Jira.png) diff --git a/src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-runs-in-jira.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md similarity index 79% rename from src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-runs-in-jira.md rename to src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md index a31cd67..549e578 100644 --- a/src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-runs-in-jira.md +++ b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Runs in Jira App' page_title: 'Manage Test Runs in Jira' -metadesc: 'The Arcus by Testsigma app simplifies your workflow by allowing you to manage test runs & test case results directly within Jira.' +metadesc: 'The Test Management by Testsigma app simplifies your workflow by allowing you to manage test runs & test case results directly within Jira.' noindex: false order: 10.13 page_id: 'manage-test-runs-in-jira-app' @@ -28,17 +28,17 @@ contextual_links:
-**Learn how to manage test runs and update test case status directly within Jira using Arcus by Testsigma.** +**Learn how to manage test runs and update test case status directly within Jira using Test Management by Testsigma.** --- -The Arcus by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Jira. You can update test results, add or link defects, and manage linked test cases from within the Jira issue view. +The Test Management by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Jira. You can update test results, add or link defects, and manage linked test cases from within the Jira issue view. --- > ## **Prerequisites** > -> Before you begin, ensure that your Testsigma project is connected to a Jira project in Arcus by Testsigma. +> Before you begin, ensure that your Testsigma project is connected to a Jira project in Test Management by Testsigma. --- @@ -46,7 +46,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te 1. Open the Jira issue in a linked Jira project. -2. Click **Jira App Actions**, and then select **Arcus by Testsigma**. +2. Click **Jira App Actions**, and then select **Test Management by Testsigma**. ![Testsigma App Connection](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Connect_Testsigma_to_Issue.png) [[info | **NOTE**:]] @@ -56,7 +56,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te ## **Update Test Case Results from Jira** -1. In the Jira issue, go to **Arcus by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to **Test Management by Testsigma > Linked Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Test_Runs_In_Jira.png) 2. Expand the test run. @@ -67,13 +67,13 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te 4. Refresh the page to view the updated status in **Linked Test Cases**. [[info | **NOTE**:]] -| The test case status will also update in Arcus by Testsigma. +| The test case status will also update in Test Management by Testsigma. --- ## **Add Defects from the Jira App** -1. In the Jira issue, go to **Arcus by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to **Test Management by Testsigma > Linked Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Test_Runs_In_Jira.png) 2. Expand the test run. @@ -90,7 +90,7 @@ The Arcus by Testsigma app simplifies your workflow by allowing you to manage te ## **Link Defects to Existing Issues** -1. In the Jira issue, go to **Arcus by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to **Test Management by Testsigma > Linked Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Test_Runs_In_Jira.png) 2. Expand the test run. diff --git a/src/pages/docs/arcus/integrations/jira.md b/src/pages/docs/test-management/integrations/jira.md similarity index 84% rename from src/pages/docs/arcus/integrations/jira.md rename to src/pages/docs/test-management/integrations/jira.md index 6419888..b1a63da 100644 --- a/src/pages/docs/arcus/integrations/jira.md +++ b/src/pages/docs/test-management/integrations/jira.md @@ -1,7 +1,7 @@ --- -title: 'Jira Integration with Arcus by Testsigma' +title: 'Jira Integration with Test Management by Testsigma' page_title: 'Jira Integration with Testsigma' -metadesc: 'Integrate Arcus by Testsigma with Jira to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' +metadesc: 'Integrate Test Management by Testsigma with Jira to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' noindex: false order: 10.3 page_id: 'jira-integration-with-testsigma-test-management' @@ -31,11 +31,11 @@ contextual_links:
-**Integrate Jira with Arcus by Testsigma to seamlessly link defects to Jira issues.** +**Integrate Jira with Test Management by Testsigma to seamlessly link defects to Jira issues.** --- -Arcus by Testsigma allows seamless integration with Jira, which enables you to link test defects directly to Jira issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. +Test Management by Testsigma allows seamless integration with Jira, which enables you to link test defects directly to Jira issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. --- diff --git a/src/pages/docs/arcus/integrations/linear.md b/src/pages/docs/test-management/integrations/linear.md similarity index 84% rename from src/pages/docs/arcus/integrations/linear.md rename to src/pages/docs/test-management/integrations/linear.md index cf42c93..00353f1 100644 --- a/src/pages/docs/arcus/integrations/linear.md +++ b/src/pages/docs/test-management/integrations/linear.md @@ -1,7 +1,7 @@ --- -title: 'Linear Integration with Arcus by Testsigma' +title: 'Linear Integration with Test Management by Testsigma' page_title: 'Linear Integration with Testsigma' -metadesc: 'Integrate Arcus by Testsigma with Linear to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' +metadesc: 'Integrate Test Management by Testsigma with Linear to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' noindex: false order: 10.5 page_id: 'linear-integration-with-testsigma-test-management' @@ -31,11 +31,11 @@ contextual_links:
-**Integrate Linear with Arcus by Testsigma to seamlessly link defects to Linear issues.** +**Integrate Linear with Test Management by Testsigma to seamlessly link defects to Linear issues.** --- -Arcus by Testsigma allows seamless integration with Linear, which enables you to link test defects directly to Linear issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. +Test Management by Testsigma allows seamless integration with Linear, which enables you to link test defects directly to Linear issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. --- diff --git a/src/pages/docs/test-management/introduction/getting-started.md b/src/pages/docs/test-management/introduction/getting-started.md new file mode 100644 index 0000000..d18209f --- /dev/null +++ b/src/pages/docs/test-management/introduction/getting-started.md @@ -0,0 +1,61 @@ +--- +title: 'Getting Started: Test Management by Testsigma' +page_title: 'Getting Started with Test Management by Testsigma' +metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' +noindex: false +order: 1.2 +page_id: 'getting-started-testsigma-test-management' +warning: false +contextual_links: + - type: section + name: 'Contents' + - type: link + name: 'Interactive Demo' + url: '#interactive-demo' + - type: link + name: 'Steps to Access Test Management by Testsigma' + url: '#steps-to-access-testsigma-test-management' +--- + +--- + +Get started with our platform and streamline how you manage and analyze test cases, plans, and runs. This article discusses steps to set up your Test Management with Testsigma. + +[[info | **NOTE**:]] +| If you're an existing Testsigma user, contact **support@testsigma.com** to connect your account with the Test Management by Testsigma tool. + +--- + +> ## **Prerequisites** +> +> Before you begin, ensure you have an active Testsigma account. If you don’t have one, go to the Testsigma signup page to create an account. + +--- + +## **Interactive Demo** + +
+ +
+ +
+
+ +--- + +## **Steps to Access Test Management by Testsigma** + +1. Navigate to Test Management by Testsigma Login Page. + +2. Sign in with your credentials. If you don't have an account, sign up. + +3. In your **User Profile Settings**, select **TMS**. + +4. You'll be redirected to **Test Management by Testsigma** application. + +5. On the **Dashboard**, click the **Candy Box** icon and select **+ New Project** to get started. + +[[info | **NOTE**:]] +| When you log in for the first time, you're automatically redirected to the project creation page. For more information, see **Projects**. + +--- diff --git a/src/pages/docs/test-management/introduction/overview.md b/src/pages/docs/test-management/introduction/overview.md new file mode 100644 index 0000000..60860f1 --- /dev/null +++ b/src/pages/docs/test-management/introduction/overview.md @@ -0,0 +1,49 @@ +--- +title: 'Overview: Test Management by Testsigma' +page_title: 'Overview of Test Management in Testsigma' +metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' +noindex: false +order: 1.1 +page_id: 'Overview: Test Management by Testsigma' +warning: false +contextual_links: + - type: section + name: 'Contents' + - type: link + name: 'Benefits of Using Test Management by Testsigma' + url: '#benefits-of-using-testsigma-test-management' +--- + +--- + +Managing test cases shouldn't be a mess. If you're using traditional Test Management tools or Excel for it, you know the pain! Endless spreadsheets, scattered data, and lots of copy-pasting. As the projects grow, things only get worse. + +Test Management by Testsigma changes that. It keeps your test cases, test plans, test runs, and reports organized and accessible in one place. No more digging through tabs or wondering who updated what. + +Test Management isn’t just about managing tests, it’s about making testing work for you, not against you! + +--- + +## **Benefits of Using Test Management by Testsigma** + +### ⚡ **Faster Testing, Fewer Errors** + +Automate repetitive tasks and reduce manual errors to speed up test execution. + +### 🤝 **Seamless Collaboration** + +Centralize test management so teams and stakeholders always stay aligned. + +### 📋 **Better Test Coverage** + +Document every test case for thorough and consistent testing. + +### 🐞 **Effortless Defect Tracking** + +Log and track defects instantly with Jira integration. + +### 🤖 **AI-Powered Productivity with ATTO (Agentic AI)** + +Leverage ATTO's capabilities to autonomously create tests, execute them, and report bugs. + +--- diff --git a/src/pages/docs/arcus/manage-users/invite-users.md b/src/pages/docs/test-management/manage-users/invite-users.md similarity index 74% rename from src/pages/docs/arcus/manage-users/invite-users.md rename to src/pages/docs/test-management/manage-users/invite-users.md index 9ce97b4..255f5ee 100644 --- a/src/pages/docs/arcus/manage-users/invite-users.md +++ b/src/pages/docs/test-management/manage-users/invite-users.md @@ -1,7 +1,7 @@ --- title: 'Invite Users' -page_title: 'Invite Users to Arcus by Testsigma' -metadesc: 'Invite users to your Arcus by Testsigma to collaborate & assign roles & permissions to control access based on their responsibilities.' +page_title: 'Invite Users to Test Management by Testsigma' +metadesc: 'Invite users to your Test Management by Testsigma to collaborate & assign roles & permissions to control access based on their responsibilities.' noindex: false order: 13.1 page_id: 'users-in-testsigma-test-management' @@ -22,17 +22,17 @@ contextual_links:
-**Learn how to invite users & assign roles and permissions for effective collaboration in Arcus by Testsigma.** +**Learn how to invite users & assign roles and permissions for effective collaboration in Test Management by Testsigma.** --- -Invite users to your Arcus by Testsigma to collaborate and assign roles and permissions to control access based on their responsibilities. This article discusses inviting users to your Arcus by Testsigma. +Invite users to your Test Management by Testsigma to collaborate and assign roles and permissions to control access based on their responsibilities. This article discusses inviting users to your Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project in Arcus by Testsigma and the necessary permissions to invite team members. +> Before you begin, ensure you have a project in Test Management by Testsigma and the necessary permissions to invite team members. --- diff --git a/src/pages/docs/arcus/projects/manage-projects.md b/src/pages/docs/test-management/projects/manage-projects.md similarity index 79% rename from src/pages/docs/arcus/projects/manage-projects.md rename to src/pages/docs/test-management/projects/manage-projects.md index e0a1ce9..08187eb 100644 --- a/src/pages/docs/arcus/projects/manage-projects.md +++ b/src/pages/docs/test-management/projects/manage-projects.md @@ -1,7 +1,7 @@ --- title: 'Projects: Top-Level of Test Management' -page_title: 'Projects in Arcus by Testsigma' -metadesc: 'In Arcus by Testsigma, projects come at the top level of the hierarchy that contains test cases, test runs, and test plans | Learn about projects in Test Management' +page_title: 'Projects in Test Management by Testsigma' +metadesc: 'In Test Management by Testsigma, projects come at the top level of the hierarchy that contains test cases, test runs, and test plans | Learn about projects in Test Management' noindex: false order: 2.1 page_id: 'projects-in-testsigma-test-management' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to create, edit, or delete projects in Arcus by Testsigma with ease.** +**Learn how to create, edit, or delete projects in Test Management by Testsigma with ease.** --- -In Arcus by Testsigma, the projects come at the top level of the hierarchy. Each project contains test cases, runs, and plans for a specific application. With everything in one place, tracking progress is more manageable, and you can focus on delivering high-quality testing confidently. This article discusses managing projects in Arcus by Testsigma. +In Test Management by Testsigma, the projects come at the top level of the hierarchy. Each project contains test cases, runs, and plans for a specific application. With everything in one place, tracking progress is more manageable, and you can focus on delivering high-quality testing confidently. This article discusses managing projects in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/projects/project-settings.md b/src/pages/docs/test-management/projects/project-settings.md similarity index 79% rename from src/pages/docs/arcus/projects/project-settings.md rename to src/pages/docs/test-management/projects/project-settings.md index f29d5b5..30e809e 100644 --- a/src/pages/docs/arcus/projects/project-settings.md +++ b/src/pages/docs/test-management/projects/project-settings.md @@ -1,7 +1,7 @@ --- title: 'Project Settings: Project Details and Test Assets' -page_title: 'Project Settings in Arcus by Testsigma' -metadesc: 'Update project details & manage test cases and step groups through import & export options | This article explains how to perform these actions in Arcus by Testsigma' +page_title: 'Project Settings in Test Management by Testsigma' +metadesc: 'Update project details & manage test cases and step groups through import & export options | This article explains how to perform these actions in Test Management by Testsigma' noindex: false order: 2.2 page_id: 'project-settings-in-testsigma-test-management' @@ -40,7 +40,7 @@ Project Settings allows you to update project details, manage test cases and ste > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see [Projects](http://testsigma.com/docs/test-management/projects/manage-projects/). +> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see [Projects](http://testsigma.com/docs/test-management/projects/manage-projects/). --- @@ -62,7 +62,7 @@ For more information, see [Imports](https://testsigma.com/docs/test-management/i ## **Export Test Cases and Step Groups** -Export test cases and step groups from Arcus by Testsigma with their associated details. +Export test cases and step groups from Test Management by Testsigma with their associated details. For more information, see [Exports](https://testsigma.com/docs/test-management/imports-and-exports/export-tests/). @@ -70,7 +70,7 @@ For more information, see [Exports](https://testsigma.com/docs/test-management/i ## **Review Management** -Review Management provides a structured review workflow for test cases in Arcus by Testsigma. You can enable or disable Review Management from Project Settings. +Review Management provides a structured review workflow for test cases in Test Management by Testsigma. You can enable or disable Review Management from Project Settings. For more information, see [Review Management](https://testsigma.com/docs/test-management/test-cases/review-management/). diff --git a/src/pages/docs/arcus/qi-home/ad-hoc/attach-context-sources.md b/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md similarity index 88% rename from src/pages/docs/arcus/qi-home/ad-hoc/attach-context-sources.md rename to src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md index 4ff4f47..2180614 100644 --- a/src/pages/docs/arcus/qi-home/ad-hoc/attach-context-sources.md +++ b/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md @@ -1,8 +1,8 @@ --- title: 'Attach Context Sources' page_title: 'Attach Context Sources' -metadesc: 'Attach context sources such as Jira, Confluence, Figma, files, and video recordings so the Generator Agent creates test cases that accurately reflect your feature.' -description: 'Learn how to attach context sources in the Playground before generating test cases with the Generator Agent.' +metadesc: 'Attach context sources such as Jira, Confluence, Figma, files, and video recordings so Atto generates test cases that accurately reflect your feature.' +description: 'Learn how to attach context sources in the Playground before generating test cases with Atto.' noindex: false order: 13.21 page_id: 'qi-home-attach-context-sources' @@ -38,11 +38,11 @@ contextual_links:
-**Give the Generator Agent the right context and it creates test cases that accurately reflect your feature.** +**Give Atto the right context and it generates test cases that accurately reflect your feature.** --- -Context sources are the inputs the Generator Agent reads before generating test cases. The more relevant your context, the more accurate and complete the output. You can attach context from your project management tools, design files, images, videos, and documents, all in the same session. +Context sources are the inputs Atto reads before generating test cases. The more relevant your context, the more accurate and complete the output. You can attach context from your project management tools, design files, images, videos, and documents, all in the same session. You attach context sources inside the Playground, before writing a prompt and triggering generation. You can attach from multiple sources in a single session and add or remove sources any time before clicking **Generate with AI**. @@ -51,7 +51,7 @@ You attach context sources inside the Playground, before writing a prompt and tr > ## **Prerequisites** > > Before you begin, ensure that: -> - You have an active project in Arcus by Testsigma. +> - You have an active project in Test Management by Testsigma. > - The integrations for the tools you want to attach context from are connected to your project. > - The files or documents you want to attach are available on your device. @@ -83,7 +83,7 @@ The Playground shows a prompt input area with an **Add Context** bar at the bott 3. The **Issue Type** defaults to **Story**. Change it if you want to pull in **Epics** or other **Issue Types**. -4. In the stories list, select the checkboxes next to the stories you want the Generator Agent to use as context. +4. In the stories list, select the checkboxes next to the stories you want Atto to use as context. [[info | **NOTE**:]] | Use the **Search** icon at the top of the stories list to find specific stories by title or ID. @@ -112,7 +112,7 @@ The flow for Azure DevOps, Linear, and ClickUp follows the same pattern as Jira. 2. Select the **Space** you want to pull pages from. -3. Select the **Pages** you want the Generator Agent to read. +3. Select the **Pages** you want Atto to read. 4. Click **Save**. @@ -191,6 +191,6 @@ After saving a source, it appears as a badge at the top of the prompt input show [[info | **NOTE**:]] | Context is not saved between sessions. Each new Ad-Hoc session starts with no context attached. -With context attached, the next step is to write your prompt. See [Write Effective Prompts](https://testsigma.com/docs/arcus/qi-home/ad-hoc/write-effective-prompts/). +With context attached, the next step is to write your prompt. See [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/). --- diff --git a/src/pages/docs/arcus/qi-home/ad-hoc/generate-test-cases.md b/src/pages/docs/test-management/qi-home/ad-hoc/generate-test-cases.md similarity index 57% rename from src/pages/docs/arcus/qi-home/ad-hoc/generate-test-cases.md rename to src/pages/docs/test-management/qi-home/ad-hoc/generate-test-cases.md index b482c50..bab4dfb 100644 --- a/src/pages/docs/arcus/qi-home/ad-hoc/generate-test-cases.md +++ b/src/pages/docs/test-management/qi-home/ad-hoc/generate-test-cases.md @@ -1,8 +1,8 @@ --- title: 'Generate Test Cases' page_title: 'Generate Test Cases (Ad-Hoc)' -metadesc: 'Write your prompt, click Generate with AI, and the Generator Agent builds your test cases. Learn how to trigger Ad-Hoc generation and read the generation summary.' -description: 'Learn how to trigger test case generation in Ad-Hoc and what the Generator Agent does during the process.' +metadesc: 'Write your prompt, click Generate with AI, and Atto builds your test cases. Learn how to trigger Ad-Hoc generation and read the generation summary.' +description: 'Learn how to trigger test case generation in Ad-Hoc and what Atto does during the process.' noindex: false order: 13.23 page_id: 'qi-home-ad-hoc-generate-test-cases' @@ -29,18 +29,18 @@ contextual_links:
-**Write your prompt, click Generate with AI, and the Generator Agent builds your test cases.** +**Write your prompt, click Generate with AI, and Atto builds your test cases.** --- -This article covers how to trigger test case generation in Ad-Hoc and what the Generator Agent does during the process. Before generating, make sure you have attached your context sources and written your prompt. See [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/arcus/qi-home/ad-hoc/write-effective-prompts/). +This article covers how to trigger test case generation in Ad-Hoc and what Atto does during the process. Before generating, make sure you have attached your context sources and written your prompt. See [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/). --- > ## **Prerequisites** > > Before you begin, ensure that: -> - The Playground is open from **QI Home > Adhoc**. See [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/arcus/qi-home/ad-hoc/write-effective-prompts/) if you have not done this yet. +> - The Playground is open from **QI Home > Adhoc**. See [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/) if you have not done this yet. > - You have attached at least one context source and written your prompt. --- @@ -55,24 +55,24 @@ This article covers how to trigger test case generation in Ad-Hoc and what the G 4. Click **Generate with AI**. -The Generator Agent begins generating test cases. The generation log appears in the left panel, showing each step as it progresses. +Atto begins generating test cases. The generation log appears in the left panel, showing each step as it progresses. --- ## **What Happens During Generation** -After you click **Generate with AI**, the Generator Agent begins building your test cases. You can watch the progress in the left panel as each step completes. Generation typically takes 5–10 minutes depending on the amount of context attached. +After you click **Generate with AI**, Atto begins building your test cases. You can watch the progress in the left panel as each step completes. Generation typically takes 5–10 minutes depending on the amount of context attached. [[info | **NOTE**:]] -| The Generator Agent searches your existing test library during generation to avoid duplicating coverage you already have. If you want faster generation without this check, you can disable it in the Playground. +| Atto searches your existing test library during generation to avoid duplicating coverage you already have. If you want faster generation without this check, you can disable it in the Playground. --- ## **Review the Generation Summary** -When generation completes, the left panel shows a summary of what the Generator Agent produced. +When generation completes, the left panel shows a summary of what Atto produced. @@ -80,11 +80,11 @@ The summary includes: - **Test type breakdown**: The number of test cases by type: Functional, Non-Functional, User Experience, and Integration. - **Scenarios with full test cases**: A table listing each scenario, its mapped story, and the number of test cases generated. -- **Reusable Step Groups proposed**: Step groups the Generator Agent identified from your test library that apply to the generated scenarios. +- **Reusable Step Groups proposed**: Step groups Atto identified from your test library that apply to the generated scenarios. - **Remaining Scenario Outlines**: Scenarios that have been created as stubs but not yet fully filled. These are organized by area (for example, Search, Filters, Checkout). You can fill them later using the Playground. [[info | **NOTE**:]] -| Remaining Scenario Outlines are not test cases yet. They are placeholders that flag areas needing coverage. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/) to generate full test cases from them. +| Remaining Scenario Outlines are not test cases yet. They are placeholders Atto created to flag areas that need coverage. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/) to generate full test cases from them. --- @@ -96,8 +96,8 @@ The main area switches to the session detail view with three tabs: **Tests**, ** From here you can: -- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/). -- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/). -- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/). +- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/). +- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/). +- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/). --- diff --git a/src/pages/docs/arcus/qi-home/ad-hoc/write-effective-prompts.md b/src/pages/docs/test-management/qi-home/ad-hoc/write-effective-prompts.md similarity index 89% rename from src/pages/docs/arcus/qi-home/ad-hoc/write-effective-prompts.md rename to src/pages/docs/test-management/qi-home/ad-hoc/write-effective-prompts.md index a0c7ce0..e27cfab 100644 --- a/src/pages/docs/arcus/qi-home/ad-hoc/write-effective-prompts.md +++ b/src/pages/docs/test-management/qi-home/ad-hoc/write-effective-prompts.md @@ -1,8 +1,8 @@ --- title: 'Write Effective Prompts' page_title: 'Write Effective Prompts' -metadesc: 'The quality of your prompt determines the quality of the Generator Agent output. Learn how to write clear, specific prompts that generate accurate, relevant test cases.' -description: 'Learn how to write effective prompts that generate accurate test cases with the Generator Agent.' +metadesc: 'The quality of your prompt determines the quality of Atto output. Learn how to write clear, specific prompts that generate accurate, relevant test cases.' +description: 'Learn how to write effective prompts that generate accurate test cases with Atto.' noindex: false order: 13.22 page_id: 'qi-home-write-effective-prompts' @@ -32,11 +32,11 @@ contextual_links:
-**The quality of your prompt determines the quality of the Generator Agent's output.** +**The quality of your prompt determines the quality of Atto's output.** --- -Prompts are how you tell the Generator Agent what to test. A well-written prompt gives it the goal, the context, and the constraints it needs to generate test cases that are accurate and relevant. Vague prompts produce generic test cases. Specific prompts produce test cases that match your feature. +Prompts are how you tell Atto what to test. A well-written prompt gives Atto the goal, the context, and the constraints it needs to generate test cases that are accurate and relevant. Vague prompts produce generic test cases. Specific prompts produce test cases that match your feature. This article covers how to write prompts that get you the right test cases the first time. @@ -45,7 +45,7 @@ This article covers how to write prompts that get you the right test cases the f > ## **Prerequisites** > > Before you begin, ensure that: -> - The Playground is open with context attached. See [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/) if you have not done this yet. +> - The Playground is open with context attached. See [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/) if you have not done this yet. --- @@ -81,7 +81,7 @@ You do not need to use all five elements every time. Start with WHAT and add the Before clicking **Generate with AI**, run through this checklist: -- **Goal**: Have you stated what you want the Generator Agent to generate? +- **Goal**: Have you stated what you want Atto to generate? - **Context**: Have you described the feature, flow, or user story? - **Inputs**: Have you attached the relevant stories, files, and designs? - **Edge Cases**: Have you called out tricky or high-risk conditions to include? @@ -197,11 +197,11 @@ Expected Outcomes: ## **Tips for Better Prompts** -- **Use personas.** "As a mobile user on a slow connection…" gives the Generator Agent relevant constraints that affect test design. +- **Use personas.** "As a mobile user on a slow connection…" gives Atto relevant constraints that affect test design. - **Reference your context.** If you have attached Jira stories, mention the story IDs in the prompt. For example: "Generate test cases for AUTOM-3 and AUTOM-4, focusing on the OAuth login flow." - **Call out what matters most.** If security, performance, or accessibility is a priority for this feature, say so explicitly. - **Iterate.** If the first generation does not cover everything you need, open the Playground and refine the prompt with additional context or more specific constraints. -When your prompt is ready, see [Generate Test Cases](https://testsigma.com/docs/arcus/qi-home/ad-hoc/generate-test-cases/). +When your prompt is ready, see [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/ad-hoc/generate-test-cases/). --- diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md similarity index 72% rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md index cb07217..8014ee8 100644 --- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md +++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md @@ -1,7 +1,7 @@ --- title: 'Learn Test Case Live (Cloud)' page_title: 'Learn Test Case Live (Cloud)' -metadesc: 'Let the Runner Agent walk through your test case on a cloud browser on Testsigma Lab and generate automated steps for you — no scripts required.' +metadesc: 'Let Atto walk through your test case on a cloud browser on Testsigma Lab and generate automated steps for you — no scripts required.' description: 'Learn how to run Agentic Learning on a cloud browser to automate a test case.' noindex: false order: 13.31 @@ -29,7 +29,7 @@ contextual_links:
-**Let the Runner Agent walk through your test case on a cloud browser and generate automated steps for you.** +**Let Atto walk through your test case on a cloud browser and generate automated steps for you.** --- @@ -63,15 +63,15 @@ Use Cloud when you do not want to set up anything locally. Testsigma Lab provide ## **During the Learning Session** -When the browser tab opens, the Runner Agent introduces itself and displays the test case steps in the Agentic Learning panel. +When the browser tab opens, Atto introduces itself and displays the test case steps in the Agentic Learning panel. -The Runner Agent begins walking through each step on your live application. As each step is validated, it is marked with a checkmark in the panel. +Atto begins walking through each step on your live application. As each step is validated, it is marked with a checkmark in the panel. **What you can do during learning:** -- Watch the Runner Agent execute each step in the browser. -- If it gets stuck or waits for your input, a banner appears: "Atto is waiting on your input to continue learning." Click **Go to Session** to provide guidance. See [Live Learning Controls](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls/). -- Click **Start Learning Live App** to begin interactive learning if it has not started automatically. +- Watch Atto execute each step in the browser. +- If Atto gets stuck or waits for your input, a banner appears: "Atto is waiting on your input to continue learning." Click **Go to Session** to provide guidance. See [Live Learning Controls](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls/). +- Click **Start Learning Live App** to begin interactive learning if Atto has not started automatically. --- @@ -104,8 +104,8 @@ While Agentic Learning is running, the test case shows a status on the sprint or | Status | What it means | | :--- | :--- | -| **Agentic Learning in progress** | Learning is running. The Runner Agent is walking through the steps. | -| **Atto needs user's input** | The Runner Agent has paused and is waiting for you to provide guidance in the browser session. | +| **Agentic Learning in progress** | Learning is running. Atto is walking through the steps. | +| **Atto needs user's input** | Atto has paused and is waiting for you to provide guidance in the browser session. | | **Learn and Automated** | Learning completed and automated steps were saved successfully. | --- diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local.md similarity index 82% rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local.md rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local.md index fc1a23c..c5c2398 100644 --- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local.md +++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local.md @@ -33,7 +33,7 @@ contextual_links: --- -Agentic Learning (Local) works the same way as Cloud — the Runner Agent walks through your test case on a live application and generates automated steps — but the browser or device runs on your local machine instead of Testsigma Lab. Use Local when your application is not publicly accessible, when you need to test against a local build, or when you are automating mobile test cases on a physical device or emulator. +Agentic Learning (Local) works the same way as Cloud — Atto walks through your test case on a live application and generates automated steps — but the browser or device runs on your local machine instead of Testsigma Lab. Use Local when your application is not publicly accessible, when you need to test against a local build, or when you are automating mobile test cases on a physical device or emulator. Local execution requires Testsigma Terminal to be running on your desktop. @@ -70,7 +70,7 @@ Local execution requires Testsigma Terminal to be running on your desktop. -Once Terminal is running and connected, the learning session opens in a browser on your machine. The Agentic Learning panel behavior is the same as Cloud. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) for the learning session flow, generating automated steps, and saving to your library. +Once Terminal is running and connected, the learning session opens in a browser on your machine. The Agentic Learning panel behavior is the same as Cloud. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) for the learning session flow, generating automated steps, and saving to your library. --- @@ -128,8 +128,8 @@ The iOS flow uses the same dialog as Android Local. Select **iOS** as the Applic ## **During the Learning Session** -The Agentic Learning panel behavior is the same for Local as it is for Cloud. The Runner Agent walks through the steps, marks each one with a checkmark, and waits for your input if it gets stuck. See [Live Learning Controls](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls/) for controls available during the session. +The Agentic Learning panel behavior is the same for Local as it is for Cloud. Atto walks through the steps, marks each one with a checkmark, and waits for your input if it gets stuck. See [Live Learning Controls](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls/) for controls available during the session. -After learning completes, generate and save automated steps following the same steps as Cloud. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/). +After learning completes, generate and save automated steps following the same steps as Cloud. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/). --- diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls.md similarity index 62% rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls.md rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls.md index 444f39d..9e66347 100644 --- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls.md +++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls.md @@ -1,7 +1,7 @@ --- title: 'Live Learning Controls' page_title: 'Live Learning Controls' -metadesc: 'The controls available to you during an Agentic Learning session — panel controls, session states, providing input when the Runner Agent gets stuck, and re-learning a test case.' +metadesc: 'The controls available to you during an Agentic Learning session — panel controls, session states, providing input when Atto gets stuck, and re-learning a test case.' description: 'Reference for the controls and session states available during an Agentic Learning session.' noindex: false order: 13.33 @@ -17,8 +17,8 @@ contextual_links: name: 'Session States' url: '#session-states' - type: link - name: 'Providing Input When the Runner Agent Gets Stuck' - url: '#providing-input-when-the-runner-agent-gets-stuck' + name: 'Providing Input When Atto Gets Stuck' + url: '#providing-input-when-atto-gets-stuck' - type: link name: 'Re-Learning a Test Case' url: '#re-learning-a-test-case' @@ -40,9 +40,9 @@ The Agentic Learning panel appears alongside the browser during a live learning | Control | What it does | | :--- | :--- | -| **Start Learning Live App** | Start the learning session. The Runner Agent begins walking through the test case steps on the live application. This button appears when the session is ready but has not yet started. | -| **Record Step** | Manually records the current state of the browser or device as a step. Use this if the Runner Agent misses a step or if you want to add a step that is not in the original test case. | -| **Pause** | Pauses the Runner Agent's execution. It stops walking through steps and waits for you to resume. | +| **Start Learning Live App** | Start the learning session. Atto begins walking through the test case steps on the live application. This button appears when the session is ready but has not yet started. | +| **Record Step** | Manually records the current state of the browser or device as a step. Use this if Atto misses a step or if you want to add a step that is not in the original test case. | +| **Pause** | Pauses Atto's execution. Atto stops walking through steps and waits for you to resume. | | **Resume** | Resumes execution after a pause. | | **Stop** | Ends the learning session without generating automated steps. | @@ -56,24 +56,24 @@ The panel and the test case view reflect the current state of the learning sessi | State | What it means | What you see | | :--- | :--- | :--- | -| **Learning** | The Runner Agent is actively walking through steps. | Steps list with spinner on the current step. "Learning..." status in the panel. | -| **Atto needs user's input** | The Runner Agent has reached a step it cannot complete without guidance. The session is paused. | Yellow banner on the test case view: "Atto is waiting on your input to continue learning." **Go to Session** button. | -| **Completed** | The Runner Agent has walked through all steps. | Steps list with checkmarks. "Generate Automated Steps", "Save to Library", and "Reject" buttons appear. | -| **Generation Failed** | The Runner Agent could not generate automated steps from the learned session. | "Generation Failed" error with an **Edit** option. | +| **Learning** | Atto is actively walking through steps. | Steps list with spinner on the current step. "Learning..." status in the panel. | +| **Atto needs user's input** | Atto has reached a step it cannot complete without guidance. The session is paused. | Yellow banner on the test case view: "Atto is waiting on your input to continue learning." **Go to Session** button. | +| **Completed** | Atto has walked through all steps. | Steps list with checkmarks. "Generate Automated Steps", "Save to Library", and "Reject" buttons appear. | +| **Generation Failed** | Atto could not generate automated steps from the learned session. | "Generation Failed" error with an **Edit** option. | --- -## **Providing Input When the Runner Agent Gets Stuck** +## **Providing Input When Atto Gets Stuck** -When the Runner Agent needs your input, a banner appears on the test case view. +When Atto needs your input, a banner appears on the test case view in Atto. 1. On the test case view, click **Go to Session** in the banner. The browser tab with the learning session opens. -2. In the browser, complete the action the Runner Agent could not perform. For example, if it stopped at a CAPTCHA or a multi-factor authentication step, complete it manually. +2. In the browser, complete the action Atto could not perform. For example, if Atto stopped at a CAPTCHA or a multi-factor authentication step, complete it manually. -3. After completing the action, the Runner Agent resumes walking through the remaining steps automatically. +3. After completing the action, Atto resumes walking through the remaining steps automatically. [[info | **NOTE**:]] | If you close the browser tab without completing the required action, the learning session ends and you will need to start a new session. diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md similarity index 89% rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md index 85aec54..02b763e 100644 --- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md +++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md @@ -36,7 +36,7 @@ This is the final step in the Agentic Learning workflow. The test case moves fro > ## **Prerequisites** > > Before you begin, ensure that: -> - Agentic Learning has completed and automated steps have been generated. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) or [Learn Test Case Live (Local)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local/). +> - Agentic Learning has completed and automated steps have been generated. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) or [Learn Test Case Live (Local)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local/). --- @@ -56,7 +56,7 @@ This is the final step in the Agentic Learning workflow. The test case moves fro -For the full Copilot execution experience — including controls, step switching, and saving results — see [Execute Test Case in Cloud](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud/). +For the full Copilot execution experience — including controls, step switching, and saving results — see [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/). --- diff --git a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud.md b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud.md similarity index 93% rename from src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud.md rename to src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud.md index e5967ce..52133e5 100644 --- a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud.md +++ b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud.md @@ -37,7 +37,7 @@ Copilot opens a cloud browser on Testsigma Lab and executes your test case steps > ## **Prerequisites** > > Before you begin, ensure that: -> - You have a test case with automated steps saved in your library. Automated steps are required for Copilot execution. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/). +> - You have a test case with automated steps saved in your library. Automated steps are required for Copilot execution. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/). > - Your application is accessible from a cloud environment. --- @@ -80,7 +80,7 @@ When the browser is ready, the Copilot panel opens alongside it. Steps execute i -For the full list of controls available during execution, see [Execution Controls in Copilot](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot/). +For the full list of controls available during execution, see [Execution Controls in Copilot](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/). --- diff --git a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-local.md b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local.md similarity index 94% rename from src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-local.md rename to src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local.md index ca9bf4e..6d7bb09 100644 --- a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-local.md +++ b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local.md @@ -67,7 +67,7 @@ Local execution requires Testsigma Terminal to be running on your desktop. If Testsigma Terminal is not running, a prompt appears. Start Terminal and return to launch the session. -The Copilot panel opens in a browser on your machine. The execution flow is the same as Cloud. See [Execution Controls in Copilot](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot/). +The Copilot panel opens in a browser on your machine. The execution flow is the same as Cloud. See [Execution Controls in Copilot](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/). --- @@ -116,7 +116,7 @@ The iOS flow uses the same Run with Copilot dialog as Android Local. ## **Complete the Session** -The completion flow for Local is the same as Cloud. When execution finishes, save your results and end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud/) for the save and end steps. +The completion flow for Local is the same as Cloud. When execution finishes, save your results and end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/) for the save and end steps. [[info | **NOTE**:]] | For Local execution, there is no cloud VM to release. The session simply closes when you end it. diff --git a/src/pages/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot.md b/src/pages/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot.md similarity index 100% rename from src/pages/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot.md rename to src/pages/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot.md diff --git a/src/pages/docs/arcus/qi-home/plugins/connect-claude-code.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md similarity index 51% rename from src/pages/docs/arcus/qi-home/plugins/connect-claude-code.md rename to src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md index 36270da..b1ed915 100644 --- a/src/pages/docs/arcus/qi-home/plugins/connect-claude-code.md +++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md @@ -10,12 +10,6 @@ warning: false contextual_links: - type: section name: 'Contents' - - type: link - name: 'Overview' - url: '#overview' - - type: link - name: 'Why Arcus' - url: '#why-arcus' - type: link name: 'Prerequisites' url: '#prerequisites' @@ -25,18 +19,12 @@ contextual_links: - type: link name: 'Log In and Connect Your Project' url: '#log-in-and-connect-your-project' - - type: link - name: 'How the Quality Intelligence Loop Works' - url: '#how-the-quality-intelligence-loop-works' - type: link name: 'Map Your Context to a Sprint' url: '#map-your-context-to-a-sprint' - type: link name: 'Push Your Context' url: '#push-your-context' - - type: link - name: "Who It's For" - url: '#who-its-for' - type: link name: 'Commands Reference' url: '#commands-reference' @@ -47,28 +35,9 @@ contextual_links: **Install the Arcus plugin for Claude Code so that your coding context is captured and sent to QI Home for test generation.** -The plugin hooks into each stage of a Claude Code session and captures it as structured events: your prompts, the tools Claude runs, the files it reads and writes, and subagent boundaries. When you are done, you push the captured context to QI Home with a single command. QA maps the context to the right sprint, and the Generator Agent creates test cases from your development activity. +The plugin hooks into each stage of a Claude Code session and captures it as structured events: your prompts, the tools Claude runs, the files it reads and writes, and subagent boundaries. When you are done, you push the captured context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases from your development activity. ---- - -## **Overview** - -At a glance, Arcus: - -* **Generates test cases from what you actually built**, with no manual authoring. -* **Finds the gaps** between what changed and what's tested, with a reason for each. -* **Plans and runs** those tests across Smoke, Feature, Regression, and Deep Regression suites. -* **Decides with a single Release Readiness score** and a GO / CONDITIONAL GO / NO-GO verdict. - ---- - -## **Why Arcus** - -AI coding agents have made it trivial to ship large changes fast. The bottleneck has moved: it's no longer writing the code, it's trusting it. Teams using Claude Code routinely merge features, refactors, and fixes faster than their QA process can keep up, and the gap between "the code is written" and "we know it works" keeps widening. - -The traditional answer, writing tests by hand after the fact, is slow, always behind, and never tells you with confidence how much of what you just built is actually covered. - -Arcus closes that gap by treating your Claude Code session as the source of truth for what changed. It captures the session automatically, turns it into tests you review rather than write, keeps a live map of what's covered, and rolls everything up into an evidence-backed release signal. +For how mapped context becomes test cases, coverage, and a release signal, see [Overview: Developer Context Mapping](https://testsigma.com/docs/test-management/qi-home/context-mapping/). --- @@ -111,47 +80,6 @@ claude plugin install arcus@testsigma --- -## **How the Quality Intelligence Loop Works** - -Once you push a session, Arcus runs that context through the Quality Intelligence loop: a continuous cycle that keeps your tests and your release signal in sync with the code. - -**1. Generate** - -The **Generator Agent** reads the captured session, code changes, the prompts you gave Claude, the tools it ran, and drafts test cases for the behavior you actually built. You review each one and accept, edit, or reject it; accepted cases join your test suite. Nothing is auto-merged behind your back. - -**2. Find gaps** - -The **Coverage Agent** answers the question manual QA can never keep up with: what did we change that we haven't tested yet? It re-runs whenever context changes, a new Claude Code session or a pull request, or whenever you accept a case, and surfaces untested areas with a reason for each gap. - -**3. Plan and execute** - -Accepted cases roll up into auto-generated test plans, nested by scope: - -| Plan | Scope | -|------|-------| -| Smoke | Critical-path sanity checks, fast feedback | -| Feature | Cases tied to the current feature or session | -| Regression | Existing behavior that shouldn't have broken | -| Deep Regression | Broad, exhaustive run across the product | - -The **Runner Agent** executes these plans, automated runs against your configured machines and environments, or manual runs for cases that still need a human. See [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) for how the nested plan hierarchy works. - -**4. Measure and decide** - -Execution results feed the Quality Intelligence metrics, which build on each other up to a single verdict: - -| Metric | Question It Answers | -|--------|----------------------| -| Coverage | Of what should be tested, how much is approved and tested? | -| Pass Rate | Of the tests that ran, how many passed? | -| Confidence | How trustworthy are the results? | -| Release Readiness | On a 0 to 100 scale, how shippable is this sprint? | -| Release Gate | The verdict: GO / CONDITIONAL GO / NO-GO | - -See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for the full formulas and thresholds behind each metric. - ---- - ## **Map Your Context to a Sprint** Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. Replace **<ticket-key>** with the Jira ticket ID for the work you are doing. @@ -163,7 +91,7 @@ Run **/arcus:map <ticket-key>** at any point before pushing to link your c Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint, and the test cases generated from it trace back to that ticket. QA does not need to route it manually from Unmapped Context. [[info | **NOTE**:]] -| You can push without mapping. The context lands in Unmapped Context and waits there with its generated tests until you resolve it, either to a sprint or to an Ad-Hoc session. See [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/). +| You can push without mapping. The context lands in Unmapped Context and waits there with its generated tests until you resolve it, either to a sprint or to an Ad-Hoc session. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/). --- @@ -175,14 +103,6 @@ The context appears in QI Home under **Unmapped Context** (if you did not run ** --- -## **Who It's For** - -* **Developers** shipping with Claude Code who want their changes tested without breaking flow to write tests by hand. -* **QA and test engineers** who want generated cases to review and refine, plus a coverage map that updates itself instead of a stale spreadsheet. -* **Engineering leads and release managers** who need an objective, evidence-backed answer to "is this sprint safe to ship?" rather than a status-meeting guess. - ---- - ## **Commands Reference** | Command | What it does | @@ -200,9 +120,9 @@ The context appears in QI Home under **Unmapped Context** (if you did not run ** ## **If You Also Use GitHub** -If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Arcus connects the two automatically: +If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically: -* **Context still unmapped**: Arcus converts it into a GitHub context. The Claude Code context and the pull request are unified as a single entry in Unmapped Context. +* **Context still unmapped**: Atto converts it into a GitHub context. The Claude Code context and the pull request are unified as a single entry in Unmapped Context. * **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. --- diff --git a/src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md new file mode 100644 index 0000000..73f0a99 --- /dev/null +++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md @@ -0,0 +1,117 @@ +--- +title: 'Connect Codex' +page_title: 'Connect Codex' +metadesc: 'How to install and connect the Arcus plugin for Codex so your coding context is captured and sent to QI Home for test generation.' +description: 'How to install and connect the Arcus plugin for Codex so your coding context is captured and sent to QI Home for test generation.' +noindex: false +order: 13.45 +page_id: 'qi-home-connect-codex' +warning: false +contextual_links: + - type: section + name: 'Contents' + - type: link + name: 'Prerequisites' + url: '#prerequisites' + - type: link + name: 'Install the Plugin' + url: '#install-the-plugin' + - type: link + name: 'Log In and Connect Your Project' + url: '#log-in-and-connect-your-project' + - type: link + name: 'Map Your Context to a Sprint' + url: '#map-your-context-to-a-sprint' + - type: link + name: 'Push Your Context' + url: '#push-your-context' + - type: link + name: 'Commands Reference' + url: '#commands-reference' + - type: link + name: 'If You Also Use GitHub' + url: '#if-you-also-use-github' +--- + +**Install the Arcus plugin for Codex so that your coding context is captured and sent to QI Home for test generation.** + +When the plugin is installed and connected to a project, Atto captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases based on your development activity. + +--- + +> ## **Prerequisites** +> +> Before you begin, ensure that: +> * Codex is installed. +> * You have an active project in Arcus by Testsigma. + +--- + +## **Install the Plugin** + +[[info | **NOTE**:]] +| The install command for the Codex Arcus plugin is pending confirmation from the dev team. This step will be updated before publication. + +--- + +## **Log In and Connect Your Project** + +1. In Codex, run **/arcus:login**. + +2. Complete the login flow in the browser. Return to Codex when prompted. + +3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**. + +4. Start coding. The plugin begins capturing your context in the background. + +[[info | **NOTE**:]] +| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload. + +--- + +## **Map Your Context to a Sprint** + +Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. + +``` +/arcus:map PROJ-123 +``` + +Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint. QA does not need to route it manually from Unmapped Context. + +[[info | **NOTE**:]] +| You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/). + +--- + +## **Push Your Context** + +1. When you are done, run **/arcus:push** to upload the captured context to QI Home. + +The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did). + +--- + +## **Commands Reference** + +| Command | What it does | +|---------|-------------| +| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it | +| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation | +| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine | +| /arcus:project | Shows your Arcus projects and sets one as the active project | +| /arcus:map | Links a ticket key to the current context so it routes to the right sprint | +| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them | +| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them | +| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped | + +--- + +## **If You Also Use GitHub** + +If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically: + +* **Context still unmapped**: Atto converts it into a GitHub context. The Codex context and the pull request are unified as a single entry in Unmapped Context. +* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. + +--- diff --git a/src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md new file mode 100644 index 0000000..1c2f865 --- /dev/null +++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md @@ -0,0 +1,116 @@ +--- +title: 'Connect Cursor' +page_title: 'Connect Cursor' +metadesc: 'How to install and connect the Arcus plugin for Cursor so your coding context is captured and sent to QI Home for test generation.' +description: 'How to install and connect the Arcus plugin for Cursor so your coding context is captured and sent to QI Home for test generation.' +noindex: false +order: 13.43 +page_id: 'qi-home-connect-cursor' +warning: false +contextual_links: + - type: section + name: 'Contents' + - type: link + name: 'Prerequisites' + url: '#prerequisites' + - type: link + name: 'Install the Plugin' + url: '#install-the-plugin' + - type: link + name: 'Log In and Connect Your Project' + url: '#log-in-and-connect-your-project' + - type: link + name: 'Map Your Context to a Sprint' + url: '#map-your-context-to-a-sprint' + - type: link + name: 'Push Your Context' + url: '#push-your-context' + - type: link + name: 'Commands Reference' + url: '#commands-reference' + - type: link + name: 'If You Also Use GitHub' + url: '#if-you-also-use-github' +--- + +**Install the Arcus plugin for Cursor so that your coding context is captured and sent to QI Home for test generation.** + +When the plugin is installed and connected to a project, Atto captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases based on your development activity. + +--- + +> ## **Prerequisites** +> +> Before you begin, ensure that: +> * Cursor is installed. +> * You have an active project in Arcus by Testsigma. + +--- + +## **Install the Plugin** + +The install Arcus plugin from Cursor marketplace. + +--- + +## **Log In and Connect Your Project** + +1. In Cursor, run **/arcus:login**. + +2. Complete the login flow in the browser. Return to Cursor when prompted. + +3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**. + +4. Start coding. The plugin begins capturing your context in the background. + +[[info | **NOTE**:]] +| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload. + +--- + +## **Map Your Context to a Sprint** + +Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. + +``` +/arcus:map PROJ-123 +``` + +Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint. QA does not need to route it manually from Unmapped Context. + +[[info | **NOTE**:]] +| You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/). + +--- + +## **Push Your Context** + +1. When you are done, run **/arcus:push** to upload the captured context to QI Home. + +The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did). + +--- + +## **Commands Reference** + +| Command | What it does | +|---------|-------------| +| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it | +| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation | +| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine | +| /arcus:project | Shows your Arcus projects and sets one as the active project | +| /arcus:map | Links a ticket key to the current context so it routes to the right sprint | +| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them | +| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them | +| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped | + +--- + +## **If You Also Use GitHub** + +If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically: + +* **Context still unmapped**: Atto converts it into a GitHub context. The Cursor context and the pull request are unified as a single entry in Unmapped Context. +* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. + +--- diff --git a/src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md new file mode 100644 index 0000000..9018085 --- /dev/null +++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md @@ -0,0 +1,120 @@ +--- +title: 'Connect GitHub Copilot' +page_title: 'Connect GitHub Copilot' +metadesc: 'How to install and connect the Arcus plugin for GitHub Copilot so your coding context is captured and sent to QI Home for test generation.' +description: 'How to install and connect the Arcus plugin for GitHub Copilot so your coding context is captured and sent to QI Home for test generation.' +noindex: false +order: 13.44 +page_id: 'qi-home-connect-github-copilot' +warning: false +contextual_links: + - type: section + name: 'Contents' + - type: link + name: 'Prerequisites' + url: '#prerequisites' + - type: link + name: 'Install the Plugin' + url: '#install-the-plugin' + - type: link + name: 'Log In and Connect Your Project' + url: '#log-in-and-connect-your-project' + - type: link + name: 'Map Your Context to a Sprint' + url: '#map-your-context-to-a-sprint' + - type: link + name: 'Push Your Context' + url: '#push-your-context' + - type: link + name: 'Commands Reference' + url: '#commands-reference' + - type: link + name: 'If You Also Use GitHub' + url: '#if-you-also-use-github' +--- + +**Install the Arcus plugin for GitHub Copilot so that your coding context is captured and sent to QI Home for test generation.** + +When the plugin is installed and connected to a project, Atto captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases based on your development activity. + +[[info | **NOTE**:]] +| This doc refers to the GitHub Copilot CLI plugin for Arcus, not Testsigma Copilot (the test execution feature). They are separate tools. + +--- + +> ## **Prerequisites** +> +> Before you begin, ensure that: +> * GitHub Copilot is installed. +> * You have an active project in Arcus by Testsigma. + +--- + +## **Install the Plugin** + +[[info | **NOTE**:]] +| The install command for the GitHub Copilot Arcus plugin is pending confirmation from the dev team. This step will be updated before publication. + +--- + +## **Log In and Connect Your Project** + +1. In GitHub Copilot, run **/arcus:login**. + +2. Complete the login flow in the browser. Return to GitHub Copilot when prompted. + +3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**. + +4. Start coding. The plugin begins capturing your context in the background. + +[[info | **NOTE**:]] +| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload. + +--- + +## **Map Your Context to a Sprint** + +Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. + +``` +/arcus:map PROJ-123 +``` + +Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint. QA does not need to route it manually from Unmapped Context. + +[[info | **NOTE**:]] +| You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/). + +--- + +## **Push Your Context** + +1. When you are done, run **/arcus:push** to upload the captured context to QI Home. + +The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did). + +--- + +## **Commands Reference** + +| Command | What it does | +|---------|-------------| +| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it | +| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation | +| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine | +| /arcus:project | Shows your Arcus projects and sets one as the active project | +| /arcus:map | Links a ticket key to the current context so it routes to the right sprint | +| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them | +| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them | +| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped | + +--- + +## **If You Also Use GitHub** + +If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically: + +* **Context still unmapped**: Atto converts it into a GitHub context. The GitHub Copilot context and the pull request are unified as a single entry in Unmapped Context. +* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. + +--- diff --git a/src/pages/docs/arcus/qi-home/plugins/connect-github.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-github.md similarity index 84% rename from src/pages/docs/arcus/qi-home/plugins/connect-github.md rename to src/pages/docs/test-management/qi-home/context-mapping/connect-github.md index 1444ae9..7eb4452 100644 --- a/src/pages/docs/arcus/qi-home/plugins/connect-github.md +++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-github.md @@ -29,7 +29,7 @@ contextual_links: **Connect the Arcus GitHub App to your repositories so that every pull request your team raises flows into QI Home for test generation.** -When the Arcus GitHub App is installed and connected to a project, the Coverage Agent detects every pull request raised in the connected repositories and surfaces it in the Unmapped Context view. QA maps each PR to a sprint or Ad-Hoc session, and the Generator Agent creates test cases based on the code changes. Developers do not change how they work. +When the Arcus GitHub App is installed and connected to a project, Atto detects every pull request raised in the connected repositories and surfaces it in the Unmapped Context view. QA maps each PR to a sprint or Ad-Hoc session, and Atto generates test cases based on the code changes. Developers do not change how they work. --- @@ -61,7 +61,7 @@ The GitHub App is now installed. All pull requests raised in the connected repos ## **Connect Jira for Auto-Mapping** -If your project is connected to Jira, the Coverage Agent can auto-map pull requests to the correct sprint when the PR title or description contains a Jira ticket ID. +If your project is connected to Jira, Atto can auto-map pull requests to the correct sprint when the PR title or description contains a Jira ticket ID. 1. In Arcus, go to **Settings > Integrations**. @@ -71,7 +71,7 @@ If your project is connected to Jira, the Coverage Agent can auto-map pull reque Once Jira is connected, any PR with a ticket ID such as **PROJ-123** in the title or description is routed directly to the sprint that contains that story. The PR does not land in Unmapped Context. QA does not need to map it manually. [[info | **NOTE**:]] -| If a PR does not contain a Jira ticket ID, it lands in Unmapped Context regardless of whether Jira is connected. QA maps it manually from there. See [Map GitHub Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-github/). +| If a PR does not contain a Jira ticket ID, it lands in Unmapped Context regardless of whether Jira is connected. QA maps it manually from there. See [Map GitHub Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/). --- @@ -89,7 +89,7 @@ Once Jira is connected, any PR with a ticket ID such as **PROJ-123** in the titl ## **What Happens Next** -After a PR appears in Unmapped Context, a QA team member maps it to a sprint or Ad-Hoc session. The Generator Agent then creates test cases based on the PR diff. +After a PR appears in Unmapped Context, a QA team member maps it to a sprint or Ad-Hoc session. Atto then generates test cases based on the PR diff. If your developers also use a CLI tool (Claude Code, Cursor, GitHub Copilot, or Codex), their context unifies with the PR automatically when it is raised. diff --git a/src/pages/docs/arcus/qi-home/plugins/map-developer-context.md b/src/pages/docs/test-management/qi-home/context-mapping/map-developer-context.md similarity index 71% rename from src/pages/docs/arcus/qi-home/plugins/map-developer-context.md rename to src/pages/docs/test-management/qi-home/context-mapping/map-developer-context.md index 4a04dde..9701f07 100644 --- a/src/pages/docs/arcus/qi-home/plugins/map-developer-context.md +++ b/src/pages/docs/test-management/qi-home/context-mapping/map-developer-context.md @@ -1,8 +1,8 @@ --- title: 'Map Developer Context' page_title: 'Map Developer Context' -metadesc: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on development activity.' -description: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on development activity.' +metadesc: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on development activity.' +description: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on development activity.' noindex: false order: 13.47 page_id: 'qi-home-map-developer-context' @@ -36,11 +36,11 @@ contextual_links: url: '#view-mapped-context' --- -**Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on development activity.** +**Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on development activity.** -When developers work in Claude Code, Cursor, GitHub Copilot, or Codex with the Arcus plugin installed and push context using `/arcus:push`, the Coverage Agent surfaces it in the **Unmapped Context** view in QI Home. Each context entry includes an AI-generated suggestion for which module and sprint it belongs to. Once mapped, the Generator Agent creates test cases based on the development activity captured in that context. +When developers work in Claude Code, Cursor, GitHub Copilot, or Codex with the Arcus plugin installed and push context using `/arcus:push`, Atto surfaces it in the **Unmapped Context** view in QI Home. Each context entry includes an AI-generated suggestion for which module and sprint it belongs to. Once mapped, Atto generates test cases based on the development activity captured in that context. -For plugin setup on the developer side, see [Connect Claude Code](https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/). +For plugin setup on the developer side, see [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/). --- @@ -65,9 +65,9 @@ Each CLI context entry shows: * **Context title** * **Author** — the developer whose activity produced this context * **Service** — the module or service area this context relates to -* **Tests explored** — areas the Coverage Agent identified in this context +* **Tests explored** — areas Atto identified in this context * **Time** the context was pushed -* **AI Suggestion** — the module and sprint the Coverage Agent recommends +* **AI Suggestion** — the module and sprint Atto recommends [[info | **NOTE**:]] | The mapping flow is identical for Claude Code, Cursor, GitHub Copilot, and Codex context. The steps below apply to all four tools. @@ -88,7 +88,7 @@ Each CLI context entry shows: 6. Review the **What happens next** message and click **Map**. -The Generator Agent triggers test generation for the selected sprint. +Atto triggers test generation for the selected sprint. --- @@ -124,9 +124,9 @@ If a context entry is not relevant to your test coverage, click **Dismiss**. It ## **When a Developer Also Uses GitHub** -If your team has GitHub connected and a developer raises a pull request for the same work they captured in CLI context, the Coverage Agent handles the overlap automatically: +If your team has GitHub connected and a developer raises a pull request for the same work they captured in CLI context, Atto handles the overlap automatically: -* **Context still unmapped**: The Coverage Agent converts it into a GitHub context. The CLI context and the pull request unify as a single entry. You map it as a GitHub PR, not as separate CLI context. +* **Context still unmapped**: Atto converts it into a GitHub context. The CLI context and the pull request unify as a single entry. You map it as a GitHub PR, not as separate CLI context. * **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. diff --git a/src/pages/docs/arcus/qi-home/plugins/map-github.md b/src/pages/docs/test-management/qi-home/context-mapping/map-github.md similarity index 79% rename from src/pages/docs/arcus/qi-home/plugins/map-github.md rename to src/pages/docs/test-management/qi-home/context-mapping/map-github.md index 4ceabc6..223bea9 100644 --- a/src/pages/docs/arcus/qi-home/plugins/map-github.md +++ b/src/pages/docs/test-management/qi-home/context-mapping/map-github.md @@ -1,7 +1,7 @@ --- title: 'Map GitHub Context' page_title: 'Map GitHub Context' -metadesc: 'Map GitHub pull requests to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on code changes.' +metadesc: 'Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.' description: 'Learn how to map GitHub pull requests to sprints or Ad-Hoc sessions for coverage tracking.' noindex: false order: 13.46 @@ -30,15 +30,15 @@ contextual_links: url: '#view-mapped-context' --- -**Map GitHub pull requests to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on code changes.** +**Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.** -For GitHub App setup on the developer side, see [Connect GitHub](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/). +For GitHub App setup on the developer side, see [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/). --- -When your developers open or update pull requests in GitHub, the Coverage Agent detects them and shows them in the **Unmapped Context** view in QI Home. Each pull request appears with an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks. +When your developers open or update pull requests in GitHub, Atto detects them and shows them in the **Unmapped Context** view in QI Home. Each pull request appears with an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks. -Once mapped, the Generator Agent creates new test cases or updates existing ones based on the code changes in that pull request. +Once mapped, Atto generates new test cases or updates existing ones based on the code changes in that pull request. --- @@ -65,7 +65,7 @@ Each GitHub PR entry shows: - **Author**: The developer who opened the PR. - **Lines changed**: Lines added and removed. - **Time**: When the PR was opened or last updated. -- **AI Suggestion**: The module the Coverage Agent recommends mapping this PR to. +- **AI Suggestion**: The module Atto recommends mapping this PR to. --- @@ -85,7 +85,7 @@ Each GitHub PR entry shows: 7. Click **Map**. -The Generator Agent triggers test generation for the selected sprint. New test cases are generated or existing ones are updated based on the PR's changes. +Atto triggers test generation for the selected sprint. New test cases are generated or existing ones are updated based on the PR's changes. --- diff --git a/src/pages/docs/arcus/qi-home/plugins/overview.md b/src/pages/docs/test-management/qi-home/context-mapping/overview.md similarity index 62% rename from src/pages/docs/arcus/qi-home/plugins/overview.md rename to src/pages/docs/test-management/qi-home/context-mapping/overview.md index 496e587..5acc445 100644 --- a/src/pages/docs/arcus/qi-home/plugins/overview.md +++ b/src/pages/docs/test-management/qi-home/context-mapping/overview.md @@ -23,8 +23,8 @@ contextual_links: name: 'The Mapping Model' url: '#the-mapping-model' - type: link - name: 'What Gets Generated After Mapping' - url: '#what-gets-generated-after-mapping' + name: 'What Atto Generates After Mapping' + url: '#what-atto-generates-after-mapping' - type: link name: 'When CLI Context and a Pull Request Overlap' url: '#when-cli-context-and-a-pull-request-overlap' @@ -36,7 +36,7 @@ contextual_links: url: '#prerequisite' --- -Developer Context Mapping connects the tools your developers already use to the Quality Intelligence loop in Arcus. When a developer opens a pull request or finishes working in a CLI tool, the Coverage Agent captures that context and surfaces it in QI Home for test generation. Developers keep their existing workflow. QA reviews what arrives and maps it to the right sprint or Ad-Hoc session. +Developer Context Mapping connects the tools your developers already use to the Quality Intelligence loop in Arcus. When a developer opens a pull request or finishes working in a CLI tool, Atto captures that context and surfaces it in QI Home for test generation. Developers keep their existing workflow. QA reviews what arrives and maps it to the right sprint or Ad-Hoc session. --- @@ -44,7 +44,7 @@ Developer Context Mapping connects the tools your developers already use to the AI coding tools let developers write and merge changes faster than tests can be authored by hand. Test coverage trails the code, and there is no direct measure of how much of a recent change has been tested. -Developer Context Mapping treats the coding session as the record of what changed. The Coverage Agent captures the session and identifies changed areas with no corresponding tests, the Generator Agent creates test cases from it for you to review, and QI Home reports the result through the Quality Intelligence Metrics. Developers continue working in their existing tool, and the test suite is built from the work they have already done rather than reconstructed afterwards. +Developer Context Mapping treats the coding session as the record of what changed. Atto captures the session, generates test cases from it for you to review, identifies changed areas with no corresponding tests, and reports the result through the Quality Intelligence Metrics. Developers continue working in their existing tool, and the test suite is built from the work they have already done rather than reconstructed afterwards. --- @@ -52,7 +52,7 @@ Developer Context Mapping treats the coding session as the record of what change * **Developers** work in their existing CLI tool. The plugin captures context in the background, and they push it when a task is complete. * **QA and test engineers** review the generated test cases, accept, edit, or reject each one, and map incoming context to the correct sprint or Ad-Hoc session. -* **Engineering leads and release managers** read the Coverage, Release Readiness, and Release Gate values that result. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/). +* **Engineering leads and release managers** read the Coverage, Release Readiness, and Release Gate values that result. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/). --- @@ -74,11 +74,11 @@ Every incoming context entry, whether a pull request or captured coding activity **Unmapped** -All context lands here first. The Coverage Agent shows an AI-generated suggestion for which sprint and story the context belongs to. You review the suggestion and map it manually, or dismiss it if it is not relevant. +All context lands here first. Atto shows an AI-generated suggestion for which sprint and story the context belongs to. You review the suggestion and map it manually, or dismiss it if it is not relevant. **Sprint** -Context mapped to a sprint contributes to test generation for that sprint. The Generator Agent creates new test cases or updates existing ones based on the context content. The sprint's coverage, pass rate, and release readiness metrics update accordingly. +Context mapped to a sprint contributes to test generation for that sprint. Atto generates new test cases or updates existing ones based on the context content. The sprint's coverage, pass rate, and release readiness metrics update accordingly. Context routes to a sprint automatically when: @@ -91,23 +91,23 @@ Context mapped to an Ad-Hoc session is for work not tied to a sprint, such as ho --- -## **What Gets Generated After Mapping** +## **What Atto Generates After Mapping** -Mapping is the trigger. Once context is assigned to a sprint or Ad-Hoc session: +Mapping is the trigger. Once context is assigned to a sprint or Ad-Hoc session, Atto produces: -* The **Generator Agent** creates **test cases** based on the pull request diff or captured context. You review each case and accept, edit, or reject it before it is added to the sprint. -* The **Coverage Agent** identifies **coverage gaps**, areas of the change with no corresponding tests. -* The **Runner Agent** organizes **a test plan** into Smoke, Feature, Regression, and Deep Regression suites. +* **Test cases** based on the pull request diff or captured context. You review each case and accept, edit, or reject it before it is added to the sprint. +* **Coverage gaps** identifying areas of the change with no corresponding tests. +* **A test plan** organized into Smoke, Feature, Regression, and Deep Regression suites. -Execution results from these test plans feed the Quality Intelligence Metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for how Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate are calculated. +Execution results from these test plans feed the Quality Intelligence Metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/) for how Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate are calculated. --- ## **When CLI Context and a Pull Request Overlap** -Developers using a CLI tool often raise a pull request for the same work they captured as context. The Coverage Agent handles this automatically: +Developers using a CLI tool often raise a pull request for the same work they captured as context. Atto handles this automatically: -* **Context still unmapped when the PR is raised** — The Coverage Agent converts it into a GitHub context. The CLI context and the pull request are unified as a single entry in Unmapped Context. Its prompt history and code changes are analyzed together with the PR diff. +* **Context still unmapped when the PR is raised** — Atto converts it into a GitHub context. The CLI context and the pull request are unified as a single entry in Unmapped Context. Its prompt history and code changes are analyzed together with the PR diff. * **Context already mapped when the PR is raised** — The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed. @@ -119,11 +119,11 @@ Developers who run `/arcus:map` early do not need to take any action when they r | Tool | What it captures | Setup | |------|-----------------|-------| -| GitHub | Pull requests from connected repositories | [Connect GitHub](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/) | -| Claude Code | Coding context: prompts, tool calls, file changes | [Connect Claude Code](https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/) | -| Cursor | Coding context: prompts, tool calls, file changes | [Connect Cursor](https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/) | -| GitHub Copilot | Coding context: prompts, tool calls, file changes | [Connect GitHub Copilot](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/) | -| Codex | Coding context: prompts, tool calls, file changes | [Connect Codex](https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/) | +| GitHub | Pull requests from connected repositories | [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/) | +| Claude Code | Coding context: prompts, tool calls, file changes | [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/) | +| Cursor | Coding context: prompts, tool calls, file changes | [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/) | +| GitHub Copilot | Coding context: prompts, tool calls, file changes | [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/) | +| Codex | Coding context: prompts, tool calls, file changes | [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/) | You can connect any combination of tools. Most teams connect GitHub and at least one CLI tool. diff --git a/src/pages/docs/arcus/qi-home/coverage-and-gaps.md b/src/pages/docs/test-management/qi-home/coverage-and-gaps.md similarity index 83% rename from src/pages/docs/arcus/qi-home/coverage-and-gaps.md rename to src/pages/docs/test-management/qi-home/coverage-and-gaps.md index 4354d8d..2139923 100644 --- a/src/pages/docs/arcus/qi-home/coverage-and-gaps.md +++ b/src/pages/docs/test-management/qi-home/coverage-and-gaps.md @@ -1,7 +1,7 @@ --- title: 'Coverage and Gaps' page_title: 'Coverage and Gaps' -metadesc: 'Track how much of your feature is covered by accepted test cases and where the gaps are. Learn how the Coverage Agent calculates coverage at the session and module level.' +metadesc: 'Track how much of your feature is covered by accepted test cases and where the gaps are. Learn how Atto calculates coverage at the session and module level.' description: 'Learn how coverage is calculated and how to review gaps by module in QI Home.' noindex: false order: 13.27 @@ -33,7 +33,7 @@ contextual_links: --- -Coverage tells you what percentage of your generated test cases have been accepted. Gaps are the test cases that have not been accepted yet. The more test cases you accept, the higher your coverage. Both coverage and gaps update in real time as you review test cases, tracked by the Coverage Agent. +Coverage tells you what percentage of your generated test cases have been accepted. Gaps are the test cases that have not been accepted yet. The more test cases you accept, the higher your coverage. Both coverage and gaps update in real time as you review test cases. --- @@ -43,7 +43,7 @@ Coverage is calculated using this formula: **Coverage = Accepted ÷ (Accepted + Pending) × 100** -For example, if the Generator Agent generated 10 test cases and you have accepted 3, your coverage is 30%. The remaining 7 test cases are gaps. +For example, if Atto generated 10 test cases and you have accepted 3, your coverage is 30%. The remaining 7 test cases are gaps. Coverage appears at two levels: @@ -87,7 +87,7 @@ The Coverage tab shows test cases grouped by module. Each module row shows: 2. Click a gap to open the test case detail view. From there you can accept or reject it. [[info | **NOTE**:]] -| Gaps are not failed tests. They are pending test cases that the Generator Agent created but you have not reviewed yet. Accepting a gap removes it from the gaps list and increases your coverage percentage. +| Gaps are not failed tests. They are pending test cases that Atto generated but you have not reviewed yet. Accepting a gap removes it from the gaps list and increases your coverage percentage. --- @@ -100,8 +100,8 @@ The session header always shows your current coverage at a glance. - **Pass Rate, Confidence, and Release Readiness**: These show "Awaiting execution" until test runs are executed. - **Release Gate**: Shows "**Not Ready**" until the configured thresholds are met. -For details on all five metrics, see [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/). +For details on all five metrics, see [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/). -To generate test cases for modules with gaps, open the Playground from the session header. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/). +To generate test cases for modules with gaps, open the Playground from the session header. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/). --- diff --git a/src/pages/docs/arcus/qi-home/faqs.md b/src/pages/docs/test-management/qi-home/faqs.md similarity index 63% rename from src/pages/docs/arcus/qi-home/faqs.md rename to src/pages/docs/test-management/qi-home/faqs.md index 33af113..49e1dc7 100644 --- a/src/pages/docs/arcus/qi-home/faqs.md +++ b/src/pages/docs/test-management/qi-home/faqs.md @@ -2,7 +2,7 @@ title: 'FAQs' page_title: 'QI Home FAQs' metadesc: 'Frequently asked questions about QI Home — Ad-Hoc vs Sprints, coverage, quality metrics, Agentic Learning, Copilot, and developer context mapping.' -description: 'Answers to frequently asked questions about QI Home in Arcus by Testsigma.' +description: 'Answers to frequently asked questions about QI Home in Test Management by Testsigma.' noindex: false order: 13.52 page_id: 'qi-home-faqs' @@ -31,65 +31,65 @@ contextual_links: ### **1. What is the difference between Ad-Hoc and Sprints?** -Both generate test cases using the Generator Agent. The difference is in how generation is triggered and where the context comes from. In Ad-Hoc, you manually attach context sources and click Generate. In Sprints, the Generator Agent detects when a sprint starts in your connected project management tool and offers to generate automatically using the sprint stories and linked artifacts. Everything after generation — reviewing test cases, coverage, test plans, and quality metrics — is the same for both. See the [Overview](https://testsigma.com/docs/arcus/qi-home/overview/). +Both generate test cases using Atto. The difference is in how generation is triggered and where the context comes from. In Ad-Hoc, you manually attach context sources and click Generate. In Sprints, Atto detects when a sprint starts in your connected project management tool and offers to generate automatically using the sprint stories and linked artifacts. Everything after generation — reviewing test cases, coverage, test plans, and quality metrics — is the same for both. See the [Overview](https://testsigma.com/docs/test-management/qi-home/overview/). -### **2. Why did generation skip some scenarios or leave scenario outlines empty?** +### **2. Why did Atto skip some scenarios or leave scenario outlines empty?** -The Generator Agent creates full test cases for the scenarios it can complete based on your context. For areas where the context was incomplete, or where the Coverage Agent flagged that coverage was needed but the scenario could not be fully expanded, the Generator Agent creates Remaining Scenario Outlines instead. These are stubs that mark areas needing coverage. Open the Playground and describe the missing scenarios to fill them. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/). +Atto generates full test cases for the scenarios it can complete based on your context. For areas where the context was incomplete or where Atto identified coverage was needed but could not fully expand the scenario, it creates Remaining Scenario Outlines. These are stubs that mark areas needing coverage. Open the Playground and describe the missing scenarios to fill them. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/). ### **3. I clicked Not Now on a sprint notification. Can I still generate test cases?** -Yes. Go to **QI Home > Sprints** tab. Find the sprint with **To Do** status and click **Generate Test Cases** next to it. See [Generate Test Cases](https://testsigma.com/docs/arcus/qi-home/sprints/generate-test-cases/). +Yes. Go to **QI Home > Sprints** tab. Find the sprint with **To Do** status and click **Generate Test Cases** next to it. See [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/sprints/generate-test-cases/). ### **4. Why is my coverage showing 0%?** -Coverage reflects accepted test cases, not generated ones. Generated test cases start in Pending status. You need to review them and click Save to Library to accept them. Once you accept test cases, coverage updates in real time. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/). +Coverage reflects accepted test cases, not generated ones. Generated test cases start in Pending status. You need to review them and click Save to Library to accept them. Once you accept test cases, coverage updates in real time. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/). ### **5. What happens to test cases I do not accept?** -Unaccepted test cases remain in Pending status and are counted as gaps. They count against your coverage percentage until you either accept or reject them. Rejecting a test case removes it from the gaps count. Leaving it as Pending keeps it as a gap. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/). +Unaccepted test cases remain in Pending status and are counted as gaps. They count against your coverage percentage until you either accept or reject them. Rejecting a test case removes it from the gaps count. Leaving it as Pending keeps it as a gap. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/). -### **6. Can I edit a test case the Generator Agent created?** +### **6. Can I edit a test case Atto generated?** Yes. Open the test case from the session detail view or from your library. You can edit the title, steps, preconditions, and expected results directly on the test case page. ### **7. Can I regenerate test cases for a sprint after the initial generation?** -Yes. Open the Playground from the session header and write a new prompt describing what you want to add or change. The Generator Agent creates additional test cases and adds them to the existing session. You can also add new context sources before generating. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/). +Yes. Open the Playground from the session header and write a new prompt describing what you want to add or change. Atto generates additional test cases and adds them to the existing session. You can also add new context sources before generating. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/). ### **8. What is a test library?** -Your test library is where accepted test cases are stored. When you click Save to Library, you select a folder and QI Home saves the test case there. Saved test cases are available for automation, test plan inclusion, and re-use across sessions. +Your test library is where accepted test cases are stored. When you click Save to Library, you select a folder and Atto saves the test case there. Saved test cases are available for automation, test plan inclusion, and re-use across sessions. ### **9. Why does the Release Gate show "Not Ready" even though I have accepted test cases?** -The Release Gate evaluates Release Readiness, which requires test runs to have been executed. Accepting test cases updates Coverage but does not affect Pass Rate, Confidence, or Release Readiness until test runs complete. Execute at least one test plan to activate the remaining metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/). +The Release Gate evaluates Release Readiness, which requires test runs to have been executed. Accepting test cases updates Coverage but does not affect Pass Rate, Confidence, or Release Readiness until test runs complete. Execute at least one test plan to activate the remaining metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/). ### **10. What is the difference between Release Readiness and Release Gate?** -Release Readiness is a 0 to 100 score that combines Coverage, Pass Rate, and Confidence. Release Gate translates that score into a decision: GO, CONDITIONAL, or NO-GO, based on configurable thresholds. Release Readiness tells you how ready you are. Release Gate tells you whether that readiness meets your project's release standard. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/). +Release Readiness is a 0 to 100 score that combines Coverage, Pass Rate, and Confidence. Release Gate translates that score into a decision: GO, CONDITIONAL, or NO-GO, based on configurable thresholds. Release Readiness tells you how ready you are. Release Gate tells you whether that readiness meets your project's release standard. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/). ### **11. Do I need the Testsigma Terminal for Agentic Learning?** -Only for Local execution. Cloud execution uses Testsigma Lab and requires nothing on your machine. If you choose Local Devices in the Learn and Automate dialog, Testsigma Terminal must be running on your desktop. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) and [Learn Test Case Live (Local)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local/). +Only for Local execution. Cloud execution uses Testsigma Lab and requires nothing on your machine. If you choose Local Devices in the Learn and Automate dialog, Testsigma Terminal must be running on your desktop. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) and [Learn Test Case Live (Local)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local/). ### **12. What happens to the cloud VM when I end a Copilot session?** -The cloud VM is released and any unsaved changes are lost. Use Save and End to save your results before the VM closes. If you click Dismiss, the VM stays running and continues to consume resources until you end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud/). +The cloud VM is released and any unsaved changes are lost. Use Save and End to save your results before the VM closes. If you click Dismiss, the VM stays running and continues to consume resources until you end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/). ### **13. Can I map a GitHub PR to an Ad-Hoc session instead of a sprint?** -Yes. In the Map to Module dialog, select Adhoc under Map to, then select an existing Ad-Hoc session or create a new one. See [Map GitHub Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-github/). +Yes. In the Map to Module dialog, select Adhoc under Map to, then select an existing Ad-Hoc session or create a new one. See [Map GitHub Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/). ### **14. How do I connect Jira, GitHub, or a CLI tool to my project?** -Go to **Settings > Integrations** from the left navigation. Each integration has its own connection flow. Jira, Azure DevOps, Linear, ClickUp, and Confluence are used as context sources for test generation. GitHub, Claude Code, Cursor, GitHub Copilot, and Codex are used for Developer Context Mapping. Each has a dedicated setup guide. See [Connect GitHub](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/), [Connect Claude Code](https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/). +Go to **Settings > Integrations** from the left navigation. Each integration has its own connection flow. Jira, Azure DevOps, Linear, ClickUp, and Confluence are used as context sources for test generation. GitHub, Claude Code, Cursor, GitHub Copilot, and Codex are used for Developer Context Mapping. Each has a dedicated setup guide. See [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/), [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/). --- ### **15. What CLI tools does Developer Context Mapping support?** -Developer Context Mapping supports Claude Code, Cursor, GitHub Copilot, and Codex. All four capture coding activity through an Arcus plugin and push it to QI Home as context using the `/arcus:push` command. The mapping flow in QI Home is identical for all four. Context appears in Unmapped Context with a tool-specific badge, and you map it to a sprint or Ad-Hoc session the same way. See [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/). +Developer Context Mapping supports Claude Code, Cursor, GitHub Copilot, and Codex. All four capture coding activity through an Arcus plugin and push it to QI Home as context using the `/arcus:push` command. The mapping flow in QI Home is identical for all four. Context appears in Unmapped Context with a tool-specific badge, and you map it to a sprint or Ad-Hoc session the same way. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/). --- diff --git a/src/pages/docs/test-management/qi-home/overview.md b/src/pages/docs/test-management/qi-home/overview.md new file mode 100644 index 0000000..1628fb1 --- /dev/null +++ b/src/pages/docs/test-management/qi-home/overview.md @@ -0,0 +1,194 @@ +--- +title: "Overview: QI Home" +page_title: "Overview of QI Home" +metadesc: 'QI Home is where Atto generates test cases from your requirements, tracks coverage, builds test plans, and automates test execution in Test Management by Testsigma.' +description: 'An overview of QI Home, where Atto generates test cases, tracks coverage, builds test plans, and automates test execution.' +noindex: false +order: 13.20 +page_id: 'qi-home-overview' +warning: false +contextual_links: + - type: section + name: 'Contents' + - type: link + name: 'Two Ways to Start Test Generation' + url: '#two-ways-to-start-test-generation' + - type: link + name: 'After Test Cases Are Generated' + url: '#after-test-cases-are-generated' + - type: link + name: 'Automation' + url: '#automation' + - type: link + name: 'Developer Context Mapping' + url: '#developer-context-mapping' + - type: link + name: 'Overview: Developer Context Mapping' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/overview/' + - type: link + name: 'Connect GitHub' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/' + - type: link + name: 'Connect Claude Code' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/' + - type: link + name: 'Connect Cursor' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/' + - type: link + name: 'Connect GitHub Copilot' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/' + - type: link + name: 'Connect Codex' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/' + - type: link + name: 'Map GitHub Context' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/' + - type: link + name: 'Map Developer Context' + url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/' + - type: link + name: "What's in This Section" + url: '#whats-in-this-section' + - type: link + name: 'Getting Help' + url: '#getting-help' +--- + +
+ +**QI Home is where you generate test cases, track coverage, and automate with AI.** + +--- + +QI Home is where Atto, the AI feature in Test Management by Testsigma, generates test cases from your requirements, tracks coverage against your modules, builds test plans, and automates test execution. It also detects developer activity from connected Claude Code, Cursor, GitHub Copilot, and Codex context and GitHub pull requests, so your test coverage stays current with what your team is building. + +You do not write test cases from scratch. You give Atto the context it needs, and it generates test cases for you. You review what was generated, accept the cases that are accurate, and save them to your library. Coverage, test plans, and quality metrics update as you go. + +There are two ways to start: Ad-Hoc, where you attach context manually and trigger generation yourself, and Sprints, where Atto detects a sprint start and begins generation automatically. Everything after generation works the same for both. + +--- + +## **Two Ways to Start Test Generation** + +QI Home gives you two starting points depending on how your team works. The generation trigger is different for each, but the rest of the workflow is identical. + +### **Ad-Hoc** + +Ad-Hoc lets you generate test cases on demand by attaching your own context sources, without tying them to a sprint. You open a new session, attach context sources, write a prompt, and click Generate. Atto reads what you have provided and generates test cases mapped to your features. + +Context sources you can attach include: + +- **Jira, Azure DevOps, Linear, or ClickUp** for user stories and requirements (requires the respective integration to be connected) +- **Confluence** for PRDs and specification documents (requires Confluence integration) +- **Figma** for UI designs and flows (requires Figma integration) +- **Files and Documents** such as PDFs, Word docs, or text files +- **Video Recording** for walkthroughs or recorded user flows + +Use Ad-Hoc when: + +- You are generating test cases outside a sprint cycle +- You want to control exactly what context Atto uses +- You are exploring coverage for a new feature, release, or exploratory session + +### **Sprints** + +Sprints mode generates test coverage automatically at the start of each sprint, pulling context straight from your linked stories. When a sprint starts in your connected project management tool, Atto detects it and shows a notification. You confirm generation, and Atto pulls in the context linked to the sprint stories, including Figma designs, Confluence pages, PRDs, and relevant pull requests, and begins generating test cases. + +Use Sprints when: + +- Your team works in agile sprints +- You want test coverage to start as soon as a sprint kicks off, without manually attaching anything +- You want Atto to use your Jira, Linear, ClickUp, or Azure DevOps stories as the primary source of truth + +--- + +## **After Test Cases Are Generated** + +Whether you use **Ad-Hoc** or **Sprints**, the next steps are the same. You review the test cases Atto generated, accept the ones that are accurate, and save them to your library. Coverage, test plans, and quality metrics update as you go. + +[**Review and Accept Test Cases**](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/) allows you to browse the generated test cases grouped by scenario, view step-by-step details for each case, and accept or reject them individually or in bulk. Test cases you save go into your library. Test cases you do not accept are tracked as gaps. + +[**Coverage and Gaps**](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/) shows you the coverage percentage per module. Coverage is calculated as accepted test cases divided by accepted plus pending test cases, and rejected cases are excluded. Gaps are pending test cases that have not been accepted yet. They are your signal that certain areas of the application are not yet covered. + +[**Test Plans**](https://testsigma.com/docs/test-management/qi-home/test-plans/) are generated automatically by Atto in four types: Smoke, Feature, Regression, and Deep Regression. Each type is a superset of the previous one. Smoke is always included in Feature, Feature in Regression, and Regression in Deep Regression. Plans are ready to run as soon as you have accepted test cases. + +[**Quality Intelligence Metrics**](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/) are five metrics shown in the session header that together tell you how confident you can be in the current build. The metrics are Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate. They update as test cases are accepted and test runs are executed. + +--- + +## **Automation** + +Once a test case exists in your library, Atto can automate it without you writing any code or scripts. + +**Agentic Learning** opens a browser, either on Testsigma Lab in the cloud or on your local device, and walks through the test case steps on your live application. Atto observes how the application behaves at each step, learns the element interactions, and generates automated steps. You review the output and save it to your library. The test case moves from manual to automated in a few minutes. + +**Copilot** takes those automated steps and executes them in a browser with a live panel showing each step as it runs. You can pause the execution, add new steps mid-run, switch between manual and automated steps, and save the results when done. Copilot also works without Agentic Learning for running any test case interactively, which is useful for quick sanity checks or exploratory runs. + +--- + +## **Developer Context Mapping** + +Developer Context Mapping keeps your test coverage aligned with what your team is actually building. + +When your developers work in Claude Code, Cursor, GitHub Copilot, or Codex, or open pull requests in GitHub, Atto detects that context and surfaces it in the **Unmapped Context** view in QI Home. Each context entry includes an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks. Once mapped, Atto generates new test cases or updates existing ones based on the code changes or development activity captured. + +See [Overview: Developer Context Mapping](https://testsigma.com/docs/test-management/qi-home/context-mapping/overview/) for how the Unmapped Context model works, when to use GitHub versus a CLI tool, and what happens when a developer raises a PR for work already captured as CLI context. + +--- + +## **What's in This Section** + +**Ad-Hoc** + +- [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/) +- [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/) +- [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/ad-hoc/generate-test-cases/) + +**Sprints** + +- [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/sprints/generate-test-cases/) + +**Shared Workflows** + +- [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/) +- [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/) +- [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/) +- [Test Plans](https://testsigma.com/docs/test-management/qi-home/test-plans/) +- [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/) + +**Automation** + +- [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) +- [Learn Test Case Live (Local)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local/) +- [Live Learning Controls](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls/) +- [Run Automated Test Case with Copilot](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot/) +- [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/) +- [Execute Test Case in Local](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local/) +- [Execution Controls in Copilot](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/) + +**Developer Context Mapping** + +- [Overview](https://testsigma.com/docs/test-management/qi-home/context-mapping/overview/) +- [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/) +- [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/) +- [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/) +- [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/) +- [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/) +- [Map GitHub Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/) +- [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/) + +**Others** + +- Best Practices +- [FAQs](https://testsigma.com/docs/test-management/qi-home/faqs/) + +[[info | **NOTE**:]] +| QI Home requires an active project in Test Management by Testsigma. To attach context from Jira, Azure DevOps, Linear, ClickUp, Confluence, or Figma in Ad-Hoc, you need the respective integration connected to your project. Files, documents, and video recordings can be attached without any external integration. For Sprints, connect your project to a supported project management tool. For Developer Context Mapping, connect your Claude or GitHub account. + +--- + +## **Getting Help** + +For questions or support, reach out to the Testsigma team at **support@testsigma.com**. + +--- diff --git a/src/pages/docs/arcus/qi-home/quality-intelligence-metrics.md b/src/pages/docs/test-management/qi-home/quality-intelligence-metrics.md similarity index 91% rename from src/pages/docs/arcus/qi-home/quality-intelligence-metrics.md rename to src/pages/docs/test-management/qi-home/quality-intelligence-metrics.md index cffe30c..7caf417 100644 --- a/src/pages/docs/arcus/qi-home/quality-intelligence-metrics.md +++ b/src/pages/docs/test-management/qi-home/quality-intelligence-metrics.md @@ -69,7 +69,7 @@ Pending includes AI-discovered gaps and test cases still in Pending status. Reje | **Gap Risk** | 60% – 79% | Material untested surface. | | **Critical Gap** | < 60% | Majority of testing surface unaddressed. | -See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/) for the module-level breakdown. +See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/) for the module-level breakdown. --- @@ -103,7 +103,7 @@ Total Weight is the sum of priority weights for all test units in the topmost ge **When it appears:** Confidence shows "Awaiting execution" until test runs have been executed. -**How it works in practice:** If the Runner Agent generated a Deep Regression plan but you only ran Smoke, Confidence reflects the gap. The 40 units you did not run are in the denominator but contribute zero to the numerator. The score reports honestly: "you committed to Regression-level validation but validated only Smoke." If you explicitly reject the higher plans and keep only Smoke, the scope adjusts and Confidence can reach 100%. +**How it works in practice:** If Atto generated a Deep Regression plan but you only ran Smoke, Confidence reflects the gap. The 40 units you did not run are in the denominator but contribute zero to the numerator. The score reports honestly: "you committed to Regression-level validation but validated only Smoke." If you explicitly reject the higher plans and keep only Smoke, the scope adjusts and Confidence can reach 100%. **Bands:** @@ -114,7 +114,7 @@ Total Weight is the sum of priority weights for all test units in the topmost ge | **Low** | < 50% | Significant trust or commitment-fulfillment issues. Pass Rate cannot be relied on. | [[info | **NOTE**:]] -| Confidence depends on the nested test plan hierarchy. See [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) for how the topmost generated and topmost executed plan affect this calculation. +| Confidence depends on the nested test plan hierarchy. See [Test Plans](https://testsigma.com/docs/test-management/qi-home/test-plans/) for how the topmost generated and topmost executed plan affect this calculation. --- diff --git a/src/pages/docs/arcus/qi-home/review-and-accept-test-cases.md b/src/pages/docs/test-management/qi-home/review-and-accept-test-cases.md similarity index 79% rename from src/pages/docs/arcus/qi-home/review-and-accept-test-cases.md rename to src/pages/docs/test-management/qi-home/review-and-accept-test-cases.md index b4ec53a..d6a0277 100644 --- a/src/pages/docs/arcus/qi-home/review-and-accept-test-cases.md +++ b/src/pages/docs/test-management/qi-home/review-and-accept-test-cases.md @@ -1,8 +1,8 @@ --- title: 'Review and Accept Test Cases' page_title: 'Review and Accept Test Cases' -metadesc: 'Review the test cases the Generator Agent created, accept the ones that look right, and save them to your library. Learn the review workflow for sprints and Ad-Hoc sessions.' -description: 'Learn how to review, accept or reject, and save Generator Agent test cases to your library.' +metadesc: 'Review the test cases Atto generated, accept the ones that look right, and save them to your library. Learn the review workflow for sprints and Ad-Hoc sessions.' +description: 'Learn how to review, accept or reject, and save Atto-generated test cases to your library.' noindex: false order: 13.26 page_id: 'qi-home-review-and-accept-test-cases' @@ -32,11 +32,11 @@ contextual_links:
-**Review the test cases the Generator Agent created, accept the ones that look right, and save them to your library.** +**Review the test cases Atto generated, accept the ones that look right, and save them to your library.** --- -After generation completes, the Generator Agent's test cases are in **Pending** status. They are not part of your library yet. Your job is to review them, accept the ones that are accurate and relevant, and save them. Test cases that are not accepted remain as gaps and count against your coverage. +After generation completes, Atto's test cases are in **Pending** status. They are not part of your library yet. Your job is to review them, accept the ones that are accurate and relevant, and save them. Test cases that are not accepted remain as gaps and count against your coverage. The review experience is the same whether you generated test cases from a sprint or an Ad-Hoc session. @@ -114,7 +114,7 @@ When you save a test case, you select the folder where it will be stored. 3. Click **Save**. The test cases are saved and their status changes from **Pending** to **Accepted**. [[info | **NOTE**:]] -| The Generator Agent suggests a folder based on the feature taxonomy of your project. You can accept the suggestion or choose a different folder. +| Atto suggests a folder based on the feature taxonomy of your project. You can accept the suggestion or choose a different folder. --- @@ -123,6 +123,6 @@ When you save a test case, you select the folder where it will be stored. - **Rejected** test cases are dismissed and do not count toward coverage. - **Pending** test cases (not yet reviewed) are treated as gaps. They count against your coverage percentage until they are accepted or rejected. -Your coverage percentage updates in real time as you accept test cases. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/) for how coverage is calculated. +Your coverage percentage updates in real time as you accept test cases. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/) for how coverage is calculated. --- diff --git a/src/pages/docs/arcus/qi-home/sprints/generate-test-cases.md b/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md similarity index 56% rename from src/pages/docs/arcus/qi-home/sprints/generate-test-cases.md rename to src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md index 3325b63..a460ec7 100644 --- a/src/pages/docs/arcus/qi-home/sprints/generate-test-cases.md +++ b/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Generate Test Cases' page_title: 'Generate Test Cases (Sprints)' -metadesc: 'When a sprint starts, the Generator Agent detects it and creates test cases automatically from the sprint stories and linked artifacts. Learn how sprint detection works.' +metadesc: 'When a sprint starts, Atto detects it and generates test cases automatically from the sprint stories and linked artifacts. Learn how sprint detection works.' description: 'Learn how sprint detection triggers automatic test case generation, and how to generate test cases for skipped sprints.' noindex: false order: 13.24 @@ -17,8 +17,8 @@ contextual_links: name: 'Confirm Generation When a Sprint Starts' url: '#confirm-generation-when-a-sprint-starts' - type: link - name: 'What the Generator Agent Uses as Context' - url: '#what-the-generator-agent-uses-as-context' + name: 'What Atto Uses as Context' + url: '#what-atto-uses-as-context' - type: link name: 'Generate Test Cases for an Unprocessed Sprint' url: '#generate-test-cases-for-an-unprocessed-sprint' @@ -32,11 +32,11 @@ contextual_links:
-**When a sprint starts, the Generator Agent detects it and generates test cases automatically.** +**When a sprint starts, Atto detects it and generates test cases automatically.** --- -In Sprints, test case generation is triggered by your sprint workflow, not manually. When a sprint starts in your connected project management tool, the Generator Agent detects the new sprint and notifies you. You confirm, and it pulls context from the sprint stories and linked artifacts to generate test cases. +In Sprints, test case generation is triggered by your sprint workflow, not manually. When a sprint starts in your connected project management tool, Atto detects the new sprint and notifies you. You confirm, and Atto pulls context from the sprint stories and linked artifacts to generate test cases. This article covers how sprint detection works, how to confirm or defer generation, and how to generate test cases for sprints that were skipped. @@ -45,7 +45,7 @@ This article covers how sprint detection works, how to confirm or defer generati > ## **Prerequisites** > > Before you begin, ensure that: -> - You have an active project in Arcus by Testsigma. +> - You have an active project in Test Management by Testsigma. > - Your project management tool (Jira, Azure DevOps, Linear, or ClickUp) is connected to your project. > - The context sources linked in your sprint stories (Confluence pages, Figma designs, PRDs) are either publicly accessible or connected as integrations. @@ -53,26 +53,26 @@ This article covers how sprint detection works, how to confirm or defer generati ## **Confirm Generation When a Sprint Starts** -When a sprint starts in your connected project management tool, the Generator Agent automatically detects it and shows a notification. +When a sprint starts in your connected project management tool, Atto automatically detects it and shows a notification. 1. From the left navigation bar, go to **QI Home**. 2. Select the **Sprints** tab. -3. When the Generator Agent detects a new sprint, a notification appears: **A new sprint is live. Start creating test cases for it?** The notification shows the sprint name and start date. +3. When Atto detects a new sprint, a notification appears: **Atto has started to Generate your tests. A new sprint is live. Shall I start creating test cases for this?** The notification shows the sprint name and start date. -4. Click **Start Generating Tests** to begin. The Generator Agent moves the sprint to **In Progress** and begins generating test cases. +4. Click **Start Generating Tests** to begin. Atto moves the sprint to **In Progress** and begins generating test cases. [[info | **NOTE**:]] | Click **Not Now** to skip generation for now. The sprint stays in **To Do** status and appears in the Sprints sidebar with a **Generate Test Cases** link. You can trigger generation manually whenever you are ready. --- -## **What the Generator Agent Uses as Context** +## **What Atto Uses as Context** -The Generator Agent automatically pulls context from the sprint stories and their linked artifacts. You do not need to attach anything manually. +Atto automatically pulls context from the sprint stories and their linked artifacts. You do not need to attach anything manually. -Context the Generator Agent uses includes: +Context Atto uses includes: - Story titles, descriptions, and acceptance criteria from your project management tool - Confluence pages linked in sprint stories @@ -81,29 +81,29 @@ Context the Generator Agent uses includes: - Relevant pull requests linked to sprint stories [[info | **NOTE**:]] -| The Generator Agent can only read artifacts that are either publicly accessible or connected as integrations. If a Confluence page or Figma file is private and the integration is not set up, it will not be able to use it as context. +| Atto can only read artifacts that are either publicly accessible or connected as integrations. If a Confluence page or Figma file is private and the integration is not set up, Atto will not be able to use it as context. --- ## **Generate Test Cases for an Unprocessed Sprint** -If you clicked **Not Now** on a sprint or if the Generator Agent missed a sprint notification, you can trigger generation manually. +If you clicked **Not Now** on a sprint or if Atto missed a sprint notification, you can trigger generation manually. 1. From the left navigation bar, go to **QI Home** and select the **Sprints** tab. 2. In the left sidebar, find the sprint with **To Do** status. -3. Click **Generate Test Cases** next to the sprint name. The Generator Agent begins generating test cases using the same process as automatic detection. +3. Click **Generate Test Cases** next to the sprint name. Atto begins generating test cases using the same process as automatic detection. --- ## **What Happens During Generation** -The Generator Agent uses the same generation process as Ad-Hoc. You can watch the progress in the left panel as each step completes. Generation typically takes one to two minutes. +Atto uses the same generation process as Ad-Hoc. You can watch the progress in the left panel as each step completes. Generation typically takes one to two minutes. -See [Generate Test Cases](https://testsigma.com/docs/arcus/qi-home/ad-hoc/generate-test-cases/) in the Ad-Hoc section for details on what the Generator Agent does during generation and how to read the generation summary. +See [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/ad-hoc/generate-test-cases/) in the Ad-Hoc section for details on what Atto does during generation and how to read the generation summary. --- @@ -113,8 +113,8 @@ When generation completes, the sprint moves to **In Progress** status in the sid From here you can: -- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/). -- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/). -- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/). +- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/). +- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/). +- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/). --- diff --git a/src/pages/docs/arcus/qi-home/test-plans.md b/src/pages/docs/test-management/qi-home/test-plans.md similarity index 71% rename from src/pages/docs/arcus/qi-home/test-plans.md rename to src/pages/docs/test-management/qi-home/test-plans.md index 3e6ca91..ad63f21 100644 --- a/src/pages/docs/arcus/qi-home/test-plans.md +++ b/src/pages/docs/test-management/qi-home/test-plans.md @@ -1,8 +1,8 @@ --- title: 'Test Plans' page_title: 'Test Plans' -metadesc: 'The Runner Agent automatically generates four nested test plan types for every sprint and Ad-Hoc session: Smoke, Feature, Regression, and Deep Regression. Learn how to review and run them.' -description: 'Learn how the Runner Agent auto-generates the four test plan types, and how to review, accept, and link them.' +metadesc: 'Atto automatically generates four nested test plan types for every sprint and Ad-Hoc session: Smoke, Feature, Regression, and Deep Regression. Learn how to review and run them.' +description: 'Learn how Atto auto-generates the four test plan types, and how to review, accept, and link them.' noindex: false order: 13.28 page_id: 'qi-home-test-plans' @@ -35,25 +35,25 @@ contextual_links:
-**The Runner Agent automatically generates test plans for every sprint and Ad-Hoc session. Review them, understand their scope, and run them when you are ready.** +**Atto automatically generates test plans for every sprint and Ad-Hoc session. Review them, understand their scope, and run them when you are ready.** --- -The Runner Agent generates four types of test plans as soon as test cases exist in your session. You do not create or configure them manually. Each plan type covers a different scope of your test cases, and they are always generated as a nested set, meaning the narrowest plan is always a subset of the next broader one. +Atto generates four types of test plans as soon as test cases exist in your session. You do not create or configure them manually. Each plan type covers a different scope of your test cases, and they are always generated as a nested set, meaning the narrowest plan is always a subset of the next broader one. --- > ## **Prerequisites** > > Before you begin, ensure that: -> - Test cases have been generated and accepted for the session. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/). +> - Test cases have been generated and accepted for the session. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/). > - You are viewing a sprint or Ad-Hoc session in QI Home. --- ## **The Four Plan Types** -The Runner Agent generates these four test plan types automatically. Each is a superset of the one before it. +Atto generates these four test plan types automatically. Each is a superset of the one before it. | Plan Type | Scope | | :--- | :--- | @@ -65,7 +65,7 @@ The Runner Agent generates these four test plan types automatically. Each is a s Smoke is always included in Feature, Feature in Regression, and Regression in Deep Regression. Running Deep Regression validates everything that Smoke, Feature, and Regression would have covered. [[info | **NOTE**:]] -| The topmost plan type that the Runner Agent generates defines the scope used to calculate the Confidence metric. The topmost plan type you actually execute provides the pass rate results. If the Runner Agent generates all four types but you only run Smoke, Confidence reflects that the narrowest coverage was validated. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/). +| The topmost plan type that Atto generates defines the scope used to calculate the Confidence metric. The topmost plan type you actually execute provides the pass rate results. If Atto generates all four types but you only run Smoke, Confidence reflects that the narrowest coverage was validated. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/). --- @@ -103,10 +103,10 @@ Smoke is always included in Feature, Feature in Regression, and Regression in De ## **Machine Configuration Detection** -The Runner Agent detects the application type from your test cases and suggests a machine configuration for each test plan. The detected types include Web, Android, and iOS. +Atto detects the application type from your test cases and suggests a machine configuration for each test plan. The detected types include Web, Android, and iOS. [[info | **NOTE**:]] -| Machine configuration detection uses the test case steps and context to determine the application type. If your session includes test cases for multiple application types, the Runner Agent may suggest separate configurations for each plan. +| Machine configuration detection uses the test case steps and context to determine the application type. If your session includes test cases for multiple application types, Atto may suggest separate configurations for each plan. --- @@ -114,7 +114,7 @@ The Runner Agent detects the application type from your test cases and suggests Accepting is a single global action. Clicking Accept Plan accepts all four plans at once — Smoke, Feature, Regression, and Deep Regression. You cannot accept individual plan types separately. -When you accept, the Runner Agent creates the following in your project: +When you accept, Atto creates the following in your project: - All four test plans under Plans, each named **[Sprint Name] | [Plan Type] Testing** (for example, **Sprint 2 — Hotel Discovery | Smoke Testing**), with an auto-generated description summarizing the feature areas and scenario count. - A set of test runs under each plan, one run per feature area or module (for example, **Sprint 2 — Hotel Discovery | Smoke Testing | Amenities, Category Filter, Navigation**, and so on). @@ -130,7 +130,7 @@ To accept the test plans: 3. Click **Accept Plan**. -4. The Runner Agent creates all four plans and their test runs in your project. +4. Atto creates all four plans and their test runs in your project. 5. To reject the test plans, click **Reject**. @@ -138,7 +138,7 @@ To accept the test plans: ## **Link an Automated Test Plan** -After accepting the test plans, you can link each plan type to an existing test plan in Testsigma. Linking connects the Runner Agent's generated plan to your automation setup so that automated run results flow back into QI Home. +After accepting the test plans, you can link each plan type to an existing test plan in Testsigma. Linking connects the Atto-generated plan to your automation setup so that automated run results flow back into Atto. [[info | **NOTE**:]] | Linking is done per plan type. You can link the Smoke plan to a Testsigma smoke plan, the Feature plan to a feature plan, and so on. @@ -160,7 +160,7 @@ After accepting the test plans, you can link each plan type to an existing test ## **Understand Test Runs** -Each test run represents a set of test cases grouped by feature area or module within a plan. When you accept the test plans, the Runner Agent creates one test run per feature area across all four plan types. These runs appear both inside their respective plan and in the global Test Runs list. +Each test run represents a set of test cases grouped by feature area or module within a plan. When you accept the test plans, Atto creates one test run per feature area across all four plan types. These runs appear both inside their respective plan and in the global Test Runs list. Each run in the plan shows the run ID, name, number of tests, scheduled date range, and an overall progress bar. diff --git a/src/pages/docs/arcus/qi-home/use-playground.md b/src/pages/docs/test-management/qi-home/use-playground.md similarity index 76% rename from src/pages/docs/arcus/qi-home/use-playground.md rename to src/pages/docs/test-management/qi-home/use-playground.md index c7698cc..278ff6e 100644 --- a/src/pages/docs/arcus/qi-home/use-playground.md +++ b/src/pages/docs/test-management/qi-home/use-playground.md @@ -1,8 +1,8 @@ --- title: 'Use Playground' page_title: 'Use Playground' -metadesc: 'Open the Playground to add context, generate more test cases, and refine what the Generator Agent produced for any sprint or Ad-Hoc session.' -description: 'Learn how to use the Playground to add context, generate more test cases, and refine Generator Agent output.' +metadesc: 'Open the Playground to add context, generate more test cases, and refine what Atto produced for any sprint or Ad-Hoc session.' +description: 'Learn how to use the Playground to add context, generate more test cases, and refine Atto output.' noindex: false order: 13.25 page_id: 'qi-home-use-playground' @@ -29,11 +29,11 @@ contextual_links:
-**Open the Playground to add context, generate more test cases, and refine what the Generator Agent produced.** +**Open the Playground to add context, generate more test cases, and refine what Atto produced.** --- -The Playground is the interactive workspace where you work with the Generator Agent after the initial test case generation. Use it to add context you missed the first time, describe specific flows you want the Generator Agent to cover, fill scenario outlines that are still empty, or trigger an additional round of generation for the same sprint or session. +The Playground is the interactive workspace where you work with Atto after the initial test case generation. Use it to add context you missed the first time, describe specific flows you want Atto to cover, fill scenario outlines that are still empty, or trigger an additional round of generation for the same sprint or session. The Playground is available from any sprint or Ad-Hoc session detail view after generation completes. @@ -66,15 +66,15 @@ If the initial generation missed something or you have new artifacts to share, a 2. Select the items and click **Save**. -For details on each source type, see [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/). +For details on each source type, see [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/). --- ## **Generate More Test Cases** -1. Follow the same steps mentioned in the above section, and in the prompt input area, describe the feature or flow you want the Generator Agent to cover. +1. Follow the same steps mentioned in the above section, and in the prompt input area, describe the feature or flow you want Atto to cover. -2. Click **Generate with AI**. The Generator Agent creates additional test cases and adds them to the current session. +2. Click **Generate with AI**. Atto generates additional test cases and adds them to the current session. --- @@ -89,6 +89,6 @@ The right panel shows all test cases for the current session. Use the filter tab Select individual test cases, then accept or reject them directly from the Playground. -For the full review workflow, including saving test cases to your library, see [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/). +For the full review workflow, including saving test cases to your library, see [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/). --- diff --git a/src/pages/docs/arcus/reports/create-report.md b/src/pages/docs/test-management/reports/create-report.md similarity index 88% rename from src/pages/docs/arcus/reports/create-report.md rename to src/pages/docs/test-management/reports/create-report.md index 587ecfa..169bdb8 100644 --- a/src/pages/docs/arcus/reports/create-report.md +++ b/src/pages/docs/test-management/reports/create-report.md @@ -1,7 +1,7 @@ --- title: 'Creating Reports' -page_title: 'Creating Reports in Arcus by Testsigma' -metadesc: 'Learn how to create reports in Arcus by Testsigma | Reports help you analyze test execution, track progress, and identify defect trends in test cycles' +page_title: 'Creating Reports in Test Management by Testsigma' +metadesc: 'Learn how to create reports in Test Management by Testsigma | Reports help you analyze test execution, track progress, and identify defect trends in test cycles' noindex: false order: 15.1 page_id: 'create-a-report-in-testsigma-test-management' @@ -35,7 +35,7 @@ contextual_links: --- -Reports in Arcus by Testsigma help you analyze test execution, track progress, and identify defect trends. This article discusses how to create reports using selected test artifacts. +Reports in Test Management by Testsigma help you analyze test execution, track progress, and identify defect trends. This article discusses how to create reports using selected test artifacts. --- diff --git a/src/pages/docs/arcus/reports/dashboard-reports.md b/src/pages/docs/test-management/reports/dashboard-reports.md similarity index 95% rename from src/pages/docs/arcus/reports/dashboard-reports.md rename to src/pages/docs/test-management/reports/dashboard-reports.md index 945387e..fa31e32 100644 --- a/src/pages/docs/arcus/reports/dashboard-reports.md +++ b/src/pages/docs/test-management/reports/dashboard-reports.md @@ -1,7 +1,7 @@ --- title: 'Reports in Dashboard View' -page_title: 'Reports in Dashboard View in Arcus by Testsigma' -metadesc: 'The Dashboard view in Arcus by Testsigma gives real-time test metrics. Learn how to track progress, monitor test health, & identify defects from Dashboard' +page_title: 'Reports in Dashboard View in Test Management by Testsigma' +metadesc: 'The Dashboard view in Test Management by Testsigma gives real-time test metrics. Learn how to track progress, monitor test health, & identify defects from Dashboard' noindex: false order: 15.3 page_id: 'view-dashboard-reports-in-testsigma-test-management' diff --git a/src/pages/docs/arcus/reports/requirement-traceability-report.md b/src/pages/docs/test-management/reports/requirement-traceability-report.md similarity index 95% rename from src/pages/docs/arcus/reports/requirement-traceability-report.md rename to src/pages/docs/test-management/reports/requirement-traceability-report.md index 7e4f239..f1c9802 100644 --- a/src/pages/docs/arcus/reports/requirement-traceability-report.md +++ b/src/pages/docs/test-management/reports/requirement-traceability-report.md @@ -1,7 +1,7 @@ --- title: 'Requirement Traceability Report' -page_title: 'Requirement Traceability Report in Arcus by Testsigma' -metadesc: 'View requirement coverage across test cases, test runs, and defects with the Requirement Traceability Report in Arcus by Testsigma.' +page_title: 'Requirement Traceability Report in Test Management by Testsigma' +metadesc: 'View requirement coverage across test cases, test runs, and defects with the Requirement Traceability Report in Test Management by Testsigma.' noindex: false order: 15.4 page_id: 'requirement-traceability-report-in-testsigma-test-management' diff --git a/src/pages/docs/arcus/reports/view-reports.md b/src/pages/docs/test-management/reports/view-reports.md similarity index 86% rename from src/pages/docs/arcus/reports/view-reports.md rename to src/pages/docs/test-management/reports/view-reports.md index 6dbd136..7040c14 100644 --- a/src/pages/docs/arcus/reports/view-reports.md +++ b/src/pages/docs/test-management/reports/view-reports.md @@ -1,7 +1,7 @@ --- title: 'Viewing Reports' -page_title: 'Viewing Reports in Arcus by Testsigma' -metadesc: 'Learn how to view reports in Arcus by Testsigma | Interpret different sections of a report and analyze test execution, track progress, and identify defects' +page_title: 'Viewing Reports in Test Management by Testsigma' +metadesc: 'Learn how to view reports in Test Management by Testsigma | Interpret different sections of a report and analyze test execution, track progress, and identify defects' noindex: false order: 15.2 page_id: 'view-reports-in-testsigma-test-management' @@ -29,7 +29,7 @@ contextual_links: --- -Reports in Arcus by Testsigma provide dynamic, visual insights into test execution status, progress, and defect tracking. This article discusses how to view and interpret different sections of a report. +Reports in Test Management by Testsigma provide dynamic, visual insights into test execution status, progress, and defect tracking. This article discusses how to view and interpret different sections of a report. --- diff --git a/src/pages/docs/arcus/settings/api-keys.md b/src/pages/docs/test-management/settings/api-keys.md similarity index 64% rename from src/pages/docs/arcus/settings/api-keys.md rename to src/pages/docs/test-management/settings/api-keys.md index a24a566..7a567e2 100644 --- a/src/pages/docs/arcus/settings/api-keys.md +++ b/src/pages/docs/test-management/settings/api-keys.md @@ -16,11 +16,11 @@ contextual_links:
-**Securely connect and automate with API Keys in Arcus by Testsigma.** +**Securely connect and automate with API Keys in Test Management by Testsigma.** --- -You can generate API Keys in Arcus by Testsigma to automate tasks such as creating projects, test cases, test runs, and test plans, as well as executing them. This article discusses how to generate API keys in Arcus by Testsigma. +You can generate API Keys in Test Management by Testsigma to automate tasks such as creating projects, test cases, test runs, and test plans, as well as executing them. This article discusses how to generate API keys in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/settings/audit-logs.md b/src/pages/docs/test-management/settings/audit-logs.md similarity index 76% rename from src/pages/docs/arcus/settings/audit-logs.md rename to src/pages/docs/test-management/settings/audit-logs.md index d5d8cc9..9c784cc 100644 --- a/src/pages/docs/arcus/settings/audit-logs.md +++ b/src/pages/docs/test-management/settings/audit-logs.md @@ -1,7 +1,7 @@ --- title: 'Audit Logs: Complete Record of Activities' -page_title: 'Audit Logs in Arcus by Testsigma' -metadesc: 'Track and export all user actions in Arcus by Testsigma with Audit Logs. Monitor activity, ensure accountability, and support security and compliance reviews.' +page_title: 'Audit Logs in Test Management by Testsigma' +metadesc: 'Track and export all user actions in Test Management by Testsigma with Audit Logs. Monitor activity, ensure accountability, and support security and compliance reviews.' noindex: false order: 12.6 page_id: 'audit-logs-in-testsigma-test-management' @@ -26,7 +26,7 @@ contextual_links: --- -Audit logs provide a complete record of all key activities in your Arcus by Testsigma account. They capture every user action, including changes to test assets and account access events, and store them as immutable entries. Administrators can use audit logs to monitor account usage, investigate security incidents, and ensure accountability across the organization. This article discusses Audit Logs in Arcus by Testsigma. +Audit logs provide a complete record of all key activities in your Test Management by Testsigma account. They capture every user action, including changes to test assets and account access events, and store them as immutable entries. Administrators can use audit logs to monitor account usage, investigate security incidents, and ensure accountability across the organization. This article discusses Audit Logs in Test Management by Testsigma. --- @@ -51,7 +51,7 @@ Audit logs provide a complete record of all key activities in your Arcus by Test 3. Each log entry includes the following details: ![Log Entries](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Log_Entries_TMS.png) - **Time**: Date and time when the action occurred. - - **Event Type**: The entity type in Arcus by Testsigma. + - **Event Type**: The entity type in Test Management by Testsigma. - **Action**: The action type. - **Project**: The project where the change was made. - **User**: The user who performed the action. @@ -65,7 +65,7 @@ You can narrow down audit log results using the following filters: ![Filters in Audit Logs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Filters_In_Audit_Logs_TMS.png) -1. **Event Type**: Displays logs for a specific entity in Arcus by Testsigma account. +1. **Event Type**: Displays logs for a specific entity in Test Management by Testsigma account. 2. **Action**: Filters logs by the type of activity performed. diff --git a/src/pages/docs/arcus/settings/custom-fields.md b/src/pages/docs/test-management/settings/custom-fields.md similarity index 74% rename from src/pages/docs/arcus/settings/custom-fields.md rename to src/pages/docs/test-management/settings/custom-fields.md index 49ceaac..c7abfd9 100644 --- a/src/pages/docs/arcus/settings/custom-fields.md +++ b/src/pages/docs/test-management/settings/custom-fields.md @@ -1,7 +1,7 @@ --- title: 'Manage Custom Fields' page_title: 'Manage Custom Fields in Test Management' -metadesc: 'Create and manage custom fields in Arcus by Testsigma to add specific details/additional details and filter tests efficiently in your test management workflow' +metadesc: 'Create and manage custom fields in Test Management by Testsigma to add specific details/additional details and filter tests efficiently in your test management workflow' noindex: false order: 12.2 page_id: 'custom-fields-in-testsigma-test-management' @@ -32,13 +32,13 @@ contextual_links: --- -In Arcus by Testsigma, you can create custom fields to add additional, project-specific information to your test cases. These fields help you track attributes beyond the default properties. After creating a custom field, you can add it to test cases and use it to filter and locate specific test cases efficiently. This article discusses how to create a custom field, add it to test cases, and filter test cases using custom field values. +In Test Management by Testsigma, you can create custom fields to add additional, project-specific information to your test cases. These fields help you track attributes beyond the default properties. After creating a custom field, you can add it to test cases and use it to filter and locate specific test cases efficiently. This article discusses how to create a custom field, add it to test cases, and filter test cases using custom field values. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/). +> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/). --- diff --git a/src/pages/docs/arcus/settings/labels.md b/src/pages/docs/test-management/settings/labels.md similarity index 77% rename from src/pages/docs/arcus/settings/labels.md rename to src/pages/docs/test-management/settings/labels.md index 8510d77..2537d6a 100644 --- a/src/pages/docs/arcus/settings/labels.md +++ b/src/pages/docs/test-management/settings/labels.md @@ -1,7 +1,7 @@ --- title: 'Manage Labels' -page_title: 'Manage Labels in Arcus by Testsigma' -metadesc: 'Organize test cases and runs using labels in Arcus by Testsigma. Create, edit, or delete labels to filter, group, and manage tests efficiently in your test management' +page_title: 'Manage Labels in Test Management by Testsigma' +metadesc: 'Organize test cases and runs using labels in Test Management by Testsigma. Create, edit, or delete labels to filter, group, and manage tests efficiently in your test management' noindex: false order: 12.3 page_id: 'manage-labels-testsigma-test-management' @@ -35,13 +35,13 @@ Labels help you organize your test cases and test runs, making it easier to filt - Edit existing labels to refine test organization as requirements develop. - Delete labels you no longer need to keep your test suite clean. -This article discusses managing labels in Arcus by Testsigma. +This article discusses managing labels in Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see Projects. +> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see Projects. --- diff --git a/src/pages/docs/arcus/settings/manage-access.md b/src/pages/docs/test-management/settings/manage-access.md similarity index 83% rename from src/pages/docs/arcus/settings/manage-access.md rename to src/pages/docs/test-management/settings/manage-access.md index 73421c8..0be0143 100644 --- a/src/pages/docs/arcus/settings/manage-access.md +++ b/src/pages/docs/test-management/settings/manage-access.md @@ -25,11 +25,11 @@ contextual_links:
-**Learn how admins in Arcus by Testsigma can grant and revoke temporary support access for issue diagnosis and resolution.** +**Learn how admins in Test Management by Testsigma can grant and revoke temporary support access for issue diagnosis and resolution.** --- -Admin in the Arcus by Testsigma account can grant temporary access to the Testsigma Support team for diagnosing and resolving support related issues. This article discusses how to authorize and revoke support access. +Admin in the Test Management by Testsigma account can grant temporary access to the Testsigma Support team for diagnosing and resolving support related issues. This article discusses how to authorize and revoke support access. --- diff --git a/src/pages/docs/arcus/settings/manage-properties.md b/src/pages/docs/test-management/settings/manage-properties.md similarity index 91% rename from src/pages/docs/arcus/settings/manage-properties.md rename to src/pages/docs/test-management/settings/manage-properties.md index b2cc28f..7d730cf 100644 --- a/src/pages/docs/arcus/settings/manage-properties.md +++ b/src/pages/docs/test-management/settings/manage-properties.md @@ -26,13 +26,13 @@ contextual_links: --- -In the Manage Properties section, you can edit the default values for Test Case Priority, Automation Type, Test Case Status, and Test Case Type. The system uses these values when you create new test cases. This article discusses managing test case properties in Arcus by Testsigma. +In the Manage Properties section, you can edit the default values for Test Case Priority, Automation Type, Test Case Status, and Test Case Type. The system uses these values when you create new test cases. This article discusses managing test case properties in Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see Projects. +> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see Projects. --- diff --git a/src/pages/docs/arcus/settings/notifications/email.md b/src/pages/docs/test-management/settings/notifications/email.md similarity index 88% rename from src/pages/docs/arcus/settings/notifications/email.md rename to src/pages/docs/test-management/settings/notifications/email.md index 62fd0a8..a92bdb5 100644 --- a/src/pages/docs/arcus/settings/notifications/email.md +++ b/src/pages/docs/test-management/settings/notifications/email.md @@ -33,13 +33,13 @@ contextual_links: --- -Arcus by Testsigma allows you to configure custom email notifications for various test entities. Email notifications help teams stay informed about key events such as assignments, status changes, and review updates. This article discusses customizing email notifications in Arcus by Testsigma. +Test Management by Testsigma allows you to configure custom email notifications for various test entities. Email notifications help teams stay informed about key events such as assignments, status changes, and review updates. This article discusses customizing email notifications in Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that you are added as a user in Arcus by Testsigma. +> Before you begin, ensure that you are added as a user in Test Management by Testsigma. --- @@ -101,7 +101,7 @@ Send daily summary email for test plan progress 5. Click **Save** to apply the changes. [[info | **NOTE**:]] -| To send notifications from your own email address, ensure SMTP is configured. For more information, see [SMTP Configuration in Arcus by Testsigma](https://testsigma.com/docs/test-management/settings/smtp-configuration/). +| To send notifications from your own email address, ensure SMTP is configured. For more information, see [SMTP Configuration in Test Management by Testsigma](https://testsigma.com/docs/test-management/settings/smtp-configuration/). --- diff --git a/src/pages/docs/arcus/settings/notifications/microsoft-teams.md b/src/pages/docs/test-management/settings/notifications/microsoft-teams.md similarity index 92% rename from src/pages/docs/arcus/settings/notifications/microsoft-teams.md rename to src/pages/docs/test-management/settings/notifications/microsoft-teams.md index 033a7bb..5330004 100644 --- a/src/pages/docs/arcus/settings/notifications/microsoft-teams.md +++ b/src/pages/docs/test-management/settings/notifications/microsoft-teams.md @@ -33,7 +33,7 @@ contextual_links: --- -Arcus by Testsigma allows you to configure Microsoft Teams notifications for various test entities. These notifications help teams stay aligned with testing activities by delivering real-time updates within Teams channels. This article discusses setting up and customizing Microsoft Teams notifications in Arcus by Testsigma. +Test Management by Testsigma allows you to configure Microsoft Teams notifications for various test entities. These notifications help teams stay aligned with testing activities by delivering real-time updates within Teams channels. This article discusses setting up and customizing Microsoft Teams notifications in Test Management by Testsigma. [[info | **NOTE**:]] | Authorize the integration using a separate Microsoft account designated only for setup. The account used for authorization will not receive notifications due to a limitation in Microsoft Teams. diff --git a/src/pages/docs/arcus/settings/notifications/overview.md b/src/pages/docs/test-management/settings/notifications/overview.md similarity index 76% rename from src/pages/docs/arcus/settings/notifications/overview.md rename to src/pages/docs/test-management/settings/notifications/overview.md index 531a285..045c7a2 100644 --- a/src/pages/docs/arcus/settings/notifications/overview.md +++ b/src/pages/docs/test-management/settings/notifications/overview.md @@ -1,7 +1,7 @@ --- title: 'Overview: Set Up Notifications' page_title: 'Overview: Set Up Notifications' -metadesc: 'Arcus by Testsigma allows you to integrate with Slack & Microsoft Teams and configure custom notifications for various test entities.' +metadesc: 'Test Management by Testsigma allows you to integrate with Slack & Microsoft Teams and configure custom notifications for various test entities.' noindex: false order: 12.81 page_id: 'overview-of-setting-up-notifications' @@ -26,7 +26,7 @@ contextual_links: --- -Arcus by Testsigma allows you to integrate with Slack and Microsoft Teams and configure custom notifications for various test entities. Notifications help teams stay aligned with ongoing testing activities by alerting users about key events such as assignments, status changes, and review updates. This article discusses setting up notifications in Arcus by Testsigma. +Test Management by Testsigma allows you to integrate with Slack and Microsoft Teams and configure custom notifications for various test entities. Notifications help teams stay aligned with ongoing testing activities by alerting users about key events such as assignments, status changes, and review updates. This article discusses setting up notifications in Test Management by Testsigma. --- @@ -76,7 +76,7 @@ Send notification when a test plan is completed Send daily summary notification for active test plans [[info | **NOTE**:]] -| Arcus by Testsigma allows you to configure notifications for each entity and enable or disable them based on your preferences. +| Test Management by Testsigma allows you to configure notifications for each entity and enable or disable them based on your preferences. | ![Toggles](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Notification_Toggles.png) --- \ No newline at end of file diff --git a/src/pages/docs/arcus/settings/notifications/slack.md b/src/pages/docs/test-management/settings/notifications/slack.md similarity index 92% rename from src/pages/docs/arcus/settings/notifications/slack.md rename to src/pages/docs/test-management/settings/notifications/slack.md index bb48e82..cc4cee9 100644 --- a/src/pages/docs/arcus/settings/notifications/slack.md +++ b/src/pages/docs/test-management/settings/notifications/slack.md @@ -33,7 +33,7 @@ contextual_links: --- -Arcus by Testsigma allows you to configure Slack notifications for various test entities. Slack notifications help teams stay informed about assignments, reviews, and status updates directly within their Slack workspace. This article discusses setting up and customizing Slack notifications in Arcus by Testsigma. +Test Management by Testsigma allows you to configure Slack notifications for various test entities. Slack notifications help teams stay informed about assignments, reviews, and status updates directly within their Slack workspace. This article discusses setting up and customizing Slack notifications in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/settings/smtp-configuration.md b/src/pages/docs/test-management/settings/smtp-configuration.md similarity index 89% rename from src/pages/docs/arcus/settings/smtp-configuration.md rename to src/pages/docs/test-management/settings/smtp-configuration.md index a4a0e1c..975f1dd 100644 --- a/src/pages/docs/arcus/settings/smtp-configuration.md +++ b/src/pages/docs/test-management/settings/smtp-configuration.md @@ -1,7 +1,7 @@ --- -title: 'SMTP Configuration in Arcus by Testsigma' -page_title: 'SMTP Configuration in Arcus by Testsigma' -metadesc: 'Configuring SMTP allows your organization to send email notifications from your own authenticated email address | Learn configuring SMTP in Arcus by Testsigma' +title: 'SMTP Configuration in Test Management by Testsigma' +page_title: 'SMTP Configuration in Test Management by Testsigma' +metadesc: 'Configuring SMTP allows your organization to send email notifications from your own authenticated email address | Learn configuring SMTP in Test Management by Testsigma' noindex: false order: 12.7 page_id: 'smtp-configuration' @@ -26,7 +26,7 @@ contextual_links: --- -Configuring Simple Mail Transfer Protocol (SMTP) allows your organization to send email notifications from your own authenticated email address instead of Testsigma’s default sender. This ensures improved branding, deliverability, and security for automated notifications. This article discusses configuring SMTP in Arcus by Testsigma. +Configuring Simple Mail Transfer Protocol (SMTP) allows your organization to send email notifications from your own authenticated email address instead of Testsigma’s default sender. This ensures improved branding, deliverability, and security for automated notifications. This article discusses configuring SMTP in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/step-groups/create-step-groups.md b/src/pages/docs/test-management/step-groups/create-step-groups.md similarity index 80% rename from src/pages/docs/arcus/step-groups/create-step-groups.md rename to src/pages/docs/test-management/step-groups/create-step-groups.md index b1e643b..aa2e163 100644 --- a/src/pages/docs/arcus/step-groups/create-step-groups.md +++ b/src/pages/docs/test-management/step-groups/create-step-groups.md @@ -1,7 +1,7 @@ --- title: 'Creating Step Groups' -page_title: 'Creating Step Groups in Arcus by Testsigma' -metadesc: 'Step Groups in Arcus by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Arcus by Testsigma' +page_title: 'Creating Step Groups in Test Management by Testsigma' +metadesc: 'Step Groups in Test Management by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Test Management by Testsigma' noindex: false order: 6.1 page_id: 'create-step-groups' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to create to reuse common steps across multiple test cases in Arcus by Testsigma.** +**Learn how to create to reuse common steps across multiple test cases in Test Management by Testsigma.** --- -Step Groups feature in Arcus by Testsigma enhances test case management by grouping repetitive test steps. Instead of manually adding steps across multiple test cases, you can link a Step Group to various test cases with common steps. This article discusses managing Step Groups in Arcus by Testsigma. +Step Groups feature in Test Management by Testsigma enhances test case management by grouping repetitive test steps. Instead of manually adding steps across multiple test cases, you can link a Step Group to various test cases with common steps. This article discusses managing Step Groups in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/step-groups/manage-step-groups.md b/src/pages/docs/test-management/step-groups/manage-step-groups.md similarity index 83% rename from src/pages/docs/arcus/step-groups/manage-step-groups.md rename to src/pages/docs/test-management/step-groups/manage-step-groups.md index 2e1ec5c..cebb37c 100644 --- a/src/pages/docs/arcus/step-groups/manage-step-groups.md +++ b/src/pages/docs/test-management/step-groups/manage-step-groups.md @@ -1,7 +1,7 @@ --- title: 'Managing Step Groups' -page_title: 'Managing Step Groups in Arcus by Testsigma' -metadesc: 'Step Groups in Arcus by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Arcus by Testsigma' +page_title: 'Managing Step Groups in Test Management by Testsigma' +metadesc: 'Step Groups in Test Management by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Test Management by Testsigma' noindex: false order: 6.2 page_id: 'create-step-groups' @@ -22,7 +22,7 @@ contextual_links:
-**Learn how to edit or delete Step Groups in Arcus by Testsigma.** +**Learn how to edit or delete Step Groups in Test Management by Testsigma.** --- diff --git a/src/pages/docs/arcus/test-capture/capture-logs.md b/src/pages/docs/test-management/test-capture/capture-logs.md similarity index 100% rename from src/pages/docs/arcus/test-capture/capture-logs.md rename to src/pages/docs/test-management/test-capture/capture-logs.md diff --git a/src/pages/docs/arcus/test-capture/install-and-configure.md b/src/pages/docs/test-management/test-capture/install-and-configure.md similarity index 91% rename from src/pages/docs/arcus/test-capture/install-and-configure.md rename to src/pages/docs/test-management/test-capture/install-and-configure.md index aea8484..e5d58ba 100644 --- a/src/pages/docs/arcus/test-capture/install-and-configure.md +++ b/src/pages/docs/test-management/test-capture/install-and-configure.md @@ -1,7 +1,7 @@ --- title: 'Install & Configure Test Capture' page_title: 'Install & Configure Test Capture Extension' -metadesc: 'Learn how to install, author, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Arcus by Testsigma' +metadesc: 'Learn how to install, author, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Test Management by Testsigma' noindex: false order: 9.2 page_id: 'install-test-capture-extension' @@ -13,8 +13,8 @@ contextual_links: name: 'Install Test Capture Extension' url: '#install-test-capture-extension' - type: link - name: 'Install from Arcus by Testsigma' - url: '#install-from-arcus-by-testsigma' + name: 'Install from Test Management by Testsigma' + url: '#install-from-test-management-by-testsigma' - type: link name: 'Install from Chrome Web Store' url: '#install-from-chrome-web-store' @@ -34,17 +34,17 @@ contextual_links: --- -Installing, authorizing, and configuring the Test Capture Chrome extension is required before you can execute tests and capture logs during manual execution. This article discusses setting up the extension so it works correctly with Arcus by Testsigma. +Installing, authorizing, and configuring the Test Capture Chrome extension is required before you can execute tests and capture logs during manual execution. This article discusses setting up the extension so it works correctly with Test Management by Testsigma. --- ## **Install Test Capture Extension** -You can install the extension directly from **Arcus by Testsigma** or from the **Chrome Web Store**. +You can install the extension directly from **Test Management by Testsigma** or from the **Chrome Web Store**.
-## **Install from Arcus by Testsigma** +## **Install from Test Management by Testsigma** 1. From the left navigation bar, go to **Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Test_Runs_for_Capture.png) @@ -83,7 +83,7 @@ You can install the extension directly from **Arcus by Testsigma** or from the * ## **Authorize the Extension** -After installation, the extension must be authorized to connect with Arcus by Testsigma. +After installation, the extension must be authorized to connect with Test Management by Testsigma. 1. Open a test run. @@ -92,7 +92,7 @@ After installation, the extension must be authorized to connect with Arcus by Te 3. In the **Test Capture** dialog, click **Login to Test Capture**. ![Login to Test Capture](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Login_to_Test_Capture.png) -4. You are redirected to the **Arcus by Testsigma** authorization page. +4. You are redirected to the **Test Management by Testsigma** authorization page. 5. Click **Authorize Extension**. ![Authorize Extension](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Authorize_Capture_Extension.png) diff --git a/src/pages/docs/arcus/test-capture/overview.md b/src/pages/docs/test-management/test-capture/overview.md similarity index 81% rename from src/pages/docs/arcus/test-capture/overview.md rename to src/pages/docs/test-management/test-capture/overview.md index f96c040..4ff5a12 100644 --- a/src/pages/docs/arcus/test-capture/overview.md +++ b/src/pages/docs/test-management/test-capture/overview.md @@ -1,7 +1,7 @@ --- title: 'Overview: Test Capture' -page_title: 'Overview of Test Capture in Arcus by Testsigma' -metadesc: 'Test Capture runs alongside manual test execution. This article provides an overview of Test Capture in Arcus by Testsigma.' +page_title: 'Overview of Test Capture in Test Management by Testsigma' +metadesc: 'Test Capture runs alongside manual test execution. This article provides an overview of Test Capture in Test Management by Testsigma.' noindex: false order: 9.1 page_id: 'test-capture-in-testsigma-test-management' @@ -31,7 +31,7 @@ contextual_links: --- -Test Capture feature in Arcus by Testsigma that runs alongside manual test execution. It automatically captures screen recordings, video logs, and network logs during testing, removing the need to manually record or attach logs after execution. All captured logs are automatically linked to the original test run, giving developers the visual and diagnostic context needed to investigate and resolve issues. This article provides an overview of Test Capture in Test Management. +Test Capture feature in Test Management by Testsigma that runs alongside manual test execution. It automatically captures screen recordings, video logs, and network logs during testing, removing the need to manually record or attach logs after execution. All captured logs are automatically linked to the original test run, giving developers the visual and diagnostic context needed to investigate and resolve issues. This article provides an overview of Test Capture in Test Management. --- diff --git a/src/pages/docs/arcus/test-cases/clone-test-cases.md b/src/pages/docs/test-management/test-cases/clone-test-cases.md similarity index 92% rename from src/pages/docs/arcus/test-cases/clone-test-cases.md rename to src/pages/docs/test-management/test-cases/clone-test-cases.md index 7be45c1..29bfd74 100644 --- a/src/pages/docs/arcus/test-cases/clone-test-cases.md +++ b/src/pages/docs/test-management/test-cases/clone-test-cases.md @@ -1,7 +1,7 @@ --- -title: 'Clone Test Case in Arcus by Testsigma' -page_title: 'Clone Test Case in Arcus by Testsigma' -metadesc: 'Clone test cases to quickly create reusable copies without impacting the original version | Learn how to clone test cases in Arcus by Testsigma' +title: 'Clone Test Case in Test Management by Testsigma' +page_title: 'Clone Test Case in Test Management by Testsigma' +metadesc: 'Clone test cases to quickly create reusable copies without impacting the original version | Learn how to clone test cases in Test Management by Testsigma' noindex: false order: 3.8 page_id: 'clone-tests-in-test-management' @@ -28,7 +28,7 @@ contextual_links: --- -Cloning test cases allows you to create an exact copy of an existing test case for reuse within the same project or across different projects. All field values are copied at the time of cloning, and any updates made to the original test case do not affect the cloned version. This article discusses cloning test cases in Arcus by Testsigma. +Cloning test cases allows you to create an exact copy of an existing test case for reuse within the same project or across different projects. All field values are copied at the time of cloning, and any updates made to the original test case do not affect the cloned version. This article discusses cloning test cases in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-cases/comment-in-test-cases.md b/src/pages/docs/test-management/test-cases/comment-in-test-cases.md similarity index 95% rename from src/pages/docs/arcus/test-cases/comment-in-test-cases.md rename to src/pages/docs/test-management/test-cases/comment-in-test-cases.md index e169253..eee0aa4 100644 --- a/src/pages/docs/arcus/test-cases/comment-in-test-cases.md +++ b/src/pages/docs/test-management/test-cases/comment-in-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Comment in Test Cases' -page_title: 'Comment in Test Cases in Arcus by Testsigma' -metadesc: 'Use comments to collaborate instantly on test cases by sharing feedback, raising issues, & tracking discussions in one place | Comment in Test Cases in Arcus by Testsigma' +page_title: 'Comment in Test Cases in Test Management by Testsigma' +metadesc: 'Use comments to collaborate instantly on test cases by sharing feedback, raising issues, & tracking discussions in one place | Comment in Test Cases in Test Management by Testsigma' noindex: false order: 3.9 page_id: 'comment-in-test-cases-in-test-management' diff --git a/src/pages/docs/arcus/test-cases/customize-test-case-list-view.md b/src/pages/docs/test-management/test-cases/customize-test-case-list-view.md similarity index 66% rename from src/pages/docs/arcus/test-cases/customize-test-case-list-view.md rename to src/pages/docs/test-management/test-cases/customize-test-case-list-view.md index 58de199..ef87f90 100644 --- a/src/pages/docs/arcus/test-cases/customize-test-case-list-view.md +++ b/src/pages/docs/test-management/test-cases/customize-test-case-list-view.md @@ -1,7 +1,7 @@ --- title: 'Customize Test Case List View' -page_title: 'Customize Test Case List View in Arcus by Testsigma' -metadesc: 'This article discusses customizing Test Case List View in Arcus by Testsigma | Customizing test case list view helps show only the columns that are relevant' +page_title: 'Customize Test Case List View in Test Management by Testsigma' +metadesc: 'This article discusses customizing Test Case List View in Test Management by Testsigma | Customizing test case list view helps show only the columns that are relevant' noindex: false order: 3.5 page_id: 'customize-test-cases-list-view-in-test-management' @@ -25,13 +25,13 @@ contextual_links: --- -The customize test case list view feature in Arcus by Testsigma lets you select the columns that matter most to you. This helps you focus on the specific data you need, beyond the default view. This article discusses steps to customize the test case list view. +The customize test case list view feature in Test Management by Testsigma lets you select the columns that matter most to you. This helps you focus on the specific data you need, beyond the default view. This article discusses steps to customize the test case list view. --- > ## **Prerequisites** > -> Before you begin, ensure that you have test cases available in Arcus by Testsigma. +> Before you begin, ensure that you have test cases available in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-cases/filter-test-cases.md b/src/pages/docs/test-management/test-cases/filter-test-cases.md similarity index 90% rename from src/pages/docs/arcus/test-cases/filter-test-cases.md rename to src/pages/docs/test-management/test-cases/filter-test-cases.md index 6ecec94..f4d9d44 100644 --- a/src/pages/docs/arcus/test-cases/filter-test-cases.md +++ b/src/pages/docs/test-management/test-cases/filter-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Test Case Filters' -page_title: 'Test Case Filters in Arcus by Testsigma' -metadesc: 'This article discusses Test Case Filters in Arcus by Testsigma | Filtering test cases involves in filtering tests based on priority, type, status, and more' +page_title: 'Test Case Filters in Test Management by Testsigma' +metadesc: 'This article discusses Test Case Filters in Test Management by Testsigma | Filtering test cases involves in filtering tests based on priority, type, status, and more' noindex: false order: 3.4 page_id: 'test-cases-filters-in-testsigma-test-management' @@ -35,7 +35,7 @@ Filtering test cases helps you find specific test cases based on properties such > ## **Prerequisites** > -> Before you begin, ensure that you have test cases available in Arcus by Testsigma. +> Before you begin, ensure that you have test cases available in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-cases/folders.md b/src/pages/docs/test-management/test-cases/folders.md similarity index 77% rename from src/pages/docs/arcus/test-cases/folders.md rename to src/pages/docs/test-management/test-cases/folders.md index 98cde63..8366abe 100644 --- a/src/pages/docs/arcus/test-cases/folders.md +++ b/src/pages/docs/test-management/test-cases/folders.md @@ -1,6 +1,6 @@ --- title: 'Folders: Organizing Test Cases' -page_title: 'Getting Started with Arcus by Testsigma' +page_title: 'Getting Started with Test Management by Testsigma' metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' noindex: false order: 3.1 @@ -32,14 +32,14 @@ contextual_links: --- -Organizing test cases is easier with folders within a project. Arcus by Testsigma allows you to create a hierarchical folder structure, where subfolders nest under parent folders for better organization. Each folder displays cumulative test case counts, giving you a clear view of the total test cases within a project. This article discusses creating, managing, and navigating test case folders efficiently. -Arcus by Testsigma +Organizing test cases is easier with folders within a project. Test Management by Testsigma allows you to create a hierarchical folder structure, where subfolders nest under parent folders for better organization. Each folder displays cumulative test case counts, giving you a clear view of the total test cases within a project. This article discusses creating, managing, and navigating test case folders efficiently. +Test Management by Testsigma --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see Projects +> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see Projects --- diff --git a/src/pages/docs/arcus/test-cases/manage-test-cases.md b/src/pages/docs/test-management/test-cases/manage-test-cases.md similarity index 94% rename from src/pages/docs/arcus/test-cases/manage-test-cases.md rename to src/pages/docs/test-management/test-cases/manage-test-cases.md index 71e2fdf..1057c5d 100644 --- a/src/pages/docs/arcus/test-cases/manage-test-cases.md +++ b/src/pages/docs/test-management/test-cases/manage-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Test Cases: The Core of Testing' -page_title: 'Test Cases in Arcus by Testsigma' -metadesc: 'This article discusses managing test cases in Arcus by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' +page_title: 'Test Cases in Test Management by Testsigma' +metadesc: 'This article discusses managing test cases in Test Management by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' noindex: false order: 3.2 page_id: 'test-cases-in-testsigma-test-management' @@ -37,7 +37,7 @@ contextual_links:
-**Learn how to create, organize, and maintain test cases in Arcus by Testsigma.** +**Learn how to create, organize, and maintain test cases in Test Management by Testsigma.** --- diff --git a/src/pages/docs/arcus/test-cases/review-management.md b/src/pages/docs/test-management/test-cases/review-management.md similarity index 83% rename from src/pages/docs/arcus/test-cases/review-management.md rename to src/pages/docs/test-management/test-cases/review-management.md index 077eb95..334d05c 100644 --- a/src/pages/docs/arcus/test-cases/review-management.md +++ b/src/pages/docs/test-management/test-cases/review-management.md @@ -1,7 +1,7 @@ --- -title: 'Review Management in Arcus by Testsigma' -page_title: 'Review Management in Arcus by Testsigma' -metadesc: 'Review Management adds a structured approval workflow that helps teams maintain high-quality, reliable test cases | Learn Review Management in Arcus by Testsigma' +title: 'Review Management in Test Management by Testsigma' +page_title: 'Review Management in Test Management by Testsigma' +metadesc: 'Review Management adds a structured approval workflow that helps teams maintain high-quality, reliable test cases | Learn Review Management in Test Management by Testsigma' noindex: false order: 3.7 page_id: 'review-management-in-test-management' @@ -34,13 +34,13 @@ contextual_links: --- -Review Management helps teams maintain high-quality test cases by adding a structured review workflow to Arcus by Testsigma. QA members can submit their test cases for review, and designated reviewers can approve them or return them for rework with comments. This ensures that test cases are accurate, consistent, and aligned with project standards. This article discusses Review Management in Arcus by Testsigma. +Review Management helps teams maintain high-quality test cases by adding a structured review workflow to Test Management by Testsigma. QA members can submit their test cases for review, and designated reviewers can approve them or return them for rework with comments. This ensures that test cases are accurate, consistent, and aligned with project standards. This article discusses Review Management in Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure required team members are invited & added to Arcus by Testsigma. +> Before you begin, ensure required team members are invited & added to Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-cases/run-history.md b/src/pages/docs/test-management/test-cases/run-history.md similarity index 89% rename from src/pages/docs/arcus/test-cases/run-history.md rename to src/pages/docs/test-management/test-cases/run-history.md index fc8c363..3545e4c 100644 --- a/src/pages/docs/arcus/test-cases/run-history.md +++ b/src/pages/docs/test-management/test-cases/run-history.md @@ -1,7 +1,7 @@ --- title: 'View Run History for a Test Case' -page_title: 'View Run History for a Test Case in Arcus by Testsigma' -metadesc: 'View the execution history of a test case across all test runs to track stability, ownership, and trends in Arcus by Testsigma.' +page_title: 'View Run History for a Test Case in Test Management by Testsigma' +metadesc: 'View the execution history of a test case across all test runs to track stability, ownership, and trends in Test Management by Testsigma.' noindex: false order: 3.91 page_id: 'run-history-in-test-cases-in-test-management' @@ -26,7 +26,7 @@ contextual_links: --- -Run History at the test case level provides a list of all executions of that test case across associated test runs. It helps teams analyze stability, audit execution ownership, and quickly trace trends without navigating into individual test runs. This article discusses Run History for a Test Case in Arcus by Testsigma. +Run History at the test case level provides a list of all executions of that test case across associated test runs. It helps teams analyze stability, audit execution ownership, and quickly trace trends without navigating into individual test runs. This article discusses Run History for a Test Case in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-cases/test-case-templates.md b/src/pages/docs/test-management/test-cases/test-case-templates.md similarity index 87% rename from src/pages/docs/arcus/test-cases/test-case-templates.md rename to src/pages/docs/test-management/test-cases/test-case-templates.md index 65ae6ac..0c3ad40 100644 --- a/src/pages/docs/arcus/test-cases/test-case-templates.md +++ b/src/pages/docs/test-management/test-cases/test-case-templates.md @@ -1,7 +1,7 @@ --- title: 'Test Case Templates' -page_title: 'Test Case Templates in Arcus by Testsigma' -metadesc: 'This article discusses Test Case Templates in Arcus by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' +page_title: 'Test Case Templates in Test Management by Testsigma' +metadesc: 'This article discusses Test Case Templates in Test Management by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' noindex: false order: 3.3 page_id: 'test-cases-templates-in-testsigma-test-management' @@ -23,7 +23,7 @@ contextual_links: --- -Arcus by Testsigma tool allows you to create test cases using two templates: +Test Management by Testsigma tool allows you to create test cases using two templates: ### 1. **Documentation Template** @@ -33,7 +33,7 @@ You can use the **Documentation Template** to create simple tests with basic pre You can use **Steps Template** when a more granular approach is necessary, breaking down each action and expected results. -Both templates allow you to attach files up to 25 MB, which enhances test documentation with relevant files for better clarity and context. This article discusses Test Case Templates in Arcus by Testsigma. +Both templates allow you to attach files up to 25 MB, which enhances test documentation with relevant files for better clarity and context. This article discusses Test Case Templates in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-cases/versions.md b/src/pages/docs/test-management/test-cases/versions.md similarity index 95% rename from src/pages/docs/arcus/test-cases/versions.md rename to src/pages/docs/test-management/test-cases/versions.md index c9abbda..882c07c 100644 --- a/src/pages/docs/arcus/test-cases/versions.md +++ b/src/pages/docs/test-management/test-cases/versions.md @@ -1,6 +1,6 @@ --- title: 'Versions: See What is Changed in a Test Case' -page_title: 'Versions in Arcus by Testsigma' +page_title: 'Versions in Test Management by Testsigma' metadesc: 'View the changes made to a test case using Versions. It also lets you compare the current version of a test case with any previous version to clearly see the differences' noindex: false order: 3.6 @@ -31,7 +31,7 @@ contextual_links: --- -You can view the changes made to a test case from Versions. Versions let you compare the current version of a test case with any previous version to clearly identify the differences. This article discusses how to view and compare versions in Arcus by Testsigma. +You can view the changes made to a test case from Versions. Versions let you compare the current version of a test case with any previous version to clearly identify the differences. This article discusses how to view and compare versions in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-plans/manage-test-plans.md b/src/pages/docs/test-management/test-plans/manage-test-plans.md similarity index 89% rename from src/pages/docs/arcus/test-plans/manage-test-plans.md rename to src/pages/docs/test-management/test-plans/manage-test-plans.md index 79d85ed..dd10efe 100644 --- a/src/pages/docs/arcus/test-plans/manage-test-plans.md +++ b/src/pages/docs/test-management/test-plans/manage-test-plans.md @@ -1,7 +1,7 @@ --- title: 'Managing Test Plans' -page_title: 'Test Plans in Arcus by Testsigma' -metadesc: 'Organize and manage your testing with test plans in Arcus by Testsigma | Set the scope, goals, and schedules to run/track test plans clearly and efficiently.' +page_title: 'Test Plans in Test Management by Testsigma' +metadesc: 'Organize and manage your testing with test plans in Test Management by Testsigma | Set the scope, goals, and schedules to run/track test plans clearly and efficiently.' noindex: false order: 8.1 page_id: 'test-plans-in-testsigma-test-management' @@ -28,7 +28,7 @@ contextual_links:
-**Learn how to create, organize, and manage test plans in Arcus by Testsigma.** +**Learn how to create, organize, and manage test plans in Test Management by Testsigma.** --- diff --git a/src/pages/docs/arcus/test-plans/share-test-plans.md b/src/pages/docs/test-management/test-plans/share-test-plans.md similarity index 91% rename from src/pages/docs/arcus/test-plans/share-test-plans.md rename to src/pages/docs/test-management/test-plans/share-test-plans.md index e47f500..e1198c3 100644 --- a/src/pages/docs/arcus/test-plans/share-test-plans.md +++ b/src/pages/docs/test-management/test-plans/share-test-plans.md @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to generate public links to share test plans with external stakeholders in Arcus by Testsigma.** +**Learn how to generate public links to share test plans with external stakeholders in Test Management by Testsigma.** --- -You can share a test plan with anyone on the internet by generating a public link in Arcus by Testsigma. This allows external stakeholders without account access to view testing progress. +You can share a test plan with anyone on the internet by generating a public link in Test Management by Testsigma. This allows external stakeholders without account access to view testing progress. --- diff --git a/src/pages/docs/arcus/test-runs/create-test-runs.md b/src/pages/docs/test-management/test-runs/create-test-runs.md similarity index 92% rename from src/pages/docs/arcus/test-runs/create-test-runs.md rename to src/pages/docs/test-management/test-runs/create-test-runs.md index 0496d33..bae487a 100644 --- a/src/pages/docs/arcus/test-runs/create-test-runs.md +++ b/src/pages/docs/test-management/test-runs/create-test-runs.md @@ -1,7 +1,7 @@ --- title: 'Creating Test Runs' -page_title: 'Creating Test Runs in Arcus by Testsigma' -metadesc: 'Create test runs in Arcus by Testsigma by manually adding test cases, applying filters, or selecting all and ensure thorough testing of your applications' +page_title: 'Creating Test Runs in Test Management by Testsigma' +metadesc: 'Create test runs in Test Management by Testsigma by manually adding test cases, applying filters, or selecting all and ensure thorough testing of your applications' noindex: false order: 7.1 page_id: 'create-test-runs' @@ -31,11 +31,11 @@ contextual_links:
-**Learn how to create, organize & add status to the test runs in Arcus by Testsigma.** +**Learn how to create, organize & add status to the test runs in Test Management by Testsigma.** --- -Test runs ensure thorough testing of your applications. You can create test runs by adding test cases manually, using filters to dynamically include relevant test cases, or selecting all available test cases. Additionally, you can schedule, organize, and add status to the test runs. Effective test run management provides insights, drives continuous improvement, and enhances testing efficiency. This article discusses creating test runs in Arcus by Testsigma. +Test runs ensure thorough testing of your applications. You can create test runs by adding test cases manually, using filters to dynamically include relevant test cases, or selecting all available test cases. Additionally, you can schedule, organize, and add status to the test runs. Effective test run management provides insights, drives continuous improvement, and enhances testing efficiency. This article discusses creating test runs in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-runs/manage-test-runs.md b/src/pages/docs/test-management/test-runs/manage-test-runs.md similarity index 88% rename from src/pages/docs/arcus/test-runs/manage-test-runs.md rename to src/pages/docs/test-management/test-runs/manage-test-runs.md index 9ecc658..428e1bb 100644 --- a/src/pages/docs/arcus/test-runs/manage-test-runs.md +++ b/src/pages/docs/test-management/test-runs/manage-test-runs.md @@ -1,7 +1,7 @@ --- title: 'Managing Test Runs' -page_title: 'Managing Test Runs in Arcus by Testsigma' -metadesc: 'Manage test runs in Arcus by Testsigma by editing, cloning, closing, or deleting them to maintain organized and efficient test execution.' +page_title: 'Managing Test Runs in Test Management by Testsigma' +metadesc: 'Manage test runs in Test Management by Testsigma by editing, cloning, closing, or deleting them to maintain organized and efficient test execution.' noindex: false order: 7.2 page_id: 'create-test-runs' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to edit, clone, close, and delete test runs in Arcus by Testsigma.** +**Learn how to edit, clone, close, and delete test runs in Test Management by Testsigma.** --- -After creating a test run, you can manage it by editing its details, cloning it for reuse, closing it to prevent further modifications, or deleting it permanently. Editing lets you modify test run details, clone duplicates for future use, close locks it from further changes, and delete option removes the test run permanently. This article discusses managing test runs in Arcus by Testsigma. +After creating a test run, you can manage it by editing its details, cloning it for reuse, closing it to prevent further modifications, or deleting it permanently. Editing lets you modify test run details, clone duplicates for future use, close locks it from further changes, and delete option removes the test run permanently. This article discusses managing test runs in Test Management by Testsigma. --- diff --git a/src/pages/docs/arcus/test-runs/share-test-runs.md b/src/pages/docs/test-management/test-runs/share-test-runs.md similarity index 91% rename from src/pages/docs/arcus/test-runs/share-test-runs.md rename to src/pages/docs/test-management/test-runs/share-test-runs.md index a2e4f20..d366b11 100644 --- a/src/pages/docs/arcus/test-runs/share-test-runs.md +++ b/src/pages/docs/test-management/test-runs/share-test-runs.md @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to generate and share public links for test runs in Arcus by Testsigma.** +**Learn how to generate and share public links for test runs in Test Management by Testsigma.** --- -You can share a test run with anyone on the internet by generating a public link in Arcus by Testsigma. This is useful when you want external stakeholders without account access to view testing progress. +You can share a test run with anyone on the internet by generating a public link in Test Management by Testsigma. This is useful when you want external stakeholders without account access to view testing progress. --- diff --git a/src/pages/docs/arcus/test-runs/test-run-properties.md b/src/pages/docs/test-management/test-runs/test-run-properties.md similarity index 80% rename from src/pages/docs/arcus/test-runs/test-run-properties.md rename to src/pages/docs/test-management/test-runs/test-run-properties.md index 029f262..153fa1f 100644 --- a/src/pages/docs/arcus/test-runs/test-run-properties.md +++ b/src/pages/docs/test-management/test-runs/test-run-properties.md @@ -1,6 +1,6 @@ --- title: 'Test Run Properties' -page_title: 'Test Run Properties in Arcus by Testsigma' +page_title: 'Test Run Properties in Test Management by Testsigma' metadesc: 'Learn about test run properties in Testsigma Test Management. Structure, manage, and track test runs effectively to improve efficiency and ensure accurate reporting.' noindex: false order: 7.4 @@ -23,13 +23,13 @@ contextual_links: --- -Test run properties define the attributes that help teams structure, manage, and track test statuses. A well-organized test run improves efficiency and ensures accurate reporting, enabling teams to maintain quality. This article discusses test run properties in Arcus by Testsigma. +Test run properties define the attributes that help teams structure, manage, and track test statuses. A well-organized test run improves efficiency and ensures accurate reporting, enabling teams to maintain quality. This article discusses test run properties in Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that a project is created in Arcus by Testsigma and test cases are available for creating test runs. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/), [Test Cases](https://testsigma.com/docs/test-management/test-cases/manage-test-cases/) and [Test Runs](https://testsigma.com/docs/test-management/test-runs/create-test-runs/). +> Before you begin, ensure that a project is created in Test Management by Testsigma and test cases are available for creating test runs. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/), [Test Cases](https://testsigma.com/docs/test-management/test-cases/manage-test-cases/) and [Test Runs](https://testsigma.com/docs/test-management/test-runs/create-test-runs/). --- diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/automate-manual-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md similarity index 74% rename from src/pages/docs/arcus/testsigma-two-way-integration/automate-manual-test-cases.md rename to src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md index c4e7674..769b9d1 100644 --- a/src/pages/docs/arcus/testsigma-two-way-integration/automate-manual-test-cases.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Automate Manual Test Cases in Testsigma' -page_title: 'Automate Manual Test Cases from Arcus by Testsigma in Testsigma' -metadesc: 'Automate manual test cases from Arcus by Testsigma in Testsigma using Atto’s AI. Learn how to generate automated steps and begin Agentic Learning.' +page_title: 'Automate Manual Test Cases from Test Management by Testsigma in Testsigma' +metadesc: 'Automate manual test cases from Test Management by Testsigma in Testsigma using Atto’s AI. Learn how to generate automated steps and begin Agentic Learning.' noindex: false order: 11.4 page_id: 'automate-manual-test-cases-in-testsigma' @@ -28,17 +28,17 @@ contextual_links:
-**Automate manual test cases from Arcus by Testsigma in Testsigma using Atto’s AI.** +**Automate manual test cases from Test Management by Testsigma in Testsigma using Atto’s AI.** --- -You can automate manual test cases created in Arcus by Testsigma using Testsigma. Once you create a manual test case, click Automate with Atto’s AI in Arcus by Testsigma. Then select the Testsigma project, application, and version in which you want to automate the test case. The system creates a session in Atto’s Home for the selected project, where you can automate the test case using Atto. This article discusses the steps to automate manual test cases from Arcus by Testsigma in Testsigma. +You can automate manual test cases created in Test Management by Testsigma using Testsigma. Once you create a manual test case, click Automate with Atto’s AI in Test Management by Testsigma. Then select the Testsigma project, application, and version in which you want to automate the test case. The system creates a session in Atto’s Home for the selected project, where you can automate the test case using Atto. This article discusses the steps to automate manual test cases from Test Management by Testsigma in Testsigma. --- > ## **Prerequisites** > Before you begin, ensure that: -> - The Arcus by Testsigma integration with Testsigma is enabled. +> - The Test Management by Testsigma integration with Testsigma is enabled. > - Testsigma’s Live Editor is ready. --- diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/connect-testsigma.md b/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md similarity index 61% rename from src/pages/docs/arcus/testsigma-two-way-integration/connect-testsigma.md rename to src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md index 3d9bcbe..eade408 100644 --- a/src/pages/docs/arcus/testsigma-two-way-integration/connect-testsigma.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md @@ -1,7 +1,7 @@ --- -title: 'Testsigma Integration for Arcus by Testsigma' -page_title: 'Testsigma Integration for Arcus by Testsigma' -metadesc: 'Testsigma Integration with Arcus by Testsigma ensures complete visibility by synchronizing test coverage, execution results, and logs across manual & automated tests.' +title: 'Testsigma Integration for Test Management by Testsigma' +page_title: 'Testsigma Integration for Test Management by Testsigma' +metadesc: 'Testsigma Integration with Test Management by Testsigma ensures complete visibility by synchronizing test coverage, execution results, and logs across manual & automated tests.' noindex: false order: 11.1 page_id: 'testsigma-for-tms' @@ -16,8 +16,8 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Integrate Arcus by Testsigma with Testsigma' - url: '#integrate-arcus-by-testsigma-with-testsigma' + name: 'Integrate Test Management by Testsigma with Testsigma' + url: '#integrate-test-management-by-testsigma-with-testsigma' ---
@@ -26,7 +26,7 @@ contextual_links: --- -The integration between Testsigma and Arcus by Testsigma provides a unified view of both manual and automated testing. It links automated tests in Testsigma with their corresponding manual test cases in Arcus by Testsigma. +The integration between Testsigma and Test Management by Testsigma provides a unified view of both manual and automated testing. It links automated tests in Testsigma with their corresponding manual test cases in Test Management by Testsigma. This two-way synchronization ensures that execution results, logs, and screenshots are automatically updated in real time. The integration improves traceability, eliminates duplicate efforts, and provides complete visibility into test coverage and overall quality. @@ -35,7 +35,7 @@ This two-way synchronization ensures that execution results, logs, and screensho > ## **Prerequisites** > -> Before you begin, ensure you have an Enterprise plan for both Testsigma and Arcus by Testsigma. +> Before you begin, ensure you have an Enterprise plan for both Testsigma and Test Management by Testsigma. --- @@ -50,11 +50,11 @@ This two-way synchronization ensures that execution results, logs, and screensho --- -## **Integrate Arcus by Testsigma with Testsigma** +## **Integrate Test Management by Testsigma with Testsigma** -You can enable the integration either from Arcus by Testsigma or directly from Testsigma. +You can enable the integration either from Test Management by Testsigma or directly from Testsigma. -**a. Enable from Arcus by Testsigma** +**a. Enable from Test Management by Testsigma** 1. From the **Dashboard**, go to **Settings > Integrations**. @@ -67,8 +67,8 @@ You can enable the integration either from Arcus by Testsigma or directly from T 1. From the left navigation bar, go to **Settings > Integrations**. -2. Turn on the toggle next to Arcus by Testsigma. - ![Arcus by Testsigma Toggle](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/TMS_Toggle_In_Testsigma.png) +2. Turn on the toggle next to Test Management by Testsigma. + ![Test Management by Testsigma Toggle](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/TMS_Toggle_In_Testsigma.png) 3. The integration is now enabled successfully. diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/create-and-sync-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md similarity index 76% rename from src/pages/docs/arcus/testsigma-two-way-integration/create-and-sync-test-cases.md rename to src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md index 6fb882e..05cb6cb 100644 --- a/src/pages/docs/arcus/testsigma-two-way-integration/create-and-sync-test-cases.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Create & Sync Test Cases from Testsigma’s Atto’s Home' page_title: 'Create and Sync Test Cases from Testsigma’s Atto’s Home' -metadesc: 'Create & sync AI-generated test cases from Atto’s Home directly to Arcus by Testsigma. This article explains how to generate & sync Atto’s test cases into TMS.' +metadesc: 'Create & sync AI-generated test cases from Atto’s Home directly to Test Management by Testsigma. This article explains how to generate & sync Atto’s test cases into TMS.' noindex: false order: 11.5 page_id: 'create-and-sync-test-cases' @@ -22,18 +22,18 @@ contextual_links:
-**Create and sync AI-generated test cases from Atto’s Home directly to Arcus by Testsigma.** +**Create and sync AI-generated test cases from Atto’s Home directly to Test Management by Testsigma.** --- -You can sync newly generated test cases from Testsigma’s Atto’s Home to Arcus by Testsigma. Once the NLP steps are generated for AI-generated test cases in Atto’s Home, the system provides an option to create a new test case and sync with Arcus by Testsigma. This article discusses the two-way sync of AI-generated test cases between both systems. +You can sync newly generated test cases from Testsigma’s Atto’s Home to Test Management by Testsigma. Once the NLP steps are generated for AI-generated test cases in Atto’s Home, the system provides an option to create a new test case and sync with Test Management by Testsigma. This article discusses the two-way sync of AI-generated test cases between both systems. --- > ## **Prerequisites** > > Before you begin, ensure that: -> - The Arcus by Testsigma integration with Testsigma is enabled. +> - The Test Management by Testsigma integration with Testsigma is enabled. > - You have AI-generated test cases in Atto’s Home. --- @@ -69,10 +69,10 @@ You can sync newly generated test cases from Testsigma’s Atto’s Home to Arcu 8. Click the dropdown arrow next to **Accept**, and select **Accept & Sync with Testsigma TMS**. -9. In the **Sync with Arcus by Testsigma** dialog: +9. In the **Sync with Test Management by Testsigma** dialog: - Select a **Test Management** project and folder. - Click **Continue**. -10. The system creates a new test case in Arcus by Testsigma and links it to the Testsigma test case. +10. The system creates a new test case in Test Management by Testsigma and links it to the Testsigma test case. --- \ No newline at end of file diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/execute-test-plans.md b/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md similarity index 64% rename from src/pages/docs/arcus/testsigma-two-way-integration/execute-test-plans.md rename to src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md index 506c159..ab1b5e0 100644 --- a/src/pages/docs/arcus/testsigma-two-way-integration/execute-test-plans.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md @@ -1,7 +1,7 @@ --- -title: 'Execute Test Plans from Arcus by Testsigma' -page_title: 'Execute Test Plans from Arcus by Testsigma' -metadesc: 'You can execute test plans in Testsigma directly from Arcus by Testsigma | Learn how to execute test plans of Testsigma from Arcus by Testsigma.' +title: 'Execute Test Plans from Test Management by Testsigma' +page_title: 'Execute Test Plans from Test Management by Testsigma' +metadesc: 'You can execute test plans in Testsigma directly from Test Management by Testsigma | Learn how to execute test plans of Testsigma from Test Management by Testsigma.' noindex: false order: 11.7 page_id: 'execute-test-plans-in-testsigma' @@ -16,26 +16,26 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Execute a Linked Test Plan in Arcus by Testsigma' - url: '#execute-a-linked-test-plan-in-arcus-by-testsigma' + name: 'Execute a Linked Test Plan in Test Management by Testsigma' + url: '#execute-a-linked-test-plan-in-test-management-by-testsigma' - type: link - name: 'View Automated Reports in Arcus by Testsigma' - url: '#view-automated-reports-in-arcus-by-testsigma' + name: 'View Automated Reports in Test Management by Testsigma' + url: '#view-automated-reports-in-test-management-by-testsigma' ---
-**This integration lets you execute test plans in Testsigma from Arcus by Testsigma & automatically retrieves machine-level reports for each run.** +**This integration lets you execute test plans in Testsigma from Test Management by Testsigma & automatically retrieves machine-level reports for each run.** --- -You can execute test plans in Testsigma directly from Arcus by Testsigma. When you trigger an execution, Arcus by Testsigma creates a separate test run for each machine and imports machine-level reports, including the link to the result page. This article discusses executing Test Plans from Arcus by Testsigma. +You can execute test plans in Testsigma directly from Test Management by Testsigma. When you trigger an execution, Test Management by Testsigma creates a separate test run for each machine and imports machine-level reports, including the link to the result page. This article discusses executing Test Plans from Test Management by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that the test plans are linked between Arcus by Testsigma and Testsigma. +> Before you begin, ensure that the test plans are linked between Test Management by Testsigma and Testsigma. --- @@ -51,9 +51,9 @@ You can execute test plans in Testsigma directly from Arcus by Testsigma. When y --- -## **Execute a Linked Test Plan in Arcus by Testsigma** +## **Execute a Linked Test Plan in Test Management by Testsigma** -1. Create or open the test plan you want to execute in Arcus by Testsigma. +1. Create or open the test plan you want to execute in Test Management by Testsigma. 2. In the test plan details page, under **Testsigma Automated Test Plan**, click **Link a Test Plan** if the plan is not yet linked. @@ -64,7 +64,7 @@ You can execute test plans in Testsigma directly from Arcus by Testsigma. When y 4. After linking, click the **Play icon** next to the linked **Testsigma Automated Test Plan** to trigger execution. -2. After execution completes in Testsigma, Arcus by Testsigma automatically creates a test run for each machine with the associated test cases. +2. After execution completes in Testsigma, Test Management by Testsigma automatically creates a test run for each machine with the associated test cases. 3. Open the test run in the test plan to view execution details. The run includes links to the individual test case results pages for each executed test case. @@ -73,7 +73,7 @@ You can execute test plans in Testsigma directly from Arcus by Testsigma. When y --- -## **View Automated Reports in Arcus by Testsigma** +## **View Automated Reports in Test Management by Testsigma** 1. From the left navigation bar, go to **Test Plans**. diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md similarity index 78% rename from src/pages/docs/arcus/testsigma-two-way-integration/link-test-cases.md rename to src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md index 68eeb95..b49a3c7 100644 --- a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-cases.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md @@ -1,7 +1,7 @@ --- -title: 'Link Test Cases Between Arcus by Testsigma & Testsigma' -page_title: 'Link Test Cases Between Arcus by Testsigma & Testsigma' -metadesc: 'Two-way test case sync ensures consistent traceability & seamless alignment between Arcus by Testsigma and Testsigma.' +title: 'Link Test Cases Between Test Management by Testsigma & Testsigma' +page_title: 'Link Test Cases Between Test Management by Testsigma & Testsigma' +metadesc: 'Two-way test case sync ensures consistent traceability & seamless alignment between Test Management by Testsigma and Testsigma.' noindex: false order: 11.3 page_id: 'link-tests-in-testsigma-and-tms' @@ -16,8 +16,8 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Link Test Cases in Arcus by Testsigma' - url: '#link-test-cases-in-arcus-by-testsigma' + name: 'Link Test Cases in Test Management by Testsigma' + url: '#link-test-cases-in-test-management-by-testsigma' - type: link name: 'Link Test Cases in Testsigma' url: '#link-test-cases-in-testsigma' @@ -29,9 +29,9 @@ contextual_links: --- -You can link test cases between Arcus by Testsigma and Testsigma to maintain a single, synchronized source of truth for all your tests. +You can link test cases between Test Management by Testsigma and Testsigma to maintain a single, synchronized source of truth for all your tests. -Manual test cases created in Arcus by Testsigma can be directly pushed to Testsigma as automated test cases. Similarly, automated test cases in Testsigma can be pushed to Arcus by Testsigma as manual test cases with detailed steps. +Manual test cases created in Test Management by Testsigma can be directly pushed to Testsigma as automated test cases. Similarly, automated test cases in Testsigma can be pushed to Test Management by Testsigma as manual test cases with detailed steps. This two-way linkage eliminates redundancy, improves traceability, and ensures alignment between manual and automated testing efforts across both systems. @@ -39,7 +39,7 @@ This two-way linkage eliminates redundancy, improves traceability, and ensures a > ## **Prerequisites** > -> Before you begin, ensure that the integration between Testsigma and Arcus by Testsigma is enabled and that test cases are available in both systems. +> Before you begin, ensure that the integration between Testsigma and Test Management by Testsigma is enabled and that test cases are available in both systems. --- @@ -54,7 +54,7 @@ This two-way linkage eliminates redundancy, improves traceability, and ensures a --- -## **Link Test Cases in Arcus by Testsigma** +## **Link Test Cases in Test Management by Testsigma** 1. From the **Dashboard**, go to **Test Cases**. diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-plans.md b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md similarity index 70% rename from src/pages/docs/arcus/testsigma-two-way-integration/link-test-plans.md rename to src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md index 61e0ea9..316cbc7 100644 --- a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-plans.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md @@ -1,7 +1,7 @@ --- -title: 'Link Test Plans Between Arcus by Testsigma & Testsigma' -page_title: 'Link Test Plans Between Arcus by Testsigma & Testsigma' -metadesc: 'The Arcus by Testsigma & Testsigma integration streamlines execution by connecting test plans between both systems & providing centralized access to detailed results.' +title: 'Link Test Plans Between Test Management by Testsigma & Testsigma' +page_title: 'Link Test Plans Between Test Management by Testsigma & Testsigma' +metadesc: 'The Test Management by Testsigma & Testsigma integration streamlines execution by connecting test plans between both systems & providing centralized access to detailed results.' noindex: false order: 11.6 page_id: 'link-test-plans-in-testsigma-and-tms' @@ -16,8 +16,8 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Link Test Plans in Arcus by Testsigma' - url: '#link-test-plans-in-arcus-by-testsigma' + name: 'Link Test Plans in Test Management by Testsigma' + url: '#link-test-plans-in-test-management-by-testsigma' - type: link name: 'Link Test Plans in Testsigma' url: '#link-test-plans-in-testsigma' @@ -29,13 +29,13 @@ contextual_links: --- -You can link test plans between Arcus by Testsigma and Testsigma to execute test plans in Testsigma directly from Arcus by Testsigma. Once the execution is complete, you can view machine-level reports with logs and screenshots. This article discusses linking test plans between Arcus by Testsigma and Testsigma. +You can link test plans between Test Management by Testsigma and Testsigma to execute test plans in Testsigma directly from Test Management by Testsigma. Once the execution is complete, you can view machine-level reports with logs and screenshots. This article discusses linking test plans between Test Management by Testsigma and Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that the integration between Testsigma and Arcus by Testsigma is enabled and that test plans are available in both systems. +> Before you begin, ensure that the integration between Testsigma and Test Management by Testsigma is enabled and that test plans are available in both systems. --- @@ -50,7 +50,7 @@ You can link test plans between Arcus by Testsigma and Testsigma to execute test --- -## **Link Test Plans in Arcus by Testsigma** +## **Link Test Plans in Test Management by Testsigma** 1. From the **Dashboard**, go to **Test Plans**. @@ -71,7 +71,7 @@ You can link test plans between Arcus by Testsigma and Testsigma to execute test 1. From the left navigation bar, go to **Test Plans**. -2. Open the test plan you want to link with Arcus by Testsigma, and click **Test Plan Details** from the **Utility Panel**. +2. Open the test plan you want to link with Test Management by Testsigma, and click **Test Plan Details** from the **Utility Panel**. 3. Click **+ Link New Plans** and select **Testsigma Test Management**. The **Link Test Plan** dialog opens. diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/manage-user.md b/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md similarity index 64% rename from src/pages/docs/arcus/testsigma-two-way-integration/manage-user.md rename to src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md index aa1896a..efb1890 100644 --- a/src/pages/docs/arcus/testsigma-two-way-integration/manage-user.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md @@ -1,7 +1,7 @@ --- -title: 'Managing Users in Testsigma & Arcus by Testsigma' -page_title: 'Manage Users in Testsigma & Arcus by Testsigma' -metadesc: 'Testsigma & Arcus by Testsigma integration also provides unified user management, allowing you to control access for both products from a single interface.' +title: 'Managing Users in Testsigma & Test Management by Testsigma' +page_title: 'Manage Users in Testsigma & Test Management by Testsigma' +metadesc: 'Testsigma & Test Management by Testsigma integration also provides unified user management, allowing you to control access for both products from a single interface.' noindex: false order: 11.2 page_id: 'manage-users-in-testsigma-and-tms' @@ -16,8 +16,8 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Add Users in Arcus by Testsigma' - url: '#add-users-in-arcus-by-testsigma' + name: 'Add Users in Test Management by Testsigma' + url: '#add-users-in-test-management-by-testsigma' - type: link name: 'Add Users in Testsigma' url: '#add-users-in-testsigma' @@ -29,21 +29,21 @@ contextual_links: --- -You can manage user access across both Testsigma and Arcus by Testsigma from a single interface. When inviting users, you can choose to add them to either one or both products by selecting the relevant checkbox in the invite dialog. +You can manage user access across both Testsigma and Test Management by Testsigma from a single interface. When inviting users, you can choose to add them to either one or both products by selecting the relevant checkbox in the invite dialog. -In Testsigma, you can add new users, assign project-level roles, and optionally add them to Arcus by Testsigma. Similarly, in Arcus by Testsigma, you can invite users and choose to add them to Testsigma. +In Testsigma, you can add new users, assign project-level roles, and optionally add them to Test Management by Testsigma. Similarly, in Test Management by Testsigma, you can invite users and choose to add them to Testsigma. This unified user management approach helps maintain consistent access, simplifies onboarding, and ensures seamless collaboration across both platforms. [[info | **NOTE**:]] -| You must enable the Arcus by Testsigma & Testsigma integration to manage users from both systems. +| You must enable the Test Management by Testsigma & Testsigma integration to manage users from both systems. --- > ## **Prerequisites** > -> Before you begin, ensure that the Arcus by Testsigma integration with Testsigma is enabled. +> Before you begin, ensure that the Test Management by Testsigma integration with Testsigma is enabled. --- @@ -58,7 +58,7 @@ This unified user management approach helps maintain consistent access, simplifi --- -## **Add Users in Arcus by Testsigma** +## **Add Users in Test Management by Testsigma** 1. From the **Dashboard**, click **Invite Users**. This opens the **Users** section under **Settings**. @@ -82,7 +82,7 @@ This unified user management approach helps maintain consistent access, simplifi 3. In the **Add New User** dialog: - Enter the email address. - - Select **Add User in Arcus by Testsigma** if you also want to add the user in Arcus by Testsigma. + - Select **Add User in Test Management by Testsigma** if you also want to add the user in Test Management by Testsigma. - Select the projects and assign the appropriate roles. - Click **Send Invite**. From b094d681ac942e29465a876351faadbe431c1da1 Mon Sep 17 00:00:00 2001 From: Bharath Krishna <118433150+bharathk08@users.noreply.github.com> Date: Tue, 18 Aug 2026 19:30:36 +0530 Subject: [PATCH 2/3] Use Arcus by Testsigma branding while keeping test-management slug Co-Authored-By: Claude Sonnet 5 --- gatsby-node.js | 10 ++++---- src/components/navcards.jsx | 4 ++-- .../test-management/api-reference/modules.md | 10 ++++---- .../ci-cd-integrations/azure-devops.md | 16 ++++++------- .../ci-cd-integrations/circleci.md | 16 ++++++------- .../ci-cd-integrations/github.md | 14 +++++------ .../ci-cd-integrations/gitlab.md | 16 ++++++------- .../ci-cd-integrations/jenkins.md | 18 +++++++------- .../ci-cd-integrations/travis-ci.md | 16 ++++++------- .../data-sets/manage-data-sets.md | 10 ++++---- .../imports-and-exports/browserstack.md | 10 ++++---- .../imports-and-exports/csv-file.md | 8 +++---- .../imports-and-exports/export-tests.md | 6 ++--- .../imports-and-exports/testrail.md | 8 +++---- .../imports-and-exports/zephyr.md | 10 ++++---- src/pages/docs/test-management/index.jsx | 2 +- .../integrations/azure-devops.md | 10 ++++---- .../manage-test-cases-in-azure-devops.md | 16 ++++++------- .../manage-test-runs-in-azure-devops.md | 18 +++++++------- ...stsigma-integration-app-for-azuredevops.md | 12 +++++----- .../test-management/integrations/clickup.md | 8 +++---- .../integrations/confluence.md | 8 +++---- .../test-management/integrations/figma.md | 6 ++--- .../install-and-connect-testsigma.md | 16 ++++++------- .../manage-test-cases-in-jira.md | 16 ++++++------- .../manage-test-runs-in-jira.md | 18 +++++++------- .../docs/test-management/integrations/jira.md | 8 +++---- .../test-management/integrations/linear.md | 8 +++---- .../introduction/getting-started.md | 14 +++++------ .../test-management/introduction/overview.md | 10 ++++---- .../manage-users/invite-users.md | 10 ++++---- .../projects/manage-projects.md | 8 +++---- .../projects/project-settings.md | 10 ++++---- .../qi-home/ad-hoc/attach-context-sources.md | 2 +- .../docs/test-management/qi-home/faqs.md | 2 +- .../docs/test-management/qi-home/overview.md | 6 ++--- .../qi-home/sprints/generate-test-cases.md | 2 +- .../test-management/reports/create-report.md | 6 ++--- .../reports/dashboard-reports.md | 4 ++-- .../requirement-traceability-report.md | 4 ++-- .../test-management/reports/view-reports.md | 6 ++--- .../docs/test-management/settings/api-keys.md | 4 ++-- .../test-management/settings/audit-logs.md | 10 ++++---- .../test-management/settings/custom-fields.md | 6 ++--- .../docs/test-management/settings/labels.md | 8 +++---- .../test-management/settings/manage-access.md | 4 ++-- .../settings/manage-properties.md | 4 ++-- .../settings/notifications/email.md | 6 ++--- .../settings/notifications/microsoft-teams.md | 2 +- .../settings/notifications/overview.md | 6 ++--- .../settings/notifications/slack.md | 2 +- .../settings/smtp-configuration.md | 8 +++---- .../step-groups/create-step-groups.md | 8 +++---- .../step-groups/manage-step-groups.md | 6 ++--- .../test-capture/install-and-configure.md | 14 +++++------ .../test-management/test-capture/overview.md | 6 ++--- .../test-cases/clone-test-cases.md | 8 +++---- .../test-cases/comment-in-test-cases.md | 4 ++-- .../customize-test-case-list-view.md | 8 +++---- .../test-cases/filter-test-cases.md | 6 ++--- .../test-management/test-cases/folders.md | 8 +++---- .../test-cases/manage-test-cases.md | 6 ++--- .../test-cases/review-management.md | 10 ++++---- .../test-management/test-cases/run-history.md | 6 ++--- .../test-cases/test-case-templates.md | 8 +++---- .../test-management/test-cases/versions.md | 4 ++-- .../test-plans/manage-test-plans.md | 6 ++--- .../test-plans/share-test-plans.md | 4 ++-- .../test-runs/create-test-runs.md | 8 +++---- .../test-runs/manage-test-runs.md | 8 +++---- .../test-runs/share-test-runs.md | 4 ++-- .../test-runs/test-run-properties.md | 6 ++--- .../automate-manual-test-cases.md | 10 ++++---- .../connect-testsigma.md | 22 ++++++++--------- .../create-and-sync-test-cases.md | 12 +++++----- .../execute-test-plans.md | 24 +++++++++---------- .../link-test-cases.md | 16 ++++++------- .../link-test-plans.md | 16 ++++++------- .../manage-user.md | 20 ++++++++-------- 79 files changed, 360 insertions(+), 360 deletions(-) diff --git a/gatsby-node.js b/gatsby-node.js index fd91dfc..4f2664d 100644 --- a/gatsby-node.js +++ b/gatsby-node.js @@ -205,9 +205,9 @@ const writeLlmsTxt = (entries, outPath) => { ); const lines = [ - '# Test Management by Testsigma', + '# Arcus by Testsigma', '', - '> Documentation for Test Management by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto.', + '> Documentation for Arcus by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto.', '', ]; for (const name of sortedGroupNames) { @@ -225,12 +225,12 @@ const writeLlmsTxt = (entries, outPath) => { }; const TM_HOME_MD = `--- -title: 'Test Management by Testsigma' +title: 'Arcus by Testsigma' canonical: 'https://testsigma.com/docs/test-management/' --- -# Test Management by Testsigma — Documentation +# Arcus by Testsigma — Documentation -The complete documentation for Test Management by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto. +The complete documentation for Arcus by Testsigma — test cases, test plans, test runs, reports, and AI-powered automation with Atto. See [llms.txt](https://testsigma.com/docs/test-management/llms.txt) for the full document index, or browse top sections: diff --git a/src/components/navcards.jsx b/src/components/navcards.jsx index 9d6576c..dcb2b80 100644 --- a/src/components/navcards.jsx +++ b/src/components/navcards.jsx @@ -71,7 +71,7 @@ const data = [ id: 10, title: 'Integrations', description: - 'Integrate Test Management by Testsigma with your CI/CD tool for continuous testing.', + 'Integrate Arcus by Testsigma with your CI/CD tool for continuous testing.', path: '/docs/test-management/integrations/jira/', }, { @@ -119,7 +119,7 @@ const data = [ id: 17, title: 'CI/CD Integrations', description: - 'Integrate CI/CD Tools with Test Management by Testsigma and automate your test runs and generate test reports.', + 'Integrate CI/CD Tools with Arcus by Testsigma and automate your test runs and generate test reports.', path: '/docs/test-management/ci-cd-integrations/jenkins/', }, ]; diff --git a/src/pages/docs/test-management/api-reference/modules.md b/src/pages/docs/test-management/api-reference/modules.md index 310f1e6..e0b1317 100644 --- a/src/pages/docs/test-management/api-reference/modules.md +++ b/src/pages/docs/test-management/api-reference/modules.md @@ -1,7 +1,7 @@ --- -title: 'API Modules for Test Management by Testsigma' -page_title: 'API Modules for Test Management by Testsigma' -metadesc: 'Use API Reference for Test Management by Testsigma to manage all modules like projects, test cases, test runs, test plans, folders, step groups, & settings' +title: 'API Modules for Arcus by Testsigma' +page_title: 'API Modules for Arcus by Testsigma' +metadesc: 'Use API Reference for Arcus by Testsigma to manage all modules like projects, test cases, test runs, test plans, folders, step groups, & settings' noindex: false order: 16.2 page_id: 'api-modules-for-test-management-by-testsigma' @@ -23,7 +23,7 @@ contextual_links: --- -You can now use API Reference for Test Management by Testsigma to manage all modules of test management like projects, test cases, test runs, test plans, folders, step groups, and custom fields. These APIs support automation workflows and integration with CI/CD pipelines. +You can now use API Reference for Arcus by Testsigma to manage all modules of test management like projects, test cases, test runs, test plans, folders, step groups, and custom fields. These APIs support automation workflows and integration with CI/CD pipelines. Each module includes a set of RESTful endpoints that support standard CRUD operations, status updates, and data retrieval. Authentication is managed via Bearer tokens, which must be included in each request. @@ -31,7 +31,7 @@ Each module includes a set of RESTful endpoints that support standard CRUD opera > ## **Prerequisites** > -> Before you begin, ensure you have API Token from Test Management by Testsigma. +> Before you begin, ensure you have API Token from Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/ci-cd-integrations/azure-devops.md b/src/pages/docs/test-management/ci-cd-integrations/azure-devops.md index b37c840..02b492d 100644 --- a/src/pages/docs/test-management/ci-cd-integrations/azure-devops.md +++ b/src/pages/docs/test-management/ci-cd-integrations/azure-devops.md @@ -1,6 +1,6 @@ --- -title: 'Azure DevOps Integration with Test Management by Testsigma' -page_title: 'Azure DevOps Integration with Test Management by Testsigma' +title: 'Azure DevOps Integration with Arcus by Testsigma' +page_title: 'Azure DevOps Integration with Arcus by Testsigma' metadesc: 'Integrate Azure DevOps with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | Azure DevOps Integration with TMS by Testsigma' noindex: false order: 17.2 @@ -22,19 +22,19 @@ contextual_links:
-**Integrate Azure DevOps with Test Management by Testsigma and automate your test runs and generate test reports.** +**Integrate Azure DevOps with Arcus by Testsigma and automate your test runs and generate test reports.** --- -Integrate Azure DevOps with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Azure DevOps with Test Management by Testsigma. +Integrate Azure DevOps with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Azure DevOps with Arcus by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. -> - You have an API token from Test Management by Testsigma. +> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. +> - You have an API token from Arcus by Testsigma. > - You have an **Azure DevOps** account. --- @@ -85,7 +85,7 @@ Integrate Azure DevOps with Test Management by Testsigma to automate test execut [[info | **NOTE**:]] | Before triggering this build, make the following updates: -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Replace `` with the actual path to your JUnit XML report file. You can find this in your surefire-reports directory. @@ -95,6 +95,6 @@ Integrate Azure DevOps with Test Management by Testsigma to automate test execut 1. In your **Azure DevOps** pipeline, click **Run pipeline**. -2. After the build completes, the test run in Test Management by Testsigma is automatically updated with the test execution results. +2. After the build completes, the test run in Arcus by Testsigma is automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/test-management/ci-cd-integrations/circleci.md b/src/pages/docs/test-management/ci-cd-integrations/circleci.md index b3b4f0c..0012348 100644 --- a/src/pages/docs/test-management/ci-cd-integrations/circleci.md +++ b/src/pages/docs/test-management/ci-cd-integrations/circleci.md @@ -1,6 +1,6 @@ --- -title: 'CircleCI Integration with Test Management by Testsigma' -page_title: 'CircleCI Integration with Test Management by Testsigma' +title: 'CircleCI Integration with Arcus by Testsigma' +page_title: 'CircleCI Integration with Arcus by Testsigma' metadesc: 'Integrate CircleCI with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | CircleCI Integration with TMS by Testsigma' noindex: false order: 17.5 @@ -25,19 +25,19 @@ contextual_links:
-**Integrate CircleCI with Test Management by Testsigma and automate your test runs and generate test reports.** +**Integrate CircleCI with Arcus by Testsigma and automate your test runs and generate test reports.** --- -Integrate CircleCI with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating CircleCI with Test Management by Testsigma. +Integrate CircleCI with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating CircleCI with Arcus by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. -> - You have an API token from Test Management by Testsigma. +> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. +> - You have an API token from Arcus by Testsigma. > - You have a **CircleCI** account. @@ -107,7 +107,7 @@ Integrate CircleCI with Test Management by Testsigma to automate test executions [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Ensure the path to the JUnit report points to the actual XML file generated by Maven. @@ -122,7 +122,7 @@ Integrate CircleCI with Test Management by Testsigma to automate test executions 2. **CircleCI** will run the workflow. -3. After completion, the corresponding test run in Test Management by Testsigma will be automatically updated with the test execution results. +3. After completion, the corresponding test run in Arcus by Testsigma will be automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/test-management/ci-cd-integrations/github.md b/src/pages/docs/test-management/ci-cd-integrations/github.md index e6ea28f..44de1bd 100644 --- a/src/pages/docs/test-management/ci-cd-integrations/github.md +++ b/src/pages/docs/test-management/ci-cd-integrations/github.md @@ -1,6 +1,6 @@ --- -title: 'GitHub Integration with Test Management by Testsigma' -page_title: 'GitHub Integration with Test Management by Testsigma' +title: 'GitHub Integration with Arcus by Testsigma' +page_title: 'GitHub Integration with Arcus by Testsigma' metadesc: 'Integrate GitHub with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | GitHub Integration with TMS by Testsigma' noindex: false order: 17.3 @@ -22,19 +22,19 @@ contextual_links:
-**Integrate GitHub with Test Management by Testsigma and automate your test runs and generate test reports.** +**Integrate GitHub with Arcus by Testsigma and automate your test runs and generate test reports.** --- -Integrate GitHub with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitHub with Test Management by Testsigma. +Integrate GitHub with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitHub with Arcus by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. -> - You have an API token from Test Management by Testsigma. +> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. +> - You have an API token from Arcus by Testsigma. > - You have a **GitHub** account. @@ -84,7 +84,7 @@ Integrate GitHub with Test Management by Testsigma to automate test executions a ``` [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Ensure the path to the JUnit report points to the actual XML file generated by Maven. diff --git a/src/pages/docs/test-management/ci-cd-integrations/gitlab.md b/src/pages/docs/test-management/ci-cd-integrations/gitlab.md index 8693fc2..e699bf4 100644 --- a/src/pages/docs/test-management/ci-cd-integrations/gitlab.md +++ b/src/pages/docs/test-management/ci-cd-integrations/gitlab.md @@ -1,7 +1,7 @@ --- -title: 'GitLab Integration with Test Management by Testsigma' -page_title: 'GitLab Integration with Test Management by Testsigma' -metadesc: 'Integrate GitLab with Test Management by Testsigma to automate test executions & generate test reports through CI/CD pipelines | GitLab Integration with TMS by Testsigma' +title: 'GitLab Integration with Arcus by Testsigma' +page_title: 'GitLab Integration with Arcus by Testsigma' +metadesc: 'Integrate GitLab with Arcus by Testsigma to automate test executions & generate test reports through CI/CD pipelines | GitLab Integration with TMS by Testsigma' noindex: false order: 17.6 page_id: 'Gitlab-ci-integration-with-test-management-by-testsigma' @@ -25,19 +25,19 @@ contextual_links:
-**Integrate GitLab with Test Management by Testsigma and automate your test runs and generate test reports.** +**Integrate GitLab with Arcus by Testsigma and automate your test runs and generate test reports.** --- -Integrate GitLab with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitLab with Test Management by Testsigma. +Integrate GitLab with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating GitLab with Arcus by Testsigma. --- > ## **Prerequisites** > Before you begin, ensure the following: > - You have a **GitLab** account and a connected project repository. -> - A project and at least one test run exist in Test Management by Testsigma. -> - You have an API token from Test Management by Testsigma. +> - A project and at least one test run exist in Arcus by Testsigma. +> - You have an API token from Arcus by Testsigma. > - Your test results are generated in JUnit XML format (for example, reports/junit.xml) --- @@ -103,6 +103,6 @@ This configuration performs the following actions: 2. GitLab will run the workflow. -3. After completion, the corresponding test run in Test Management by Testsigma will be automatically updated with the test execution results. +3. After completion, the corresponding test run in Arcus by Testsigma will be automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/test-management/ci-cd-integrations/jenkins.md b/src/pages/docs/test-management/ci-cd-integrations/jenkins.md index 1fac8a5..ad7ae84 100644 --- a/src/pages/docs/test-management/ci-cd-integrations/jenkins.md +++ b/src/pages/docs/test-management/ci-cd-integrations/jenkins.md @@ -1,6 +1,6 @@ --- -title: 'Jenkins Integration with Test Management by Testsigma' -page_title: 'Jenkins Integration with Test Management by Testsigma' +title: 'Jenkins Integration with Arcus by Testsigma' +page_title: 'Jenkins Integration with Arcus by Testsigma' metadesc: 'Integrate Jenkins with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | Jenkins Integration with TMS by Testsigma' noindex: false order: 17.1 @@ -25,19 +25,19 @@ contextual_links:
-**Integrate Jenkins with Test Management by Testsigma and automate your test runs and generate test reports.** +**Integrate Jenkins with Arcus by Testsigma and automate your test runs and generate test reports.** --- -Integrate Jenkins with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Jenkins with Test Management by Testsigma. +Integrate Jenkins with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Jenkins with Arcus by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. -> - You have an API token from Test Management by Testsigma. +> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. +> - You have an API token from Arcus by Testsigma. > - You have a **Jenkins** account. --- @@ -54,7 +54,7 @@ Integrate Jenkins with Test Management by Testsigma to automate test executions 5. In the **Kind** dropdown menu, select **Secret text**. -6. In the **Secret** box, enter your API Token from Test Management by Testsigma. +6. In the **Secret** box, enter your API Token from Arcus by Testsigma. 7. In the **ID** box, enter `TESTSIGMA_API_TOKEN`. @@ -105,7 +105,7 @@ Integrate Jenkins with Test Management by Testsigma to automate test executions [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ 7. Click **Apply**, and then click **Save**. @@ -118,6 +118,6 @@ Integrate Jenkins with Test Management by Testsigma to automate test executions 2. In the left navigation bar, click **Build Now**. -3. Once the build completes successfully, the test case statuses in the associated test run are updated automatically in Test Management by Testsigma. +3. Once the build completes successfully, the test case statuses in the associated test run are updated automatically in Arcus by Testsigma. --- \ No newline at end of file diff --git a/src/pages/docs/test-management/ci-cd-integrations/travis-ci.md b/src/pages/docs/test-management/ci-cd-integrations/travis-ci.md index 43d54b5..22a3751 100644 --- a/src/pages/docs/test-management/ci-cd-integrations/travis-ci.md +++ b/src/pages/docs/test-management/ci-cd-integrations/travis-ci.md @@ -1,6 +1,6 @@ --- -title: 'Travis CI Integration with Test Management by Testsigma' -page_title: 'Travis CI Integration with Test Management by Testsigma' +title: 'Travis CI Integration with Arcus by Testsigma' +page_title: 'Travis CI Integration with Arcus by Testsigma' metadesc: 'Integrate Travis CI with TMS by Testsigma to automate test executions & generate test reports through CI/CD pipelines | Travis CI Integration with TMS by Testsigma' noindex: false order: 17.4 @@ -25,19 +25,19 @@ contextual_links:
-**Integrate Travis CI with Test Management by Testsigma and automate your test runs and generate test reports.** +**Integrate Travis CI with Arcus by Testsigma and automate your test runs and generate test reports.** --- -Integrate Travis CI with Test Management by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Travis CI with Test Management by Testsigma. +Integrate Travis CI with Arcus by Testsigma to automate test executions and generate test reports through CI/CD pipelines. This article discusses integrating Travis CI with Arcus by Testsigma. --- > ## **Prerequisites** > > Before you begin, ensure: -> - You have a **Project** in Test Management by Testsigma and **Test Runs** are available. -> - You have an API token from Test Management by Testsigma. +> - You have a **Project** in Arcus by Testsigma and **Test Runs** are available. +> - You have an API token from Arcus by Testsigma. > - You have a **Travis CI** account. @@ -89,7 +89,7 @@ Integrate Travis CI with Test Management by Testsigma to automate test execution ``` [[info | **NOTE**:]] -| - Replace `` in the curl command with your Project ID, which you can retrieve using the Test Management by Testsigma APIs. +| - Replace `` in the curl command with your Project ID, which you can retrieve using the Arcus by Testsigma APIs. | - Replace `` in the curl command with the Run ID, which is available in the URL when viewing a test run in the format: https://test-management.testsigma.com/ui/test_runs/{Run_ID}/ | - Ensure the path to the JUnit report points to the actual XML file generated by Maven. @@ -104,7 +104,7 @@ Integrate Travis CI with Test Management by Testsigma to automate test execution 2. **Travis CI** will run the workflow. -3. After completion, the corresponding test run in Test Management by Testsigma will be automatically updated with the test execution results. +3. After completion, the corresponding test run in Arcus by Testsigma will be automatically updated with the test execution results. --- \ No newline at end of file diff --git a/src/pages/docs/test-management/data-sets/manage-data-sets.md b/src/pages/docs/test-management/data-sets/manage-data-sets.md index 668ad0b..d1c6c19 100644 --- a/src/pages/docs/test-management/data-sets/manage-data-sets.md +++ b/src/pages/docs/test-management/data-sets/manage-data-sets.md @@ -1,6 +1,6 @@ --- -title: 'Manage Data Sets in Test Management by Testsigma' -page_title: 'Manage Data Sets in Test Management by Testsigma' +title: 'Manage Data Sets in Arcus by Testsigma' +page_title: 'Manage Data Sets in Arcus by Testsigma' metadesc: '' noindex: false order: 4.1 @@ -38,13 +38,13 @@ contextual_links: --- -Test Data Sets let you store reusable data for use across multiple test cases. They reduce manual entry, minimize errors, and help generate diverse test scenarios for better coverage. This article discusses managing Data Sets in Test Management by Testsigma. +Test Data Sets let you store reusable data for use across multiple test cases. They reduce manual entry, minimize errors, and help generate diverse test scenarios for better coverage. This article discusses managing Data Sets in Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that you have an active account in Test Management by Testsigma. +> Before you begin, ensure that you have an active account in Arcus by Testsigma. --- @@ -113,7 +113,7 @@ Test Data Sets let you store reusable data for use across multiple test cases. T --- ## **Add Multiple Data Sets to Test Case** -Follow the “**Add Data Set to Test Case**” steps to add the first data set. Repeat to add more. Test Management by Testsigma generates unique test scenarios via Cartesian product (all row combinations across data sets). +Follow the “**Add Data Set to Test Case**” steps to add the first data set. Repeat to add more. Arcus by Testsigma generates unique test scenarios via Cartesian product (all row combinations across data sets). For Example, let’s say you have two data sets, Dataset A & Dataset B. diff --git a/src/pages/docs/test-management/imports-and-exports/browserstack.md b/src/pages/docs/test-management/imports-and-exports/browserstack.md index 014ba91..f57fae6 100644 --- a/src/pages/docs/test-management/imports-and-exports/browserstack.md +++ b/src/pages/docs/test-management/imports-and-exports/browserstack.md @@ -1,6 +1,6 @@ --- title: 'Importing Test Data from Browserstack' -page_title: 'Getting Started with Test Management by Testsigma' +page_title: 'Getting Started with Arcus by Testsigma' metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' noindex: false order: 5.4 @@ -22,13 +22,13 @@ contextual_links:
-**Learn how to export test cases from Browserstack and import them into Test Management by Testsigma.** +**Learn how to export test cases from Browserstack and import them into Arcus by Testsigma.** --- -You can export test cases from Testrail and import them into Test Management by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Test Management by Testsigma. +You can export test cases from Testrail and import them into Arcus by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Arcus by Testsigma. -Note: Currently, only test cases created using the Plain Text template can be imported into Test Management by Testsigma. +Note: Currently, only test cases created using the Plain Text template can be imported into Arcus by Testsigma. --- @@ -59,6 +59,6 @@ Note: Currently, only test cases created using the Plain Text template can be im 3. Click **Upload File** and select file to import. [[info | **NOTE**:]] -| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Test Management by Testsigma. +| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/imports-and-exports/csv-file.md b/src/pages/docs/test-management/imports-and-exports/csv-file.md index 2f100a3..6837d64 100644 --- a/src/pages/docs/test-management/imports-and-exports/csv-file.md +++ b/src/pages/docs/test-management/imports-and-exports/csv-file.md @@ -1,7 +1,7 @@ --- title: 'Import Test Data from CSV Files' page_title: 'Import Test Data from CSV Files' -metadesc: 'Test Management by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature streamlines test case migration and bulk additions' +metadesc: 'Arcus by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature streamlines test case migration and bulk additions' noindex: false order: 5.1 page_id: 'import-test-data-from-csv-files' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to quickly import test cases in bulk using CSV files in Test Management by Testsigma for easy migration.** +**Learn how to quickly import test cases in bulk using CSV files in Arcus by Testsigma for easy migration.** --- -Test Management by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature simplifies the migration process from other tools by enabling bulk test case imports. This article discusses how to import test cases using a CSV file. +Arcus by Testsigma allows you to quickly import test cases in CSV files into an existing project. This feature simplifies the migration process from other tools by enabling bulk test case imports. This article discusses how to import test cases using a CSV file. --- @@ -78,7 +78,7 @@ Test Management by Testsigma allows you to quickly import test cases in CSV file - **Map Properties** to map CSV columns - **Test Case Preview** to validate mapped data -4. Atto automatically maps CSV columns to the corresponding fields in Test Management by Testsigma. +4. Atto automatically maps CSV columns to the corresponding fields in Arcus by Testsigma. 5. Review the mapped fields. If any fields are missing or incorrectly mapped, update them manually. diff --git a/src/pages/docs/test-management/imports-and-exports/export-tests.md b/src/pages/docs/test-management/imports-and-exports/export-tests.md index 76e3129..8c2b30a 100644 --- a/src/pages/docs/test-management/imports-and-exports/export-tests.md +++ b/src/pages/docs/test-management/imports-and-exports/export-tests.md @@ -1,7 +1,7 @@ --- title: 'Export Test Data' page_title: 'Export Test Data' -metadesc: 'Test Management by Testsigma allows you to quickly export test cases/step groups in excel format. This feature streamlines quick migration of test cases/step groups' +metadesc: 'Arcus by Testsigma allows you to quickly export test cases/step groups in excel format. This feature streamlines quick migration of test cases/step groups' noindex: false order: 5.5 page_id: 'export-test-data-from-testsigma' @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to export test cases and step groups in Excel format from Test Management by Testsigma.** +**Learn how to export test cases and step groups in Excel format from Arcus by Testsigma.** --- -Testsigma allows you to export test cases and step groups in excel file format, with all the associated information. This feature helps you backup, migrate, or review your test data outside the platform. This document discusses exporting test cases and step groups from Test Management by Testsigma. +Testsigma allows you to export test cases and step groups in excel file format, with all the associated information. This feature helps you backup, migrate, or review your test data outside the platform. This document discusses exporting test cases and step groups from Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/imports-and-exports/testrail.md b/src/pages/docs/test-management/imports-and-exports/testrail.md index 26fcd19..ad2170a 100644 --- a/src/pages/docs/test-management/imports-and-exports/testrail.md +++ b/src/pages/docs/test-management/imports-and-exports/testrail.md @@ -1,7 +1,7 @@ --- title: 'Import Test Data from Testrail' page_title: 'Import Test Data from Testrail' -metadesc: 'Test Management by Testsigma allows you to quickly import test cases from Testrail into an existing project. This feature streamlines test case migration and bulk additions' +metadesc: 'Arcus by Testsigma allows you to quickly import test cases from Testrail into an existing project. This feature streamlines test case migration and bulk additions' noindex: false order: 5.3 page_id: 'import-test-data-from-testrail' @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to export test cases from Testrail and import them into Test Management by Testsigma.** +**Learn how to export test cases from Testrail and import them into Arcus by Testsigma.** --- -You can export test cases from Testrail and import them into Test Management by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Test Management by Testsigma. +You can export test cases from Testrail and import them into Arcus by Testsigma. This article discusses the steps to export test cases from Testrail and import them into Arcus by Testsigma. --- @@ -62,6 +62,6 @@ You can export test cases from Testrail and import them into Test Management by 3. Click **Upload File** and select file to import. [[info | **NOTE**:]] -| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Test Management by Testsigma. +| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/imports-and-exports/zephyr.md b/src/pages/docs/test-management/imports-and-exports/zephyr.md index 4ead12c..e4cfc83 100644 --- a/src/pages/docs/test-management/imports-and-exports/zephyr.md +++ b/src/pages/docs/test-management/imports-and-exports/zephyr.md @@ -1,7 +1,7 @@ --- title: 'Import Test Data from Zephyr' page_title: 'Import Test Data from Zephyr' -metadesc: 'Test Management by Testsigma allows you to quickly import test cases Zephyr into an existing project. This feature streamlines test case migration and bulk additions' +metadesc: 'Arcus by Testsigma allows you to quickly import test cases Zephyr into an existing project. This feature streamlines test case migration and bulk additions' noindex: false order: 5.2 page_id: 'import-test-data-from-zephyr' @@ -22,14 +22,14 @@ contextual_links:
-**Learn how to export test cases from Zephyr and import them into Test Management by Testsigma.** +**Learn how to export test cases from Zephyr and import them into Arcus by Testsigma.** --- -You can export test cases from Zephyr and import them into Test Management by Testsigma. This article discusses the steps to export test cases from Zephyr and import them into Test Management by Testsigma. +You can export test cases from Zephyr and import them into Arcus by Testsigma. This article discusses the steps to export test cases from Zephyr and import them into Arcus by Testsigma. [[info | **NOTE**:]] -| Currently, only test cases created using the Plain Text template can be imported into Test Management by Testsigma. +| Currently, only test cases created using the Plain Text template can be imported into Arcus by Testsigma. --- @@ -65,6 +65,6 @@ You can export test cases from Zephyr and import them into Test Management by Te 3. Click **Upload File** and select file to import. [[info | **NOTE**:]] -| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Test Management by Testsigma. +| Follow the steps in the [Import Test Cases](https://testsigma.com/docs/test-management/imports-and-exports/csv-file/) document to prepare the file and map values or properties to align with the test case structure in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/index.jsx b/src/pages/docs/test-management/index.jsx index 613c4f8..2e0aea9 100644 --- a/src/pages/docs/test-management/index.jsx +++ b/src/pages/docs/test-management/index.jsx @@ -16,7 +16,7 @@ const IndexContent = () => { <>

- Test Management Documentation & Support + Arcus Documentation & Support



diff --git a/src/pages/docs/test-management/integrations/azure-devops.md b/src/pages/docs/test-management/integrations/azure-devops.md index e8cf2bc..7fb1b6a 100644 --- a/src/pages/docs/test-management/integrations/azure-devops.md +++ b/src/pages/docs/test-management/integrations/azure-devops.md @@ -1,7 +1,7 @@ --- -title: 'Azure DevOps Integration with Test Management by Testsigma' -page_title: 'Azure DevOps Integration with Test Management by Testsigma' -metadesc: 'Test Management by Testsigma integrates with Azure DevOps to link test defects to work items, improving traceability and collaboration.' +title: 'Azure DevOps Integration with Arcus by Testsigma' +page_title: 'Azure DevOps Integration with Arcus by Testsigma' +metadesc: 'Arcus by Testsigma integrates with Azure DevOps to link test defects to work items, improving traceability and collaboration.' noindex: false order: 10.8 page_id: 'azure-devops-integration-with-test-management-by-testsigma' @@ -29,11 +29,11 @@ contextual_links:
-**Integrate Azure DevOps with Test Management by Testsigma to seamlessly link defects to Azure DevOps work items.** +**Integrate Azure DevOps with Arcus by Testsigma to seamlessly link defects to Azure DevOps work items.** --- -Test Management by Testsigma allows seamless integration with Azure DevOps, enabling you to link test defects directly to Azure DevOps work items. This improves traceability, streamlines defect management, and enhances collaboration between QA and development teams. +Arcus by Testsigma allows seamless integration with Azure DevOps, enabling you to link test defects directly to Azure DevOps work items. This improves traceability, streamlines defect management, and enhances collaboration between QA and development teams. --- diff --git a/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md index 1992654..e02297f 100644 --- a/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md +++ b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Cases in Azure DevOps' page_title: 'Manage Test Cases in Azure DevOps' -metadesc: 'Test Management by Testsigma lets you create and manage tests directly in Azure DevOps, and edit or unlink them from linked work items.' +metadesc: 'Arcus by Testsigma lets you create and manage tests directly in Azure DevOps, and edit or unlink them from linked work items.' noindex: false order: 10.22 page_id: 'manage-tests-in-azure-devops' @@ -29,11 +29,11 @@ contextual_links:
-**Learn how to create, edit, and manage test cases directly within Azure DevOps using Test Management by Testsigma app.** +**Learn how to create, edit, and manage test cases directly within Azure DevOps using Arcus by Testsigma app.** --- -The Test Management by Testsigma simplifies your workflow by allowing you to create and manage test cases directly in Azure DevOps. You can also edit or unlink test cases from the associated work item. +The Arcus by Testsigma simplifies your workflow by allowing you to create and manage test cases directly in Azure DevOps. You can also edit or unlink test cases from the associated work item. --- @@ -41,7 +41,7 @@ The Test Management by Testsigma simplifies your workflow by allowing you to cre > > Before you begin, ensure that: > -> - Your **Azure DevOps** project is linked to a Test Management by Testsigma project. +> - Your **Azure DevOps** project is linked to a Arcus by Testsigma project. > > - The **Testsigma for Azure DevOps** extension is installed and authorized. @@ -57,7 +57,7 @@ The Test Management by Testsigma simplifies your workflow by allowing you to cre 3. Open the required work item. ![required work item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_2.png) -4. In the work item details page, click the **Test Management by Testsigma** tab. +4. In the work item details page, click the **Arcus by Testsigma** tab. ![TMS tab](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_3.png) 5. View the linked test cases associated with the work item. @@ -70,7 +70,7 @@ The Test Management by Testsigma simplifies your workflow by allowing you to cre ## **Create a New Test Case from Azure DevOps** -1. In the **Azure DevOps** issue, go to the **Test Management by Testsigma > Linked Test Cases**. +1. In the **Azure DevOps** issue, go to the **Arcus by Testsigma > Linked Test Cases**. ![work items](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_4.png) 2. Click **Create**. This opens the **Create Test Case** dialog. @@ -97,7 +97,7 @@ The Test Management by Testsigma simplifies your workflow by allowing you to cre ## **Link Test Cases from Azure DevOps** -1. In the **Azure DevOps** issue, go to the **Test Management by Testsigma > Linked Test Runs**. +1. In the **Azure DevOps** issue, go to the **Arcus by Testsigma > Linked Test Runs**. ![work items](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_4.png) 2. Click **Link**. This will open the **Add Test Cases** dialog. @@ -113,7 +113,7 @@ The Test Management by Testsigma simplifies your workflow by allowing you to cre ## **Edit a Test Case from Azure DevOps** -1. In the **Azure DevOps** issue, go to the **Test Management by Testsigma > Linked Test Cases**. +1. In the **Azure DevOps** issue, go to the **Arcus by Testsigma > Linked Test Cases**. ![work items](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_4.png) 2. Click the **meatballs menu (⋯)** next to the test case, and select **Edit** from the dropdown. diff --git a/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md index 112fd77..0051958 100644 --- a/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md +++ b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Runs in Azure DevOps' page_title: 'Manage Test Runs in Azure DevOps' -metadesc: 'The Test Management by Testsigma app simplifies your workflow by enabling you to manage test runs and test case results directly within Azure DevOps.' +metadesc: 'The Arcus by Testsigma app simplifies your workflow by enabling you to manage test runs and test case results directly within Azure DevOps.' noindex: false order: 10.23 page_id: 'manage-test-runs-in-azure-devops' @@ -29,17 +29,17 @@ contextual_links:
-**Learn how to manage test runs and update test case status directly within DevOps using Test Management by Testsigma.** +**Learn how to manage test runs and update test case status directly within DevOps using Arcus by Testsigma.** --- -The Test Management by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Azure DevOps. You can update test results, add or link defects, and manage linked test cases from within the Azure DevOps issue view. +The Arcus by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Azure DevOps. You can update test results, add or link defects, and manage linked test cases from within the Azure DevOps issue view. --- > ## **Prerequisites** > -> Before you begin, ensure that your Testsigma project is connected to an Azure DevOps project in Test Management by Testsigma. +> Before you begin, ensure that your Testsigma project is connected to an Azure DevOps project in Arcus by Testsigma. --- @@ -53,7 +53,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to 3. Open the required work item. ![required work item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_2.png) -4. In the work item details page, click the **Test Management by Testsigma** tab. +4. In the work item details page, click the **Arcus by Testsigma** tab. ![TMS tab](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_link_test_case_3.png) 5. View the linked test runs associated with the work item. @@ -66,7 +66,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to ## **Update Test Case Results from Azure DevOps** -1. In the **Azure DevOps** issue, go to **Test Management by Testsigma > Linked Test Runs**. +1. In the **Azure DevOps** issue, go to **Arcus by Testsigma > Linked Test Runs**. ![Work Item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_test_runs_1.png) 2. Expand the test run. @@ -77,13 +77,13 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to 4. Refresh the page to view the updated status in **Linked Test Cases**. [[info | **NOTE**:]] -| - The test case status will also be updated in Test Management by Testsigma. +| - The test case status will also be updated in Arcus by Testsigma. --- ## **Add Defects from Azure DevOps** -1. In the **Azure DevOps** issue, go to **Test Management by Testsigma > Linked Test Runs**. +1. In the **Azure DevOps** issue, go to **Arcus by Testsigma > Linked Test Runs**. ![Work Item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_test_runs_1.png) 2. Expand the test run. @@ -100,7 +100,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to ## **Link Defects to Existing Issues** -1. In the Azure DevOps issue, go to **Test Management by Testsigma > Linked Test Runs**. +1. In the Azure DevOps issue, go to **Arcus by Testsigma > Linked Test Runs**. ![Work Item](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_test_runs_1.png) 2. Expand the test run. diff --git a/src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md index a7d05b1..eaffca0 100644 --- a/src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md +++ b/src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md @@ -29,11 +29,11 @@ contextual_links:
-**You can create, run, and manage your tests inside Azure DevOps. Just like you do in Test Management by Testsigma.** +**You can create, run, and manage your tests inside Azure DevOps. Just like you do in Arcus by Testsigma.** --- -The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capabilities to include native test management. This enables teams to create, manage, and track test cases and test runs directly within the Azure DevOps environment, without switching to Test Management by Testsigma. You can associate test results with work items, streamline pipelines, and maintain end-to-end traceability within Azure Boards and Repos. The integration accelerates testing cycles and enhances collaboration between QA and development teams from a unified workspace. +The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capabilities to include native test management. This enables teams to create, manage, and track test cases and test runs directly within the Azure DevOps environment, without switching to Arcus by Testsigma. You can associate test results with work items, streamline pipelines, and maintain end-to-end traceability within Azure Boards and Repos. The integration accelerates testing cycles and enhances collaboration between QA and development teams from a unified workspace. --- @@ -45,7 +45,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab ## **Connect TMS to Azure DevOps** -1. Log in to your Test Management by Testsigma account. +1. Log in to your Arcus by Testsigma account. 2. From the left navigation bar, navigate to **Settings > Integrations**. ![Integrations](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_1.png) @@ -53,7 +53,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab 3. In the Integrations screen, click **Setup Integration** against **Azure DevOps**. ![Azure DevOps](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_2.png) -4. Follow the OAuth-based authorization steps to connect Azure DevOps with Test Management by Testsigma. +4. Follow the OAuth-based authorization steps to connect Azure DevOps with Arcus by Testsigma. --- @@ -61,7 +61,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab 1. Open the [Azure DevOps Marketplace](https://marketplace.visualstudio.com/items?itemName=testsigma.testsigma-azure-devops). -2. Search for **Test Management by Testsigma**. +2. Search for **Arcus by Testsigma**. 3. Install the extension in your Azure DevOps organization. ![Install TMS by Testsigma](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_3.png) @@ -79,7 +79,7 @@ The Testsigma Integration for Azure DevOps seamlessly extends Azure DevOps capab 3. Click **Testsigma for Azure DevOps**. ![Testsigma for Azure Devops](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_6.png) -4. Click **Authorize Azure DevOps Extension** and complete the authorization with Test Management by Testsigma. +4. Click **Authorize Azure DevOps Extension** and complete the authorization with Arcus by Testsigma. ![Authorize Azure DevOps Extension](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/tms_azure_7.png) --- diff --git a/src/pages/docs/test-management/integrations/clickup.md b/src/pages/docs/test-management/integrations/clickup.md index 5a262e7..55e30db 100644 --- a/src/pages/docs/test-management/integrations/clickup.md +++ b/src/pages/docs/test-management/integrations/clickup.md @@ -1,7 +1,7 @@ --- -title: 'ClickUp Integration with Test Management by Testsigma' +title: 'ClickUp Integration with Arcus by Testsigma' page_title: 'ClickUp Integration with Testsigma' -metadesc: 'Integrate Test Management by Testsigma with ClickUp to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' +metadesc: 'Integrate Arcus by Testsigma with ClickUp to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' noindex: false order: 10.6 page_id: 'clickup-integration-with-testsigma-test-management' @@ -31,11 +31,11 @@ contextual_links:
-**Integrate ClickUp with Test Management by Testsigma to seamlessly link defects to ClickUp tasks.** +**Integrate ClickUp with Arcus by Testsigma to seamlessly link defects to ClickUp tasks.** --- -Test Management by Testsigma allows seamless integration with ClickUp, which enables you to link test defects directly to ClickUp tasks. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. +Arcus by Testsigma allows seamless integration with ClickUp, which enables you to link test defects directly to ClickUp tasks. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. --- diff --git a/src/pages/docs/test-management/integrations/confluence.md b/src/pages/docs/test-management/integrations/confluence.md index 933fac2..54802bb 100644 --- a/src/pages/docs/test-management/integrations/confluence.md +++ b/src/pages/docs/test-management/integrations/confluence.md @@ -1,7 +1,7 @@ --- -title: 'Confluence Integration with Test Management by Testsigma' +title: 'Confluence Integration with Arcus by Testsigma' page_title: 'Confluence Integration with Testsigma' -metadesc: 'The Confluence integration enables users to generate test cases directly from a Confluence page | Learn how to integrate Confluence with Test Management by Testsigma' +metadesc: 'The Confluence integration enables users to generate test cases directly from a Confluence page | Learn how to integrate Confluence with Arcus by Testsigma' noindex: false order: 10.7 page_id: 'confluence-integration-with-testsigma-test-management' @@ -22,11 +22,11 @@ contextual_links:
-**Configure the Confluence integration in Test Management by Testsigma.** +**Configure the Confluence integration in Arcus by Testsigma.** --- -Confluence is a team collaboration and knowledge management platform used to create, organize, and share documentation. The Confluence integration enables users to generate structured test cases directly from a Confluence page in Test Management by Testsigma. +Confluence is a team collaboration and knowledge management platform used to create, organize, and share documentation. The Confluence integration enables users to generate structured test cases directly from a Confluence page in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/integrations/figma.md b/src/pages/docs/test-management/integrations/figma.md index a55f123..beea9f8 100644 --- a/src/pages/docs/test-management/integrations/figma.md +++ b/src/pages/docs/test-management/integrations/figma.md @@ -1,5 +1,5 @@ --- -title: 'Figma Integration with Test Management by Testsigma' +title: 'Figma Integration with Arcus by Testsigma' page_title: 'Figma Integration with Testsigma' metadesc: 'Generate test cases directly from Figma designs in Testsigma | Ensure design-to-test alignment and accelerate test creation by converting UI elements into test steps' noindex: false @@ -25,7 +25,7 @@ contextual_links:
-**Integrate Figma with Test Management by Testsigma to generate test cases from your designs.** +**Integrate Figma with Arcus by Testsigma to generate test cases from your designs.** --- @@ -35,7 +35,7 @@ Testsigma lets you generate test cases directly from your Figma designs. This he > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Test Management by Testsigma and have integrated your Figma account. +> Before you begin, ensure you have a project created in Arcus by Testsigma and have integrated your Figma account. --- diff --git a/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md index 774fbb0..c5064b3 100644 --- a/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md +++ b/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md @@ -13,7 +13,7 @@ contextual_links: name: 'Prerequisites' url: '#prerequisites' - type: link - name: 'Install the Test Management by Testsigma app' + name: 'Install the Arcus by Testsigma app' url: '#install-the-test-management-by-testsigma-app' - type: link name: 'Connect Testsigma and Jira' @@ -22,11 +22,11 @@ contextual_links:
-**You can create, run, and manage your tests inside Jira. Just like you do in Test Management by Testsigma.** +**You can create, run, and manage your tests inside Jira. Just like you do in Arcus by Testsigma.** --- -The Testsigma Integration for Jira app seamlessly extends Jira’s core capabilities to include native test management. This allows teams to create, manage, and track test cases and test runs directly from the Jira environment, without switching to Test Management by Testsigma. You can add test results to stories, streamline workflows, and maintain testing continuity within Jira. The integration enhances issue tracking, accelerates testing cycles, and improves collaboration between QA and development teams from a unified workspace. +The Testsigma Integration for Jira app seamlessly extends Jira’s core capabilities to include native test management. This allows teams to create, manage, and track test cases and test runs directly from the Jira environment, without switching to Arcus by Testsigma. You can add test results to stories, streamline workflows, and maintain testing continuity within Jira. The integration enhances issue tracking, accelerates testing cycles, and improves collaboration between QA and development teams from a unified workspace. --- @@ -36,19 +36,19 @@ The Testsigma Integration for Jira app seamlessly extends Jira’s core capabili --- -## **Install the Test Management by Testsigma App** +## **Install the Arcus by Testsigma App** -1. Navigate to the Atlassian Marketplace and search for **Test Management by Testsigma**. +1. Navigate to the Atlassian Marketplace and search for **Arcus by Testsigma**. -2. Install **Test Management by Testsigma** in your Jira instance. +2. Install **Arcus by Testsigma** in your Jira instance. -3. In Jira, go to **Apps > Manage apps** and confirm **Test Management by Testsigma** is installed. +3. In Jira, go to **Apps > Manage apps** and confirm **Arcus by Testsigma** is installed. ![Testsigma App for Jira Cloud](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/testsigma_app_for_jira.png) --- ## **Connect Testsigma and Jira** -1. In the left panel under **Apps**, click **Test Management by Testsigma**. This opens the authorization page. +1. In the left panel under **Apps**, click **Arcus by Testsigma**. This opens the authorization page. 2. On the **Connect Testsigma to Jira** page, click **Authorize to Jira Marketplace App** Integration. ![Connect Testsigma to Jira](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Connect_Testsigma_App.png) diff --git a/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md index d466810..6a3a467 100644 --- a/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md +++ b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Cases in Jira App' page_title: 'Manage Test Cases in Jira' -metadesc: 'The Test Management by Testsigma app simplifies your workflow by allowing you to create & manage tests directly in Jira. You can also edit, or unlink tests from the linked Jira issue.' +metadesc: 'The Arcus by Testsigma app simplifies your workflow by allowing you to create & manage tests directly in Jira. You can also edit, or unlink tests from the linked Jira issue.' noindex: false order: 10.12 page_id: 'manage-tests-in-jira-app' @@ -28,17 +28,17 @@ contextual_links:
-**Learn how to create, edit, and manage test cases directly within Jira using Test Management by Testsigma app.** +**Learn how to create, edit, and manage test cases directly within Jira using Arcus by Testsigma app.** --- -The Test Management by Testsigma app simplifies your workflow by allowing you to create and manage test cases directly in Jira. You can also edit, or unlink test cases from the associated Jira issue. +The Arcus by Testsigma app simplifies your workflow by allowing you to create and manage test cases directly in Jira. You can also edit, or unlink test cases from the associated Jira issue. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project and that it's connected to a Jira project in Test Management by Testsigma. +> Before you begin, ensure you have a project and that it's connected to a Jira project in Arcus by Testsigma. --- @@ -46,7 +46,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to 1. Open the Jira issue in a linked Jira project. -2. Click **Jira App Actions** and then select **Test Management by Testsigma**. +2. Click **Jira App Actions** and then select **Arcus by Testsigma**. ![Testsigma App Connection](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Connect_Testsigma_to_Issue.png) [[info | **NOTE**:]] @@ -56,7 +56,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to ## **Create a New Test Case from Jira** -1. In the Jira issue, go to the **Test Management by Testsigma > Linked Test Cases**. +1. In the Jira issue, go to the **Arcus by Testsigma > Linked Test Cases**. ![Linked Cases](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Cases_in_Jira.png) 2. Click **Create**. This opens the **Create Test Case** dialog. @@ -83,7 +83,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to ## **Link Test Cases from Jira** -1. In the Jira issue, go to the **Test Management by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to the **Arcus by Testsigma > Linked Test Runs**. 2. Click **Link**. This will open the **Add Test Cases** dialog. ![Link](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Link_Test_From_Jira.png) @@ -98,7 +98,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to **Edit a Test Case from Jira App** -1. In the Jira issue, go to the **Test Management by Testsigma > Linked Test Cases**. +1. In the Jira issue, go to the **Arcus by Testsigma > Linked Test Cases**. 2. Click the **meatballs menu (⋯)** next to the test case, and select **Edit** from dropdown. ![Edit Test Case](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Edit_Test_from_Jira.png) diff --git a/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md index 549e578..a31cd67 100644 --- a/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md +++ b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md @@ -1,7 +1,7 @@ --- title: 'Manage Test Runs in Jira App' page_title: 'Manage Test Runs in Jira' -metadesc: 'The Test Management by Testsigma app simplifies your workflow by allowing you to manage test runs & test case results directly within Jira.' +metadesc: 'The Arcus by Testsigma app simplifies your workflow by allowing you to manage test runs & test case results directly within Jira.' noindex: false order: 10.13 page_id: 'manage-test-runs-in-jira-app' @@ -28,17 +28,17 @@ contextual_links:
-**Learn how to manage test runs and update test case status directly within Jira using Test Management by Testsigma.** +**Learn how to manage test runs and update test case status directly within Jira using Arcus by Testsigma.** --- -The Test Management by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Jira. You can update test results, add or link defects, and manage linked test cases from within the Jira issue view. +The Arcus by Testsigma app simplifies your workflow by allowing you to manage test runs and test case results directly within Jira. You can update test results, add or link defects, and manage linked test cases from within the Jira issue view. --- > ## **Prerequisites** > -> Before you begin, ensure that your Testsigma project is connected to a Jira project in Test Management by Testsigma. +> Before you begin, ensure that your Testsigma project is connected to a Jira project in Arcus by Testsigma. --- @@ -46,7 +46,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to 1. Open the Jira issue in a linked Jira project. -2. Click **Jira App Actions**, and then select **Test Management by Testsigma**. +2. Click **Jira App Actions**, and then select **Arcus by Testsigma**. ![Testsigma App Connection](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Connect_Testsigma_to_Issue.png) [[info | **NOTE**:]] @@ -56,7 +56,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to ## **Update Test Case Results from Jira** -1. In the Jira issue, go to **Test Management by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to **Arcus by Testsigma > Linked Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Test_Runs_In_Jira.png) 2. Expand the test run. @@ -67,13 +67,13 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to 4. Refresh the page to view the updated status in **Linked Test Cases**. [[info | **NOTE**:]] -| The test case status will also update in Test Management by Testsigma. +| The test case status will also update in Arcus by Testsigma. --- ## **Add Defects from the Jira App** -1. In the Jira issue, go to **Test Management by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to **Arcus by Testsigma > Linked Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Test_Runs_In_Jira.png) 2. Expand the test run. @@ -90,7 +90,7 @@ The Test Management by Testsigma app simplifies your workflow by allowing you to ## **Link Defects to Existing Issues** -1. In the Jira issue, go to **Test Management by Testsigma > Linked Test Runs**. +1. In the Jira issue, go to **Arcus by Testsigma > Linked Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Linked_Test_Runs_In_Jira.png) 2. Expand the test run. diff --git a/src/pages/docs/test-management/integrations/jira.md b/src/pages/docs/test-management/integrations/jira.md index b1a63da..6419888 100644 --- a/src/pages/docs/test-management/integrations/jira.md +++ b/src/pages/docs/test-management/integrations/jira.md @@ -1,7 +1,7 @@ --- -title: 'Jira Integration with Test Management by Testsigma' +title: 'Jira Integration with Arcus by Testsigma' page_title: 'Jira Integration with Testsigma' -metadesc: 'Integrate Test Management by Testsigma with Jira to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' +metadesc: 'Integrate Arcus by Testsigma with Jira to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' noindex: false order: 10.3 page_id: 'jira-integration-with-testsigma-test-management' @@ -31,11 +31,11 @@ contextual_links:
-**Integrate Jira with Test Management by Testsigma to seamlessly link defects to Jira issues.** +**Integrate Jira with Arcus by Testsigma to seamlessly link defects to Jira issues.** --- -Test Management by Testsigma allows seamless integration with Jira, which enables you to link test defects directly to Jira issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. +Arcus by Testsigma allows seamless integration with Jira, which enables you to link test defects directly to Jira issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. --- diff --git a/src/pages/docs/test-management/integrations/linear.md b/src/pages/docs/test-management/integrations/linear.md index 00353f1..cf42c93 100644 --- a/src/pages/docs/test-management/integrations/linear.md +++ b/src/pages/docs/test-management/integrations/linear.md @@ -1,7 +1,7 @@ --- -title: 'Linear Integration with Test Management by Testsigma' +title: 'Linear Integration with Arcus by Testsigma' page_title: 'Linear Integration with Testsigma' -metadesc: 'Integrate Test Management by Testsigma with Linear to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' +metadesc: 'Integrate Arcus by Testsigma with Linear to link defects to issues, enhance traceability, streamline defect management, and boost team collaboration' noindex: false order: 10.5 page_id: 'linear-integration-with-testsigma-test-management' @@ -31,11 +31,11 @@ contextual_links:
-**Integrate Linear with Test Management by Testsigma to seamlessly link defects to Linear issues.** +**Integrate Linear with Arcus by Testsigma to seamlessly link defects to Linear issues.** --- -Test Management by Testsigma allows seamless integration with Linear, which enables you to link test defects directly to Linear issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. +Arcus by Testsigma allows seamless integration with Linear, which enables you to link test defects directly to Linear issues. This integration enhances traceability, streamlines defect management, and improves collaboration between QA and development teams. --- diff --git a/src/pages/docs/test-management/introduction/getting-started.md b/src/pages/docs/test-management/introduction/getting-started.md index d18209f..4a3f77b 100644 --- a/src/pages/docs/test-management/introduction/getting-started.md +++ b/src/pages/docs/test-management/introduction/getting-started.md @@ -1,6 +1,6 @@ --- -title: 'Getting Started: Test Management by Testsigma' -page_title: 'Getting Started with Test Management by Testsigma' +title: 'Getting Started: Arcus by Testsigma' +page_title: 'Getting Started with Arcus by Testsigma' metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' noindex: false order: 1.2 @@ -13,7 +13,7 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Steps to Access Test Management by Testsigma' + name: 'Steps to Access Arcus by Testsigma' url: '#steps-to-access-testsigma-test-management' --- @@ -22,7 +22,7 @@ contextual_links: Get started with our platform and streamline how you manage and analyze test cases, plans, and runs. This article discusses steps to set up your Test Management with Testsigma. [[info | **NOTE**:]] -| If you're an existing Testsigma user, contact **support@testsigma.com** to connect your account with the Test Management by Testsigma tool. +| If you're an existing Testsigma user, contact **support@testsigma.com** to connect your account with the Arcus by Testsigma tool. --- @@ -43,15 +43,15 @@ Get started with our platform and streamline how you manage and analyze test cas --- -## **Steps to Access Test Management by Testsigma** +## **Steps to Access Arcus by Testsigma** -1. Navigate to Test Management by Testsigma Login Page. +1. Navigate to Arcus by Testsigma Login Page. 2. Sign in with your credentials. If you don't have an account, sign up. 3. In your **User Profile Settings**, select **TMS**. -4. You'll be redirected to **Test Management by Testsigma** application. +4. You'll be redirected to **Arcus by Testsigma** application. 5. On the **Dashboard**, click the **Candy Box** icon and select **+ New Project** to get started. diff --git a/src/pages/docs/test-management/introduction/overview.md b/src/pages/docs/test-management/introduction/overview.md index 60860f1..b92abc2 100644 --- a/src/pages/docs/test-management/introduction/overview.md +++ b/src/pages/docs/test-management/introduction/overview.md @@ -1,16 +1,16 @@ --- -title: 'Overview: Test Management by Testsigma' +title: 'Overview: Arcus by Testsigma' page_title: 'Overview of Test Management in Testsigma' metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' noindex: false order: 1.1 -page_id: 'Overview: Test Management by Testsigma' +page_id: 'Overview: Arcus by Testsigma' warning: false contextual_links: - type: section name: 'Contents' - type: link - name: 'Benefits of Using Test Management by Testsigma' + name: 'Benefits of Using Arcus by Testsigma' url: '#benefits-of-using-testsigma-test-management' --- @@ -18,13 +18,13 @@ contextual_links: Managing test cases shouldn't be a mess. If you're using traditional Test Management tools or Excel for it, you know the pain! Endless spreadsheets, scattered data, and lots of copy-pasting. As the projects grow, things only get worse. -Test Management by Testsigma changes that. It keeps your test cases, test plans, test runs, and reports organized and accessible in one place. No more digging through tabs or wondering who updated what. +Arcus by Testsigma changes that. It keeps your test cases, test plans, test runs, and reports organized and accessible in one place. No more digging through tabs or wondering who updated what. Test Management isn’t just about managing tests, it’s about making testing work for you, not against you! --- -## **Benefits of Using Test Management by Testsigma** +## **Benefits of Using Arcus by Testsigma** ### ⚡ **Faster Testing, Fewer Errors** diff --git a/src/pages/docs/test-management/manage-users/invite-users.md b/src/pages/docs/test-management/manage-users/invite-users.md index 255f5ee..9ce97b4 100644 --- a/src/pages/docs/test-management/manage-users/invite-users.md +++ b/src/pages/docs/test-management/manage-users/invite-users.md @@ -1,7 +1,7 @@ --- title: 'Invite Users' -page_title: 'Invite Users to Test Management by Testsigma' -metadesc: 'Invite users to your Test Management by Testsigma to collaborate & assign roles & permissions to control access based on their responsibilities.' +page_title: 'Invite Users to Arcus by Testsigma' +metadesc: 'Invite users to your Arcus by Testsigma to collaborate & assign roles & permissions to control access based on their responsibilities.' noindex: false order: 13.1 page_id: 'users-in-testsigma-test-management' @@ -22,17 +22,17 @@ contextual_links:
-**Learn how to invite users & assign roles and permissions for effective collaboration in Test Management by Testsigma.** +**Learn how to invite users & assign roles and permissions for effective collaboration in Arcus by Testsigma.** --- -Invite users to your Test Management by Testsigma to collaborate and assign roles and permissions to control access based on their responsibilities. This article discusses inviting users to your Test Management by Testsigma. +Invite users to your Arcus by Testsigma to collaborate and assign roles and permissions to control access based on their responsibilities. This article discusses inviting users to your Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project in Test Management by Testsigma and the necessary permissions to invite team members. +> Before you begin, ensure you have a project in Arcus by Testsigma and the necessary permissions to invite team members. --- diff --git a/src/pages/docs/test-management/projects/manage-projects.md b/src/pages/docs/test-management/projects/manage-projects.md index 08187eb..e0a1ce9 100644 --- a/src/pages/docs/test-management/projects/manage-projects.md +++ b/src/pages/docs/test-management/projects/manage-projects.md @@ -1,7 +1,7 @@ --- title: 'Projects: Top-Level of Test Management' -page_title: 'Projects in Test Management by Testsigma' -metadesc: 'In Test Management by Testsigma, projects come at the top level of the hierarchy that contains test cases, test runs, and test plans | Learn about projects in Test Management' +page_title: 'Projects in Arcus by Testsigma' +metadesc: 'In Arcus by Testsigma, projects come at the top level of the hierarchy that contains test cases, test runs, and test plans | Learn about projects in Test Management' noindex: false order: 2.1 page_id: 'projects-in-testsigma-test-management' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to create, edit, or delete projects in Test Management by Testsigma with ease.** +**Learn how to create, edit, or delete projects in Arcus by Testsigma with ease.** --- -In Test Management by Testsigma, the projects come at the top level of the hierarchy. Each project contains test cases, runs, and plans for a specific application. With everything in one place, tracking progress is more manageable, and you can focus on delivering high-quality testing confidently. This article discusses managing projects in Test Management by Testsigma. +In Arcus by Testsigma, the projects come at the top level of the hierarchy. Each project contains test cases, runs, and plans for a specific application. With everything in one place, tracking progress is more manageable, and you can focus on delivering high-quality testing confidently. This article discusses managing projects in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/projects/project-settings.md b/src/pages/docs/test-management/projects/project-settings.md index 30e809e..f29d5b5 100644 --- a/src/pages/docs/test-management/projects/project-settings.md +++ b/src/pages/docs/test-management/projects/project-settings.md @@ -1,7 +1,7 @@ --- title: 'Project Settings: Project Details and Test Assets' -page_title: 'Project Settings in Test Management by Testsigma' -metadesc: 'Update project details & manage test cases and step groups through import & export options | This article explains how to perform these actions in Test Management by Testsigma' +page_title: 'Project Settings in Arcus by Testsigma' +metadesc: 'Update project details & manage test cases and step groups through import & export options | This article explains how to perform these actions in Arcus by Testsigma' noindex: false order: 2.2 page_id: 'project-settings-in-testsigma-test-management' @@ -40,7 +40,7 @@ Project Settings allows you to update project details, manage test cases and ste > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see [Projects](http://testsigma.com/docs/test-management/projects/manage-projects/). +> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see [Projects](http://testsigma.com/docs/test-management/projects/manage-projects/). --- @@ -62,7 +62,7 @@ For more information, see [Imports](https://testsigma.com/docs/test-management/i ## **Export Test Cases and Step Groups** -Export test cases and step groups from Test Management by Testsigma with their associated details. +Export test cases and step groups from Arcus by Testsigma with their associated details. For more information, see [Exports](https://testsigma.com/docs/test-management/imports-and-exports/export-tests/). @@ -70,7 +70,7 @@ For more information, see [Exports](https://testsigma.com/docs/test-management/i ## **Review Management** -Review Management provides a structured review workflow for test cases in Test Management by Testsigma. You can enable or disable Review Management from Project Settings. +Review Management provides a structured review workflow for test cases in Arcus by Testsigma. You can enable or disable Review Management from Project Settings. For more information, see [Review Management](https://testsigma.com/docs/test-management/test-cases/review-management/). diff --git a/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md b/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md index 2180614..6009f7b 100644 --- a/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md +++ b/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md @@ -51,7 +51,7 @@ You attach context sources inside the Playground, before writing a prompt and tr > ## **Prerequisites** > > Before you begin, ensure that: -> - You have an active project in Test Management by Testsigma. +> - You have an active project in Arcus by Testsigma. > - The integrations for the tools you want to attach context from are connected to your project. > - The files or documents you want to attach are available on your device. diff --git a/src/pages/docs/test-management/qi-home/faqs.md b/src/pages/docs/test-management/qi-home/faqs.md index 49e1dc7..6ae0435 100644 --- a/src/pages/docs/test-management/qi-home/faqs.md +++ b/src/pages/docs/test-management/qi-home/faqs.md @@ -2,7 +2,7 @@ title: 'FAQs' page_title: 'QI Home FAQs' metadesc: 'Frequently asked questions about QI Home — Ad-Hoc vs Sprints, coverage, quality metrics, Agentic Learning, Copilot, and developer context mapping.' -description: 'Answers to frequently asked questions about QI Home in Test Management by Testsigma.' +description: 'Answers to frequently asked questions about QI Home in Arcus by Testsigma.' noindex: false order: 13.52 page_id: 'qi-home-faqs' diff --git a/src/pages/docs/test-management/qi-home/overview.md b/src/pages/docs/test-management/qi-home/overview.md index 1628fb1..f769ddb 100644 --- a/src/pages/docs/test-management/qi-home/overview.md +++ b/src/pages/docs/test-management/qi-home/overview.md @@ -1,7 +1,7 @@ --- title: "Overview: QI Home" page_title: "Overview of QI Home" -metadesc: 'QI Home is where Atto generates test cases from your requirements, tracks coverage, builds test plans, and automates test execution in Test Management by Testsigma.' +metadesc: 'QI Home is where Atto generates test cases from your requirements, tracks coverage, builds test plans, and automates test execution in Arcus by Testsigma.' description: 'An overview of QI Home, where Atto generates test cases, tracks coverage, builds test plans, and automates test execution.' noindex: false order: 13.20 @@ -60,7 +60,7 @@ contextual_links: --- -QI Home is where Atto, the AI feature in Test Management by Testsigma, generates test cases from your requirements, tracks coverage against your modules, builds test plans, and automates test execution. It also detects developer activity from connected Claude Code, Cursor, GitHub Copilot, and Codex context and GitHub pull requests, so your test coverage stays current with what your team is building. +QI Home is where Atto, the AI feature in Arcus by Testsigma, generates test cases from your requirements, tracks coverage against your modules, builds test plans, and automates test execution. It also detects developer activity from connected Claude Code, Cursor, GitHub Copilot, and Codex context and GitHub pull requests, so your test coverage stays current with what your team is building. You do not write test cases from scratch. You give Atto the context it needs, and it generates test cases for you. You review what was generated, accept the cases that are accurate, and save them to your library. Coverage, test plans, and quality metrics update as you go. @@ -183,7 +183,7 @@ See [Overview: Developer Context Mapping](https://testsigma.com/docs/test-manage - [FAQs](https://testsigma.com/docs/test-management/qi-home/faqs/) [[info | **NOTE**:]] -| QI Home requires an active project in Test Management by Testsigma. To attach context from Jira, Azure DevOps, Linear, ClickUp, Confluence, or Figma in Ad-Hoc, you need the respective integration connected to your project. Files, documents, and video recordings can be attached without any external integration. For Sprints, connect your project to a supported project management tool. For Developer Context Mapping, connect your Claude or GitHub account. +| QI Home requires an active project in Arcus by Testsigma. To attach context from Jira, Azure DevOps, Linear, ClickUp, Confluence, or Figma in Ad-Hoc, you need the respective integration connected to your project. Files, documents, and video recordings can be attached without any external integration. For Sprints, connect your project to a supported project management tool. For Developer Context Mapping, connect your Claude or GitHub account. --- diff --git a/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md b/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md index a460ec7..bb5898d 100644 --- a/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md +++ b/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md @@ -45,7 +45,7 @@ This article covers how sprint detection works, how to confirm or defer generati > ## **Prerequisites** > > Before you begin, ensure that: -> - You have an active project in Test Management by Testsigma. +> - You have an active project in Arcus by Testsigma. > - Your project management tool (Jira, Azure DevOps, Linear, or ClickUp) is connected to your project. > - The context sources linked in your sprint stories (Confluence pages, Figma designs, PRDs) are either publicly accessible or connected as integrations. diff --git a/src/pages/docs/test-management/reports/create-report.md b/src/pages/docs/test-management/reports/create-report.md index 169bdb8..587ecfa 100644 --- a/src/pages/docs/test-management/reports/create-report.md +++ b/src/pages/docs/test-management/reports/create-report.md @@ -1,7 +1,7 @@ --- title: 'Creating Reports' -page_title: 'Creating Reports in Test Management by Testsigma' -metadesc: 'Learn how to create reports in Test Management by Testsigma | Reports help you analyze test execution, track progress, and identify defect trends in test cycles' +page_title: 'Creating Reports in Arcus by Testsigma' +metadesc: 'Learn how to create reports in Arcus by Testsigma | Reports help you analyze test execution, track progress, and identify defect trends in test cycles' noindex: false order: 15.1 page_id: 'create-a-report-in-testsigma-test-management' @@ -35,7 +35,7 @@ contextual_links: --- -Reports in Test Management by Testsigma help you analyze test execution, track progress, and identify defect trends. This article discusses how to create reports using selected test artifacts. +Reports in Arcus by Testsigma help you analyze test execution, track progress, and identify defect trends. This article discusses how to create reports using selected test artifacts. --- diff --git a/src/pages/docs/test-management/reports/dashboard-reports.md b/src/pages/docs/test-management/reports/dashboard-reports.md index fa31e32..945387e 100644 --- a/src/pages/docs/test-management/reports/dashboard-reports.md +++ b/src/pages/docs/test-management/reports/dashboard-reports.md @@ -1,7 +1,7 @@ --- title: 'Reports in Dashboard View' -page_title: 'Reports in Dashboard View in Test Management by Testsigma' -metadesc: 'The Dashboard view in Test Management by Testsigma gives real-time test metrics. Learn how to track progress, monitor test health, & identify defects from Dashboard' +page_title: 'Reports in Dashboard View in Arcus by Testsigma' +metadesc: 'The Dashboard view in Arcus by Testsigma gives real-time test metrics. Learn how to track progress, monitor test health, & identify defects from Dashboard' noindex: false order: 15.3 page_id: 'view-dashboard-reports-in-testsigma-test-management' diff --git a/src/pages/docs/test-management/reports/requirement-traceability-report.md b/src/pages/docs/test-management/reports/requirement-traceability-report.md index f1c9802..7e4f239 100644 --- a/src/pages/docs/test-management/reports/requirement-traceability-report.md +++ b/src/pages/docs/test-management/reports/requirement-traceability-report.md @@ -1,7 +1,7 @@ --- title: 'Requirement Traceability Report' -page_title: 'Requirement Traceability Report in Test Management by Testsigma' -metadesc: 'View requirement coverage across test cases, test runs, and defects with the Requirement Traceability Report in Test Management by Testsigma.' +page_title: 'Requirement Traceability Report in Arcus by Testsigma' +metadesc: 'View requirement coverage across test cases, test runs, and defects with the Requirement Traceability Report in Arcus by Testsigma.' noindex: false order: 15.4 page_id: 'requirement-traceability-report-in-testsigma-test-management' diff --git a/src/pages/docs/test-management/reports/view-reports.md b/src/pages/docs/test-management/reports/view-reports.md index 7040c14..6dbd136 100644 --- a/src/pages/docs/test-management/reports/view-reports.md +++ b/src/pages/docs/test-management/reports/view-reports.md @@ -1,7 +1,7 @@ --- title: 'Viewing Reports' -page_title: 'Viewing Reports in Test Management by Testsigma' -metadesc: 'Learn how to view reports in Test Management by Testsigma | Interpret different sections of a report and analyze test execution, track progress, and identify defects' +page_title: 'Viewing Reports in Arcus by Testsigma' +metadesc: 'Learn how to view reports in Arcus by Testsigma | Interpret different sections of a report and analyze test execution, track progress, and identify defects' noindex: false order: 15.2 page_id: 'view-reports-in-testsigma-test-management' @@ -29,7 +29,7 @@ contextual_links: --- -Reports in Test Management by Testsigma provide dynamic, visual insights into test execution status, progress, and defect tracking. This article discusses how to view and interpret different sections of a report. +Reports in Arcus by Testsigma provide dynamic, visual insights into test execution status, progress, and defect tracking. This article discusses how to view and interpret different sections of a report. --- diff --git a/src/pages/docs/test-management/settings/api-keys.md b/src/pages/docs/test-management/settings/api-keys.md index 7a567e2..a24a566 100644 --- a/src/pages/docs/test-management/settings/api-keys.md +++ b/src/pages/docs/test-management/settings/api-keys.md @@ -16,11 +16,11 @@ contextual_links:
-**Securely connect and automate with API Keys in Test Management by Testsigma.** +**Securely connect and automate with API Keys in Arcus by Testsigma.** --- -You can generate API Keys in Test Management by Testsigma to automate tasks such as creating projects, test cases, test runs, and test plans, as well as executing them. This article discusses how to generate API keys in Test Management by Testsigma. +You can generate API Keys in Arcus by Testsigma to automate tasks such as creating projects, test cases, test runs, and test plans, as well as executing them. This article discusses how to generate API keys in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/settings/audit-logs.md b/src/pages/docs/test-management/settings/audit-logs.md index 9c784cc..d5d8cc9 100644 --- a/src/pages/docs/test-management/settings/audit-logs.md +++ b/src/pages/docs/test-management/settings/audit-logs.md @@ -1,7 +1,7 @@ --- title: 'Audit Logs: Complete Record of Activities' -page_title: 'Audit Logs in Test Management by Testsigma' -metadesc: 'Track and export all user actions in Test Management by Testsigma with Audit Logs. Monitor activity, ensure accountability, and support security and compliance reviews.' +page_title: 'Audit Logs in Arcus by Testsigma' +metadesc: 'Track and export all user actions in Arcus by Testsigma with Audit Logs. Monitor activity, ensure accountability, and support security and compliance reviews.' noindex: false order: 12.6 page_id: 'audit-logs-in-testsigma-test-management' @@ -26,7 +26,7 @@ contextual_links: --- -Audit logs provide a complete record of all key activities in your Test Management by Testsigma account. They capture every user action, including changes to test assets and account access events, and store them as immutable entries. Administrators can use audit logs to monitor account usage, investigate security incidents, and ensure accountability across the organization. This article discusses Audit Logs in Test Management by Testsigma. +Audit logs provide a complete record of all key activities in your Arcus by Testsigma account. They capture every user action, including changes to test assets and account access events, and store them as immutable entries. Administrators can use audit logs to monitor account usage, investigate security incidents, and ensure accountability across the organization. This article discusses Audit Logs in Arcus by Testsigma. --- @@ -51,7 +51,7 @@ Audit logs provide a complete record of all key activities in your Test Manageme 3. Each log entry includes the following details: ![Log Entries](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Log_Entries_TMS.png) - **Time**: Date and time when the action occurred. - - **Event Type**: The entity type in Test Management by Testsigma. + - **Event Type**: The entity type in Arcus by Testsigma. - **Action**: The action type. - **Project**: The project where the change was made. - **User**: The user who performed the action. @@ -65,7 +65,7 @@ You can narrow down audit log results using the following filters: ![Filters in Audit Logs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Filters_In_Audit_Logs_TMS.png) -1. **Event Type**: Displays logs for a specific entity in Test Management by Testsigma account. +1. **Event Type**: Displays logs for a specific entity in Arcus by Testsigma account. 2. **Action**: Filters logs by the type of activity performed. diff --git a/src/pages/docs/test-management/settings/custom-fields.md b/src/pages/docs/test-management/settings/custom-fields.md index c7abfd9..49ceaac 100644 --- a/src/pages/docs/test-management/settings/custom-fields.md +++ b/src/pages/docs/test-management/settings/custom-fields.md @@ -1,7 +1,7 @@ --- title: 'Manage Custom Fields' page_title: 'Manage Custom Fields in Test Management' -metadesc: 'Create and manage custom fields in Test Management by Testsigma to add specific details/additional details and filter tests efficiently in your test management workflow' +metadesc: 'Create and manage custom fields in Arcus by Testsigma to add specific details/additional details and filter tests efficiently in your test management workflow' noindex: false order: 12.2 page_id: 'custom-fields-in-testsigma-test-management' @@ -32,13 +32,13 @@ contextual_links: --- -In Test Management by Testsigma, you can create custom fields to add additional, project-specific information to your test cases. These fields help you track attributes beyond the default properties. After creating a custom field, you can add it to test cases and use it to filter and locate specific test cases efficiently. This article discusses how to create a custom field, add it to test cases, and filter test cases using custom field values. +In Arcus by Testsigma, you can create custom fields to add additional, project-specific information to your test cases. These fields help you track attributes beyond the default properties. After creating a custom field, you can add it to test cases and use it to filter and locate specific test cases efficiently. This article discusses how to create a custom field, add it to test cases, and filter test cases using custom field values. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/). +> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/). --- diff --git a/src/pages/docs/test-management/settings/labels.md b/src/pages/docs/test-management/settings/labels.md index 2537d6a..8510d77 100644 --- a/src/pages/docs/test-management/settings/labels.md +++ b/src/pages/docs/test-management/settings/labels.md @@ -1,7 +1,7 @@ --- title: 'Manage Labels' -page_title: 'Manage Labels in Test Management by Testsigma' -metadesc: 'Organize test cases and runs using labels in Test Management by Testsigma. Create, edit, or delete labels to filter, group, and manage tests efficiently in your test management' +page_title: 'Manage Labels in Arcus by Testsigma' +metadesc: 'Organize test cases and runs using labels in Arcus by Testsigma. Create, edit, or delete labels to filter, group, and manage tests efficiently in your test management' noindex: false order: 12.3 page_id: 'manage-labels-testsigma-test-management' @@ -35,13 +35,13 @@ Labels help you organize your test cases and test runs, making it easier to filt - Edit existing labels to refine test organization as requirements develop. - Delete labels you no longer need to keep your test suite clean. -This article discusses managing labels in Test Management by Testsigma. +This article discusses managing labels in Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see Projects. +> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see Projects. --- diff --git a/src/pages/docs/test-management/settings/manage-access.md b/src/pages/docs/test-management/settings/manage-access.md index 0be0143..73421c8 100644 --- a/src/pages/docs/test-management/settings/manage-access.md +++ b/src/pages/docs/test-management/settings/manage-access.md @@ -25,11 +25,11 @@ contextual_links:
-**Learn how admins in Test Management by Testsigma can grant and revoke temporary support access for issue diagnosis and resolution.** +**Learn how admins in Arcus by Testsigma can grant and revoke temporary support access for issue diagnosis and resolution.** --- -Admin in the Test Management by Testsigma account can grant temporary access to the Testsigma Support team for diagnosing and resolving support related issues. This article discusses how to authorize and revoke support access. +Admin in the Arcus by Testsigma account can grant temporary access to the Testsigma Support team for diagnosing and resolving support related issues. This article discusses how to authorize and revoke support access. --- diff --git a/src/pages/docs/test-management/settings/manage-properties.md b/src/pages/docs/test-management/settings/manage-properties.md index 7d730cf..b2cc28f 100644 --- a/src/pages/docs/test-management/settings/manage-properties.md +++ b/src/pages/docs/test-management/settings/manage-properties.md @@ -26,13 +26,13 @@ contextual_links: --- -In the Manage Properties section, you can edit the default values for Test Case Priority, Automation Type, Test Case Status, and Test Case Type. The system uses these values when you create new test cases. This article discusses managing test case properties in Test Management by Testsigma. +In the Manage Properties section, you can edit the default values for Test Case Priority, Automation Type, Test Case Status, and Test Case Type. The system uses these values when you create new test cases. This article discusses managing test case properties in Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see Projects. +> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see Projects. --- diff --git a/src/pages/docs/test-management/settings/notifications/email.md b/src/pages/docs/test-management/settings/notifications/email.md index a92bdb5..62fd0a8 100644 --- a/src/pages/docs/test-management/settings/notifications/email.md +++ b/src/pages/docs/test-management/settings/notifications/email.md @@ -33,13 +33,13 @@ contextual_links: --- -Test Management by Testsigma allows you to configure custom email notifications for various test entities. Email notifications help teams stay informed about key events such as assignments, status changes, and review updates. This article discusses customizing email notifications in Test Management by Testsigma. +Arcus by Testsigma allows you to configure custom email notifications for various test entities. Email notifications help teams stay informed about key events such as assignments, status changes, and review updates. This article discusses customizing email notifications in Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that you are added as a user in Test Management by Testsigma. +> Before you begin, ensure that you are added as a user in Arcus by Testsigma. --- @@ -101,7 +101,7 @@ Send daily summary email for test plan progress 5. Click **Save** to apply the changes. [[info | **NOTE**:]] -| To send notifications from your own email address, ensure SMTP is configured. For more information, see [SMTP Configuration in Test Management by Testsigma](https://testsigma.com/docs/test-management/settings/smtp-configuration/). +| To send notifications from your own email address, ensure SMTP is configured. For more information, see [SMTP Configuration in Arcus by Testsigma](https://testsigma.com/docs/test-management/settings/smtp-configuration/). --- diff --git a/src/pages/docs/test-management/settings/notifications/microsoft-teams.md b/src/pages/docs/test-management/settings/notifications/microsoft-teams.md index 5330004..033a7bb 100644 --- a/src/pages/docs/test-management/settings/notifications/microsoft-teams.md +++ b/src/pages/docs/test-management/settings/notifications/microsoft-teams.md @@ -33,7 +33,7 @@ contextual_links: --- -Test Management by Testsigma allows you to configure Microsoft Teams notifications for various test entities. These notifications help teams stay aligned with testing activities by delivering real-time updates within Teams channels. This article discusses setting up and customizing Microsoft Teams notifications in Test Management by Testsigma. +Arcus by Testsigma allows you to configure Microsoft Teams notifications for various test entities. These notifications help teams stay aligned with testing activities by delivering real-time updates within Teams channels. This article discusses setting up and customizing Microsoft Teams notifications in Arcus by Testsigma. [[info | **NOTE**:]] | Authorize the integration using a separate Microsoft account designated only for setup. The account used for authorization will not receive notifications due to a limitation in Microsoft Teams. diff --git a/src/pages/docs/test-management/settings/notifications/overview.md b/src/pages/docs/test-management/settings/notifications/overview.md index 045c7a2..531a285 100644 --- a/src/pages/docs/test-management/settings/notifications/overview.md +++ b/src/pages/docs/test-management/settings/notifications/overview.md @@ -1,7 +1,7 @@ --- title: 'Overview: Set Up Notifications' page_title: 'Overview: Set Up Notifications' -metadesc: 'Test Management by Testsigma allows you to integrate with Slack & Microsoft Teams and configure custom notifications for various test entities.' +metadesc: 'Arcus by Testsigma allows you to integrate with Slack & Microsoft Teams and configure custom notifications for various test entities.' noindex: false order: 12.81 page_id: 'overview-of-setting-up-notifications' @@ -26,7 +26,7 @@ contextual_links: --- -Test Management by Testsigma allows you to integrate with Slack and Microsoft Teams and configure custom notifications for various test entities. Notifications help teams stay aligned with ongoing testing activities by alerting users about key events such as assignments, status changes, and review updates. This article discusses setting up notifications in Test Management by Testsigma. +Arcus by Testsigma allows you to integrate with Slack and Microsoft Teams and configure custom notifications for various test entities. Notifications help teams stay aligned with ongoing testing activities by alerting users about key events such as assignments, status changes, and review updates. This article discusses setting up notifications in Arcus by Testsigma. --- @@ -76,7 +76,7 @@ Send notification when a test plan is completed Send daily summary notification for active test plans [[info | **NOTE**:]] -| Test Management by Testsigma allows you to configure notifications for each entity and enable or disable them based on your preferences. +| Arcus by Testsigma allows you to configure notifications for each entity and enable or disable them based on your preferences. | ![Toggles](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Notification_Toggles.png) --- \ No newline at end of file diff --git a/src/pages/docs/test-management/settings/notifications/slack.md b/src/pages/docs/test-management/settings/notifications/slack.md index cc4cee9..bb48e82 100644 --- a/src/pages/docs/test-management/settings/notifications/slack.md +++ b/src/pages/docs/test-management/settings/notifications/slack.md @@ -33,7 +33,7 @@ contextual_links: --- -Test Management by Testsigma allows you to configure Slack notifications for various test entities. Slack notifications help teams stay informed about assignments, reviews, and status updates directly within their Slack workspace. This article discusses setting up and customizing Slack notifications in Test Management by Testsigma. +Arcus by Testsigma allows you to configure Slack notifications for various test entities. Slack notifications help teams stay informed about assignments, reviews, and status updates directly within their Slack workspace. This article discusses setting up and customizing Slack notifications in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/settings/smtp-configuration.md b/src/pages/docs/test-management/settings/smtp-configuration.md index 975f1dd..a4a0e1c 100644 --- a/src/pages/docs/test-management/settings/smtp-configuration.md +++ b/src/pages/docs/test-management/settings/smtp-configuration.md @@ -1,7 +1,7 @@ --- -title: 'SMTP Configuration in Test Management by Testsigma' -page_title: 'SMTP Configuration in Test Management by Testsigma' -metadesc: 'Configuring SMTP allows your organization to send email notifications from your own authenticated email address | Learn configuring SMTP in Test Management by Testsigma' +title: 'SMTP Configuration in Arcus by Testsigma' +page_title: 'SMTP Configuration in Arcus by Testsigma' +metadesc: 'Configuring SMTP allows your organization to send email notifications from your own authenticated email address | Learn configuring SMTP in Arcus by Testsigma' noindex: false order: 12.7 page_id: 'smtp-configuration' @@ -26,7 +26,7 @@ contextual_links: --- -Configuring Simple Mail Transfer Protocol (SMTP) allows your organization to send email notifications from your own authenticated email address instead of Testsigma’s default sender. This ensures improved branding, deliverability, and security for automated notifications. This article discusses configuring SMTP in Test Management by Testsigma. +Configuring Simple Mail Transfer Protocol (SMTP) allows your organization to send email notifications from your own authenticated email address instead of Testsigma’s default sender. This ensures improved branding, deliverability, and security for automated notifications. This article discusses configuring SMTP in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/step-groups/create-step-groups.md b/src/pages/docs/test-management/step-groups/create-step-groups.md index aa2e163..b1e643b 100644 --- a/src/pages/docs/test-management/step-groups/create-step-groups.md +++ b/src/pages/docs/test-management/step-groups/create-step-groups.md @@ -1,7 +1,7 @@ --- title: 'Creating Step Groups' -page_title: 'Creating Step Groups in Test Management by Testsigma' -metadesc: 'Step Groups in Test Management by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Test Management by Testsigma' +page_title: 'Creating Step Groups in Arcus by Testsigma' +metadesc: 'Step Groups in Arcus by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Arcus by Testsigma' noindex: false order: 6.1 page_id: 'create-step-groups' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to create to reuse common steps across multiple test cases in Test Management by Testsigma.** +**Learn how to create to reuse common steps across multiple test cases in Arcus by Testsigma.** --- -Step Groups feature in Test Management by Testsigma enhances test case management by grouping repetitive test steps. Instead of manually adding steps across multiple test cases, you can link a Step Group to various test cases with common steps. This article discusses managing Step Groups in Test Management by Testsigma. +Step Groups feature in Arcus by Testsigma enhances test case management by grouping repetitive test steps. Instead of manually adding steps across multiple test cases, you can link a Step Group to various test cases with common steps. This article discusses managing Step Groups in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/step-groups/manage-step-groups.md b/src/pages/docs/test-management/step-groups/manage-step-groups.md index cebb37c..2e1ec5c 100644 --- a/src/pages/docs/test-management/step-groups/manage-step-groups.md +++ b/src/pages/docs/test-management/step-groups/manage-step-groups.md @@ -1,7 +1,7 @@ --- title: 'Managing Step Groups' -page_title: 'Managing Step Groups in Test Management by Testsigma' -metadesc: 'Step Groups in Test Management by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Test Management by Testsigma' +page_title: 'Managing Step Groups in Arcus by Testsigma' +metadesc: 'Step Groups in Arcus by Testsigma enhances test case management by grouping repetitive test steps | Learn how to create step groups in Arcus by Testsigma' noindex: false order: 6.2 page_id: 'create-step-groups' @@ -22,7 +22,7 @@ contextual_links:
-**Learn how to edit or delete Step Groups in Test Management by Testsigma.** +**Learn how to edit or delete Step Groups in Arcus by Testsigma.** --- diff --git a/src/pages/docs/test-management/test-capture/install-and-configure.md b/src/pages/docs/test-management/test-capture/install-and-configure.md index e5d58ba..6c95d5f 100644 --- a/src/pages/docs/test-management/test-capture/install-and-configure.md +++ b/src/pages/docs/test-management/test-capture/install-and-configure.md @@ -1,7 +1,7 @@ --- title: 'Install & Configure Test Capture' page_title: 'Install & Configure Test Capture Extension' -metadesc: 'Learn how to install, author, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Test Management by Testsigma' +metadesc: 'Learn how to install, author, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Arcus by Testsigma' noindex: false order: 9.2 page_id: 'install-test-capture-extension' @@ -13,7 +13,7 @@ contextual_links: name: 'Install Test Capture Extension' url: '#install-test-capture-extension' - type: link - name: 'Install from Test Management by Testsigma' + name: 'Install from Arcus by Testsigma' url: '#install-from-test-management-by-testsigma' - type: link name: 'Install from Chrome Web Store' @@ -34,17 +34,17 @@ contextual_links: --- -Installing, authorizing, and configuring the Test Capture Chrome extension is required before you can execute tests and capture logs during manual execution. This article discusses setting up the extension so it works correctly with Test Management by Testsigma. +Installing, authorizing, and configuring the Test Capture Chrome extension is required before you can execute tests and capture logs during manual execution. This article discusses setting up the extension so it works correctly with Arcus by Testsigma. --- ## **Install Test Capture Extension** -You can install the extension directly from **Test Management by Testsigma** or from the **Chrome Web Store**. +You can install the extension directly from **Arcus by Testsigma** or from the **Chrome Web Store**.
-## **Install from Test Management by Testsigma** +## **Install from Arcus by Testsigma** 1. From the left navigation bar, go to **Test Runs**. ![Test Runs](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Test_Runs_for_Capture.png) @@ -83,7 +83,7 @@ You can install the extension directly from **Test Management by Testsigma** or ## **Authorize the Extension** -After installation, the extension must be authorized to connect with Test Management by Testsigma. +After installation, the extension must be authorized to connect with Arcus by Testsigma. 1. Open a test run. @@ -92,7 +92,7 @@ After installation, the extension must be authorized to connect with Test Manage 3. In the **Test Capture** dialog, click **Login to Test Capture**. ![Login to Test Capture](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Login_to_Test_Capture.png) -4. You are redirected to the **Test Management by Testsigma** authorization page. +4. You are redirected to the **Arcus by Testsigma** authorization page. 5. Click **Authorize Extension**. ![Authorize Extension](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Authorize_Capture_Extension.png) diff --git a/src/pages/docs/test-management/test-capture/overview.md b/src/pages/docs/test-management/test-capture/overview.md index 4ff5a12..f96c040 100644 --- a/src/pages/docs/test-management/test-capture/overview.md +++ b/src/pages/docs/test-management/test-capture/overview.md @@ -1,7 +1,7 @@ --- title: 'Overview: Test Capture' -page_title: 'Overview of Test Capture in Test Management by Testsigma' -metadesc: 'Test Capture runs alongside manual test execution. This article provides an overview of Test Capture in Test Management by Testsigma.' +page_title: 'Overview of Test Capture in Arcus by Testsigma' +metadesc: 'Test Capture runs alongside manual test execution. This article provides an overview of Test Capture in Arcus by Testsigma.' noindex: false order: 9.1 page_id: 'test-capture-in-testsigma-test-management' @@ -31,7 +31,7 @@ contextual_links: --- -Test Capture feature in Test Management by Testsigma that runs alongside manual test execution. It automatically captures screen recordings, video logs, and network logs during testing, removing the need to manually record or attach logs after execution. All captured logs are automatically linked to the original test run, giving developers the visual and diagnostic context needed to investigate and resolve issues. This article provides an overview of Test Capture in Test Management. +Test Capture feature in Arcus by Testsigma that runs alongside manual test execution. It automatically captures screen recordings, video logs, and network logs during testing, removing the need to manually record or attach logs after execution. All captured logs are automatically linked to the original test run, giving developers the visual and diagnostic context needed to investigate and resolve issues. This article provides an overview of Test Capture in Test Management. --- diff --git a/src/pages/docs/test-management/test-cases/clone-test-cases.md b/src/pages/docs/test-management/test-cases/clone-test-cases.md index 29bfd74..7be45c1 100644 --- a/src/pages/docs/test-management/test-cases/clone-test-cases.md +++ b/src/pages/docs/test-management/test-cases/clone-test-cases.md @@ -1,7 +1,7 @@ --- -title: 'Clone Test Case in Test Management by Testsigma' -page_title: 'Clone Test Case in Test Management by Testsigma' -metadesc: 'Clone test cases to quickly create reusable copies without impacting the original version | Learn how to clone test cases in Test Management by Testsigma' +title: 'Clone Test Case in Arcus by Testsigma' +page_title: 'Clone Test Case in Arcus by Testsigma' +metadesc: 'Clone test cases to quickly create reusable copies without impacting the original version | Learn how to clone test cases in Arcus by Testsigma' noindex: false order: 3.8 page_id: 'clone-tests-in-test-management' @@ -28,7 +28,7 @@ contextual_links: --- -Cloning test cases allows you to create an exact copy of an existing test case for reuse within the same project or across different projects. All field values are copied at the time of cloning, and any updates made to the original test case do not affect the cloned version. This article discusses cloning test cases in Test Management by Testsigma. +Cloning test cases allows you to create an exact copy of an existing test case for reuse within the same project or across different projects. All field values are copied at the time of cloning, and any updates made to the original test case do not affect the cloned version. This article discusses cloning test cases in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-cases/comment-in-test-cases.md b/src/pages/docs/test-management/test-cases/comment-in-test-cases.md index eee0aa4..e169253 100644 --- a/src/pages/docs/test-management/test-cases/comment-in-test-cases.md +++ b/src/pages/docs/test-management/test-cases/comment-in-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Comment in Test Cases' -page_title: 'Comment in Test Cases in Test Management by Testsigma' -metadesc: 'Use comments to collaborate instantly on test cases by sharing feedback, raising issues, & tracking discussions in one place | Comment in Test Cases in Test Management by Testsigma' +page_title: 'Comment in Test Cases in Arcus by Testsigma' +metadesc: 'Use comments to collaborate instantly on test cases by sharing feedback, raising issues, & tracking discussions in one place | Comment in Test Cases in Arcus by Testsigma' noindex: false order: 3.9 page_id: 'comment-in-test-cases-in-test-management' diff --git a/src/pages/docs/test-management/test-cases/customize-test-case-list-view.md b/src/pages/docs/test-management/test-cases/customize-test-case-list-view.md index ef87f90..58de199 100644 --- a/src/pages/docs/test-management/test-cases/customize-test-case-list-view.md +++ b/src/pages/docs/test-management/test-cases/customize-test-case-list-view.md @@ -1,7 +1,7 @@ --- title: 'Customize Test Case List View' -page_title: 'Customize Test Case List View in Test Management by Testsigma' -metadesc: 'This article discusses customizing Test Case List View in Test Management by Testsigma | Customizing test case list view helps show only the columns that are relevant' +page_title: 'Customize Test Case List View in Arcus by Testsigma' +metadesc: 'This article discusses customizing Test Case List View in Arcus by Testsigma | Customizing test case list view helps show only the columns that are relevant' noindex: false order: 3.5 page_id: 'customize-test-cases-list-view-in-test-management' @@ -25,13 +25,13 @@ contextual_links: --- -The customize test case list view feature in Test Management by Testsigma lets you select the columns that matter most to you. This helps you focus on the specific data you need, beyond the default view. This article discusses steps to customize the test case list view. +The customize test case list view feature in Arcus by Testsigma lets you select the columns that matter most to you. This helps you focus on the specific data you need, beyond the default view. This article discusses steps to customize the test case list view. --- > ## **Prerequisites** > -> Before you begin, ensure that you have test cases available in Test Management by Testsigma. +> Before you begin, ensure that you have test cases available in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-cases/filter-test-cases.md b/src/pages/docs/test-management/test-cases/filter-test-cases.md index f4d9d44..6ecec94 100644 --- a/src/pages/docs/test-management/test-cases/filter-test-cases.md +++ b/src/pages/docs/test-management/test-cases/filter-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Test Case Filters' -page_title: 'Test Case Filters in Test Management by Testsigma' -metadesc: 'This article discusses Test Case Filters in Test Management by Testsigma | Filtering test cases involves in filtering tests based on priority, type, status, and more' +page_title: 'Test Case Filters in Arcus by Testsigma' +metadesc: 'This article discusses Test Case Filters in Arcus by Testsigma | Filtering test cases involves in filtering tests based on priority, type, status, and more' noindex: false order: 3.4 page_id: 'test-cases-filters-in-testsigma-test-management' @@ -35,7 +35,7 @@ Filtering test cases helps you find specific test cases based on properties such > ## **Prerequisites** > -> Before you begin, ensure that you have test cases available in Test Management by Testsigma. +> Before you begin, ensure that you have test cases available in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-cases/folders.md b/src/pages/docs/test-management/test-cases/folders.md index 8366abe..98cde63 100644 --- a/src/pages/docs/test-management/test-cases/folders.md +++ b/src/pages/docs/test-management/test-cases/folders.md @@ -1,6 +1,6 @@ --- title: 'Folders: Organizing Test Cases' -page_title: 'Getting Started with Test Management by Testsigma' +page_title: 'Getting Started with Arcus by Testsigma' metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place' noindex: false order: 3.1 @@ -32,14 +32,14 @@ contextual_links: --- -Organizing test cases is easier with folders within a project. Test Management by Testsigma allows you to create a hierarchical folder structure, where subfolders nest under parent folders for better organization. Each folder displays cumulative test case counts, giving you a clear view of the total test cases within a project. This article discusses creating, managing, and navigating test case folders efficiently. -Test Management by Testsigma +Organizing test cases is easier with folders within a project. Arcus by Testsigma allows you to create a hierarchical folder structure, where subfolders nest under parent folders for better organization. Each folder displays cumulative test case counts, giving you a clear view of the total test cases within a project. This article discusses creating, managing, and navigating test case folders efficiently. +Arcus by Testsigma --- > ## **Prerequisites** > -> Before you begin, ensure you have a project created in Test Management by Testsigma. For more information, see Projects +> Before you begin, ensure you have a project created in Arcus by Testsigma. For more information, see Projects --- diff --git a/src/pages/docs/test-management/test-cases/manage-test-cases.md b/src/pages/docs/test-management/test-cases/manage-test-cases.md index 1057c5d..71e2fdf 100644 --- a/src/pages/docs/test-management/test-cases/manage-test-cases.md +++ b/src/pages/docs/test-management/test-cases/manage-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Test Cases: The Core of Testing' -page_title: 'Test Cases in Test Management by Testsigma' -metadesc: 'This article discusses managing test cases in Test Management by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' +page_title: 'Test Cases in Arcus by Testsigma' +metadesc: 'This article discusses managing test cases in Arcus by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' noindex: false order: 3.2 page_id: 'test-cases-in-testsigma-test-management' @@ -37,7 +37,7 @@ contextual_links:
-**Learn how to create, organize, and maintain test cases in Test Management by Testsigma.** +**Learn how to create, organize, and maintain test cases in Arcus by Testsigma.** --- diff --git a/src/pages/docs/test-management/test-cases/review-management.md b/src/pages/docs/test-management/test-cases/review-management.md index 334d05c..077eb95 100644 --- a/src/pages/docs/test-management/test-cases/review-management.md +++ b/src/pages/docs/test-management/test-cases/review-management.md @@ -1,7 +1,7 @@ --- -title: 'Review Management in Test Management by Testsigma' -page_title: 'Review Management in Test Management by Testsigma' -metadesc: 'Review Management adds a structured approval workflow that helps teams maintain high-quality, reliable test cases | Learn Review Management in Test Management by Testsigma' +title: 'Review Management in Arcus by Testsigma' +page_title: 'Review Management in Arcus by Testsigma' +metadesc: 'Review Management adds a structured approval workflow that helps teams maintain high-quality, reliable test cases | Learn Review Management in Arcus by Testsigma' noindex: false order: 3.7 page_id: 'review-management-in-test-management' @@ -34,13 +34,13 @@ contextual_links: --- -Review Management helps teams maintain high-quality test cases by adding a structured review workflow to Test Management by Testsigma. QA members can submit their test cases for review, and designated reviewers can approve them or return them for rework with comments. This ensures that test cases are accurate, consistent, and aligned with project standards. This article discusses Review Management in Test Management by Testsigma. +Review Management helps teams maintain high-quality test cases by adding a structured review workflow to Arcus by Testsigma. QA members can submit their test cases for review, and designated reviewers can approve them or return them for rework with comments. This ensures that test cases are accurate, consistent, and aligned with project standards. This article discusses Review Management in Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure required team members are invited & added to Test Management by Testsigma. +> Before you begin, ensure required team members are invited & added to Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-cases/run-history.md b/src/pages/docs/test-management/test-cases/run-history.md index 3545e4c..fc8c363 100644 --- a/src/pages/docs/test-management/test-cases/run-history.md +++ b/src/pages/docs/test-management/test-cases/run-history.md @@ -1,7 +1,7 @@ --- title: 'View Run History for a Test Case' -page_title: 'View Run History for a Test Case in Test Management by Testsigma' -metadesc: 'View the execution history of a test case across all test runs to track stability, ownership, and trends in Test Management by Testsigma.' +page_title: 'View Run History for a Test Case in Arcus by Testsigma' +metadesc: 'View the execution history of a test case across all test runs to track stability, ownership, and trends in Arcus by Testsigma.' noindex: false order: 3.91 page_id: 'run-history-in-test-cases-in-test-management' @@ -26,7 +26,7 @@ contextual_links: --- -Run History at the test case level provides a list of all executions of that test case across associated test runs. It helps teams analyze stability, audit execution ownership, and quickly trace trends without navigating into individual test runs. This article discusses Run History for a Test Case in Test Management by Testsigma. +Run History at the test case level provides a list of all executions of that test case across associated test runs. It helps teams analyze stability, audit execution ownership, and quickly trace trends without navigating into individual test runs. This article discusses Run History for a Test Case in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-cases/test-case-templates.md b/src/pages/docs/test-management/test-cases/test-case-templates.md index 0c3ad40..65ae6ac 100644 --- a/src/pages/docs/test-management/test-cases/test-case-templates.md +++ b/src/pages/docs/test-management/test-cases/test-case-templates.md @@ -1,7 +1,7 @@ --- title: 'Test Case Templates' -page_title: 'Test Case Templates in Test Management by Testsigma' -metadesc: 'This article discusses Test Case Templates in Test Management by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' +page_title: 'Test Case Templates in Arcus by Testsigma' +metadesc: 'This article discusses Test Case Templates in Arcus by Testsigma | Managing test cases involves creating, editing, moving, and deleting them in test management' noindex: false order: 3.3 page_id: 'test-cases-templates-in-testsigma-test-management' @@ -23,7 +23,7 @@ contextual_links: --- -Test Management by Testsigma tool allows you to create test cases using two templates: +Arcus by Testsigma tool allows you to create test cases using two templates: ### 1. **Documentation Template** @@ -33,7 +33,7 @@ You can use the **Documentation Template** to create simple tests with basic pre You can use **Steps Template** when a more granular approach is necessary, breaking down each action and expected results. -Both templates allow you to attach files up to 25 MB, which enhances test documentation with relevant files for better clarity and context. This article discusses Test Case Templates in Test Management by Testsigma. +Both templates allow you to attach files up to 25 MB, which enhances test documentation with relevant files for better clarity and context. This article discusses Test Case Templates in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-cases/versions.md b/src/pages/docs/test-management/test-cases/versions.md index 882c07c..c9abbda 100644 --- a/src/pages/docs/test-management/test-cases/versions.md +++ b/src/pages/docs/test-management/test-cases/versions.md @@ -1,6 +1,6 @@ --- title: 'Versions: See What is Changed in a Test Case' -page_title: 'Versions in Test Management by Testsigma' +page_title: 'Versions in Arcus by Testsigma' metadesc: 'View the changes made to a test case using Versions. It also lets you compare the current version of a test case with any previous version to clearly see the differences' noindex: false order: 3.6 @@ -31,7 +31,7 @@ contextual_links: --- -You can view the changes made to a test case from Versions. Versions let you compare the current version of a test case with any previous version to clearly identify the differences. This article discusses how to view and compare versions in Test Management by Testsigma. +You can view the changes made to a test case from Versions. Versions let you compare the current version of a test case with any previous version to clearly identify the differences. This article discusses how to view and compare versions in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-plans/manage-test-plans.md b/src/pages/docs/test-management/test-plans/manage-test-plans.md index dd10efe..79d85ed 100644 --- a/src/pages/docs/test-management/test-plans/manage-test-plans.md +++ b/src/pages/docs/test-management/test-plans/manage-test-plans.md @@ -1,7 +1,7 @@ --- title: 'Managing Test Plans' -page_title: 'Test Plans in Test Management by Testsigma' -metadesc: 'Organize and manage your testing with test plans in Test Management by Testsigma | Set the scope, goals, and schedules to run/track test plans clearly and efficiently.' +page_title: 'Test Plans in Arcus by Testsigma' +metadesc: 'Organize and manage your testing with test plans in Arcus by Testsigma | Set the scope, goals, and schedules to run/track test plans clearly and efficiently.' noindex: false order: 8.1 page_id: 'test-plans-in-testsigma-test-management' @@ -28,7 +28,7 @@ contextual_links:
-**Learn how to create, organize, and manage test plans in Test Management by Testsigma.** +**Learn how to create, organize, and manage test plans in Arcus by Testsigma.** --- diff --git a/src/pages/docs/test-management/test-plans/share-test-plans.md b/src/pages/docs/test-management/test-plans/share-test-plans.md index e1198c3..e47f500 100644 --- a/src/pages/docs/test-management/test-plans/share-test-plans.md +++ b/src/pages/docs/test-management/test-plans/share-test-plans.md @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to generate public links to share test plans with external stakeholders in Test Management by Testsigma.** +**Learn how to generate public links to share test plans with external stakeholders in Arcus by Testsigma.** --- -You can share a test plan with anyone on the internet by generating a public link in Test Management by Testsigma. This allows external stakeholders without account access to view testing progress. +You can share a test plan with anyone on the internet by generating a public link in Arcus by Testsigma. This allows external stakeholders without account access to view testing progress. --- diff --git a/src/pages/docs/test-management/test-runs/create-test-runs.md b/src/pages/docs/test-management/test-runs/create-test-runs.md index bae487a..0496d33 100644 --- a/src/pages/docs/test-management/test-runs/create-test-runs.md +++ b/src/pages/docs/test-management/test-runs/create-test-runs.md @@ -1,7 +1,7 @@ --- title: 'Creating Test Runs' -page_title: 'Creating Test Runs in Test Management by Testsigma' -metadesc: 'Create test runs in Test Management by Testsigma by manually adding test cases, applying filters, or selecting all and ensure thorough testing of your applications' +page_title: 'Creating Test Runs in Arcus by Testsigma' +metadesc: 'Create test runs in Arcus by Testsigma by manually adding test cases, applying filters, or selecting all and ensure thorough testing of your applications' noindex: false order: 7.1 page_id: 'create-test-runs' @@ -31,11 +31,11 @@ contextual_links:
-**Learn how to create, organize & add status to the test runs in Test Management by Testsigma.** +**Learn how to create, organize & add status to the test runs in Arcus by Testsigma.** --- -Test runs ensure thorough testing of your applications. You can create test runs by adding test cases manually, using filters to dynamically include relevant test cases, or selecting all available test cases. Additionally, you can schedule, organize, and add status to the test runs. Effective test run management provides insights, drives continuous improvement, and enhances testing efficiency. This article discusses creating test runs in Test Management by Testsigma. +Test runs ensure thorough testing of your applications. You can create test runs by adding test cases manually, using filters to dynamically include relevant test cases, or selecting all available test cases. Additionally, you can schedule, organize, and add status to the test runs. Effective test run management provides insights, drives continuous improvement, and enhances testing efficiency. This article discusses creating test runs in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-runs/manage-test-runs.md b/src/pages/docs/test-management/test-runs/manage-test-runs.md index 428e1bb..9ecc658 100644 --- a/src/pages/docs/test-management/test-runs/manage-test-runs.md +++ b/src/pages/docs/test-management/test-runs/manage-test-runs.md @@ -1,7 +1,7 @@ --- title: 'Managing Test Runs' -page_title: 'Managing Test Runs in Test Management by Testsigma' -metadesc: 'Manage test runs in Test Management by Testsigma by editing, cloning, closing, or deleting them to maintain organized and efficient test execution.' +page_title: 'Managing Test Runs in Arcus by Testsigma' +metadesc: 'Manage test runs in Arcus by Testsigma by editing, cloning, closing, or deleting them to maintain organized and efficient test execution.' noindex: false order: 7.2 page_id: 'create-test-runs' @@ -28,11 +28,11 @@ contextual_links:
-**Learn how to edit, clone, close, and delete test runs in Test Management by Testsigma.** +**Learn how to edit, clone, close, and delete test runs in Arcus by Testsigma.** --- -After creating a test run, you can manage it by editing its details, cloning it for reuse, closing it to prevent further modifications, or deleting it permanently. Editing lets you modify test run details, clone duplicates for future use, close locks it from further changes, and delete option removes the test run permanently. This article discusses managing test runs in Test Management by Testsigma. +After creating a test run, you can manage it by editing its details, cloning it for reuse, closing it to prevent further modifications, or deleting it permanently. Editing lets you modify test run details, clone duplicates for future use, close locks it from further changes, and delete option removes the test run permanently. This article discusses managing test runs in Arcus by Testsigma. --- diff --git a/src/pages/docs/test-management/test-runs/share-test-runs.md b/src/pages/docs/test-management/test-runs/share-test-runs.md index d366b11..a2e4f20 100644 --- a/src/pages/docs/test-management/test-runs/share-test-runs.md +++ b/src/pages/docs/test-management/test-runs/share-test-runs.md @@ -22,11 +22,11 @@ contextual_links:
-**Learn how to generate and share public links for test runs in Test Management by Testsigma.** +**Learn how to generate and share public links for test runs in Arcus by Testsigma.** --- -You can share a test run with anyone on the internet by generating a public link in Test Management by Testsigma. This is useful when you want external stakeholders without account access to view testing progress. +You can share a test run with anyone on the internet by generating a public link in Arcus by Testsigma. This is useful when you want external stakeholders without account access to view testing progress. --- diff --git a/src/pages/docs/test-management/test-runs/test-run-properties.md b/src/pages/docs/test-management/test-runs/test-run-properties.md index 153fa1f..029f262 100644 --- a/src/pages/docs/test-management/test-runs/test-run-properties.md +++ b/src/pages/docs/test-management/test-runs/test-run-properties.md @@ -1,6 +1,6 @@ --- title: 'Test Run Properties' -page_title: 'Test Run Properties in Test Management by Testsigma' +page_title: 'Test Run Properties in Arcus by Testsigma' metadesc: 'Learn about test run properties in Testsigma Test Management. Structure, manage, and track test runs effectively to improve efficiency and ensure accurate reporting.' noindex: false order: 7.4 @@ -23,13 +23,13 @@ contextual_links: --- -Test run properties define the attributes that help teams structure, manage, and track test statuses. A well-organized test run improves efficiency and ensures accurate reporting, enabling teams to maintain quality. This article discusses test run properties in Test Management by Testsigma. +Test run properties define the attributes that help teams structure, manage, and track test statuses. A well-organized test run improves efficiency and ensures accurate reporting, enabling teams to maintain quality. This article discusses test run properties in Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that a project is created in Test Management by Testsigma and test cases are available for creating test runs. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/), [Test Cases](https://testsigma.com/docs/test-management/test-cases/manage-test-cases/) and [Test Runs](https://testsigma.com/docs/test-management/test-runs/create-test-runs/). +> Before you begin, ensure that a project is created in Arcus by Testsigma and test cases are available for creating test runs. For more information, see [Projects](https://testsigma.com/docs/test-management/projects/manage-projects/), [Test Cases](https://testsigma.com/docs/test-management/test-cases/manage-test-cases/) and [Test Runs](https://testsigma.com/docs/test-management/test-runs/create-test-runs/). --- diff --git a/src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md index 769b9d1..c4e7674 100644 --- a/src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Automate Manual Test Cases in Testsigma' -page_title: 'Automate Manual Test Cases from Test Management by Testsigma in Testsigma' -metadesc: 'Automate manual test cases from Test Management by Testsigma in Testsigma using Atto’s AI. Learn how to generate automated steps and begin Agentic Learning.' +page_title: 'Automate Manual Test Cases from Arcus by Testsigma in Testsigma' +metadesc: 'Automate manual test cases from Arcus by Testsigma in Testsigma using Atto’s AI. Learn how to generate automated steps and begin Agentic Learning.' noindex: false order: 11.4 page_id: 'automate-manual-test-cases-in-testsigma' @@ -28,17 +28,17 @@ contextual_links:
-**Automate manual test cases from Test Management by Testsigma in Testsigma using Atto’s AI.** +**Automate manual test cases from Arcus by Testsigma in Testsigma using Atto’s AI.** --- -You can automate manual test cases created in Test Management by Testsigma using Testsigma. Once you create a manual test case, click Automate with Atto’s AI in Test Management by Testsigma. Then select the Testsigma project, application, and version in which you want to automate the test case. The system creates a session in Atto’s Home for the selected project, where you can automate the test case using Atto. This article discusses the steps to automate manual test cases from Test Management by Testsigma in Testsigma. +You can automate manual test cases created in Arcus by Testsigma using Testsigma. Once you create a manual test case, click Automate with Atto’s AI in Arcus by Testsigma. Then select the Testsigma project, application, and version in which you want to automate the test case. The system creates a session in Atto’s Home for the selected project, where you can automate the test case using Atto. This article discusses the steps to automate manual test cases from Arcus by Testsigma in Testsigma. --- > ## **Prerequisites** > Before you begin, ensure that: -> - The Test Management by Testsigma integration with Testsigma is enabled. +> - The Arcus by Testsigma integration with Testsigma is enabled. > - Testsigma’s Live Editor is ready. --- diff --git a/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md b/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md index eade408..414969a 100644 --- a/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md @@ -1,7 +1,7 @@ --- -title: 'Testsigma Integration for Test Management by Testsigma' -page_title: 'Testsigma Integration for Test Management by Testsigma' -metadesc: 'Testsigma Integration with Test Management by Testsigma ensures complete visibility by synchronizing test coverage, execution results, and logs across manual & automated tests.' +title: 'Testsigma Integration for Arcus by Testsigma' +page_title: 'Testsigma Integration for Arcus by Testsigma' +metadesc: 'Testsigma Integration with Arcus by Testsigma ensures complete visibility by synchronizing test coverage, execution results, and logs across manual & automated tests.' noindex: false order: 11.1 page_id: 'testsigma-for-tms' @@ -16,7 +16,7 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Integrate Test Management by Testsigma with Testsigma' + name: 'Integrate Arcus by Testsigma with Testsigma' url: '#integrate-test-management-by-testsigma-with-testsigma' --- @@ -26,7 +26,7 @@ contextual_links: --- -The integration between Testsigma and Test Management by Testsigma provides a unified view of both manual and automated testing. It links automated tests in Testsigma with their corresponding manual test cases in Test Management by Testsigma. +The integration between Testsigma and Arcus by Testsigma provides a unified view of both manual and automated testing. It links automated tests in Testsigma with their corresponding manual test cases in Arcus by Testsigma. This two-way synchronization ensures that execution results, logs, and screenshots are automatically updated in real time. The integration improves traceability, eliminates duplicate efforts, and provides complete visibility into test coverage and overall quality. @@ -35,7 +35,7 @@ This two-way synchronization ensures that execution results, logs, and screensho > ## **Prerequisites** > -> Before you begin, ensure you have an Enterprise plan for both Testsigma and Test Management by Testsigma. +> Before you begin, ensure you have an Enterprise plan for both Testsigma and Arcus by Testsigma. --- @@ -50,11 +50,11 @@ This two-way synchronization ensures that execution results, logs, and screensho --- -## **Integrate Test Management by Testsigma with Testsigma** +## **Integrate Arcus by Testsigma with Testsigma** -You can enable the integration either from Test Management by Testsigma or directly from Testsigma. +You can enable the integration either from Arcus by Testsigma or directly from Testsigma. -**a. Enable from Test Management by Testsigma** +**a. Enable from Arcus by Testsigma** 1. From the **Dashboard**, go to **Settings > Integrations**. @@ -67,8 +67,8 @@ You can enable the integration either from Test Management by Testsigma or direc 1. From the left navigation bar, go to **Settings > Integrations**. -2. Turn on the toggle next to Test Management by Testsigma. - ![Test Management by Testsigma Toggle](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/TMS_Toggle_In_Testsigma.png) +2. Turn on the toggle next to Arcus by Testsigma. + ![Arcus by Testsigma Toggle](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/TMS_Toggle_In_Testsigma.png) 3. The integration is now enabled successfully. diff --git a/src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md index 05cb6cb..6fb882e 100644 --- a/src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md @@ -1,7 +1,7 @@ --- title: 'Create & Sync Test Cases from Testsigma’s Atto’s Home' page_title: 'Create and Sync Test Cases from Testsigma’s Atto’s Home' -metadesc: 'Create & sync AI-generated test cases from Atto’s Home directly to Test Management by Testsigma. This article explains how to generate & sync Atto’s test cases into TMS.' +metadesc: 'Create & sync AI-generated test cases from Atto’s Home directly to Arcus by Testsigma. This article explains how to generate & sync Atto’s test cases into TMS.' noindex: false order: 11.5 page_id: 'create-and-sync-test-cases' @@ -22,18 +22,18 @@ contextual_links:
-**Create and sync AI-generated test cases from Atto’s Home directly to Test Management by Testsigma.** +**Create and sync AI-generated test cases from Atto’s Home directly to Arcus by Testsigma.** --- -You can sync newly generated test cases from Testsigma’s Atto’s Home to Test Management by Testsigma. Once the NLP steps are generated for AI-generated test cases in Atto’s Home, the system provides an option to create a new test case and sync with Test Management by Testsigma. This article discusses the two-way sync of AI-generated test cases between both systems. +You can sync newly generated test cases from Testsigma’s Atto’s Home to Arcus by Testsigma. Once the NLP steps are generated for AI-generated test cases in Atto’s Home, the system provides an option to create a new test case and sync with Arcus by Testsigma. This article discusses the two-way sync of AI-generated test cases between both systems. --- > ## **Prerequisites** > > Before you begin, ensure that: -> - The Test Management by Testsigma integration with Testsigma is enabled. +> - The Arcus by Testsigma integration with Testsigma is enabled. > - You have AI-generated test cases in Atto’s Home. --- @@ -69,10 +69,10 @@ You can sync newly generated test cases from Testsigma’s Atto’s Home to Test 8. Click the dropdown arrow next to **Accept**, and select **Accept & Sync with Testsigma TMS**. -9. In the **Sync with Test Management by Testsigma** dialog: +9. In the **Sync with Arcus by Testsigma** dialog: - Select a **Test Management** project and folder. - Click **Continue**. -10. The system creates a new test case in Test Management by Testsigma and links it to the Testsigma test case. +10. The system creates a new test case in Arcus by Testsigma and links it to the Testsigma test case. --- \ No newline at end of file diff --git a/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md b/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md index ab1b5e0..50a2724 100644 --- a/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md @@ -1,7 +1,7 @@ --- -title: 'Execute Test Plans from Test Management by Testsigma' -page_title: 'Execute Test Plans from Test Management by Testsigma' -metadesc: 'You can execute test plans in Testsigma directly from Test Management by Testsigma | Learn how to execute test plans of Testsigma from Test Management by Testsigma.' +title: 'Execute Test Plans from Arcus by Testsigma' +page_title: 'Execute Test Plans from Arcus by Testsigma' +metadesc: 'You can execute test plans in Testsigma directly from Arcus by Testsigma | Learn how to execute test plans of Testsigma from Arcus by Testsigma.' noindex: false order: 11.7 page_id: 'execute-test-plans-in-testsigma' @@ -16,26 +16,26 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Execute a Linked Test Plan in Test Management by Testsigma' + name: 'Execute a Linked Test Plan in Arcus by Testsigma' url: '#execute-a-linked-test-plan-in-test-management-by-testsigma' - type: link - name: 'View Automated Reports in Test Management by Testsigma' + name: 'View Automated Reports in Arcus by Testsigma' url: '#view-automated-reports-in-test-management-by-testsigma' ---
-**This integration lets you execute test plans in Testsigma from Test Management by Testsigma & automatically retrieves machine-level reports for each run.** +**This integration lets you execute test plans in Testsigma from Arcus by Testsigma & automatically retrieves machine-level reports for each run.** --- -You can execute test plans in Testsigma directly from Test Management by Testsigma. When you trigger an execution, Test Management by Testsigma creates a separate test run for each machine and imports machine-level reports, including the link to the result page. This article discusses executing Test Plans from Test Management by Testsigma. +You can execute test plans in Testsigma directly from Arcus by Testsigma. When you trigger an execution, Arcus by Testsigma creates a separate test run for each machine and imports machine-level reports, including the link to the result page. This article discusses executing Test Plans from Arcus by Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that the test plans are linked between Test Management by Testsigma and Testsigma. +> Before you begin, ensure that the test plans are linked between Arcus by Testsigma and Testsigma. --- @@ -51,9 +51,9 @@ You can execute test plans in Testsigma directly from Test Management by Testsig --- -## **Execute a Linked Test Plan in Test Management by Testsigma** +## **Execute a Linked Test Plan in Arcus by Testsigma** -1. Create or open the test plan you want to execute in Test Management by Testsigma. +1. Create or open the test plan you want to execute in Arcus by Testsigma. 2. In the test plan details page, under **Testsigma Automated Test Plan**, click **Link a Test Plan** if the plan is not yet linked. @@ -64,7 +64,7 @@ You can execute test plans in Testsigma directly from Test Management by Testsig 4. After linking, click the **Play icon** next to the linked **Testsigma Automated Test Plan** to trigger execution. -2. After execution completes in Testsigma, Test Management by Testsigma automatically creates a test run for each machine with the associated test cases. +2. After execution completes in Testsigma, Arcus by Testsigma automatically creates a test run for each machine with the associated test cases. 3. Open the test run in the test plan to view execution details. The run includes links to the individual test case results pages for each executed test case. @@ -73,7 +73,7 @@ You can execute test plans in Testsigma directly from Test Management by Testsig --- -## **View Automated Reports in Test Management by Testsigma** +## **View Automated Reports in Arcus by Testsigma** 1. From the left navigation bar, go to **Test Plans**. diff --git a/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md index b49a3c7..da0421f 100644 --- a/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md @@ -1,7 +1,7 @@ --- -title: 'Link Test Cases Between Test Management by Testsigma & Testsigma' -page_title: 'Link Test Cases Between Test Management by Testsigma & Testsigma' -metadesc: 'Two-way test case sync ensures consistent traceability & seamless alignment between Test Management by Testsigma and Testsigma.' +title: 'Link Test Cases Between Arcus by Testsigma & Testsigma' +page_title: 'Link Test Cases Between Arcus by Testsigma & Testsigma' +metadesc: 'Two-way test case sync ensures consistent traceability & seamless alignment between Arcus by Testsigma and Testsigma.' noindex: false order: 11.3 page_id: 'link-tests-in-testsigma-and-tms' @@ -16,7 +16,7 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Link Test Cases in Test Management by Testsigma' + name: 'Link Test Cases in Arcus by Testsigma' url: '#link-test-cases-in-test-management-by-testsigma' - type: link name: 'Link Test Cases in Testsigma' @@ -29,9 +29,9 @@ contextual_links: --- -You can link test cases between Test Management by Testsigma and Testsigma to maintain a single, synchronized source of truth for all your tests. +You can link test cases between Arcus by Testsigma and Testsigma to maintain a single, synchronized source of truth for all your tests. -Manual test cases created in Test Management by Testsigma can be directly pushed to Testsigma as automated test cases. Similarly, automated test cases in Testsigma can be pushed to Test Management by Testsigma as manual test cases with detailed steps. +Manual test cases created in Arcus by Testsigma can be directly pushed to Testsigma as automated test cases. Similarly, automated test cases in Testsigma can be pushed to Arcus by Testsigma as manual test cases with detailed steps. This two-way linkage eliminates redundancy, improves traceability, and ensures alignment between manual and automated testing efforts across both systems. @@ -39,7 +39,7 @@ This two-way linkage eliminates redundancy, improves traceability, and ensures a > ## **Prerequisites** > -> Before you begin, ensure that the integration between Testsigma and Test Management by Testsigma is enabled and that test cases are available in both systems. +> Before you begin, ensure that the integration between Testsigma and Arcus by Testsigma is enabled and that test cases are available in both systems. --- @@ -54,7 +54,7 @@ This two-way linkage eliminates redundancy, improves traceability, and ensures a --- -## **Link Test Cases in Test Management by Testsigma** +## **Link Test Cases in Arcus by Testsigma** 1. From the **Dashboard**, go to **Test Cases**. diff --git a/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md index 316cbc7..8819409 100644 --- a/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md @@ -1,7 +1,7 @@ --- -title: 'Link Test Plans Between Test Management by Testsigma & Testsigma' -page_title: 'Link Test Plans Between Test Management by Testsigma & Testsigma' -metadesc: 'The Test Management by Testsigma & Testsigma integration streamlines execution by connecting test plans between both systems & providing centralized access to detailed results.' +title: 'Link Test Plans Between Arcus by Testsigma & Testsigma' +page_title: 'Link Test Plans Between Arcus by Testsigma & Testsigma' +metadesc: 'The Arcus by Testsigma & Testsigma integration streamlines execution by connecting test plans between both systems & providing centralized access to detailed results.' noindex: false order: 11.6 page_id: 'link-test-plans-in-testsigma-and-tms' @@ -16,7 +16,7 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Link Test Plans in Test Management by Testsigma' + name: 'Link Test Plans in Arcus by Testsigma' url: '#link-test-plans-in-test-management-by-testsigma' - type: link name: 'Link Test Plans in Testsigma' @@ -29,13 +29,13 @@ contextual_links: --- -You can link test plans between Test Management by Testsigma and Testsigma to execute test plans in Testsigma directly from Test Management by Testsigma. Once the execution is complete, you can view machine-level reports with logs and screenshots. This article discusses linking test plans between Test Management by Testsigma and Testsigma. +You can link test plans between Arcus by Testsigma and Testsigma to execute test plans in Testsigma directly from Arcus by Testsigma. Once the execution is complete, you can view machine-level reports with logs and screenshots. This article discusses linking test plans between Arcus by Testsigma and Testsigma. --- > ## **Prerequisites** > -> Before you begin, ensure that the integration between Testsigma and Test Management by Testsigma is enabled and that test plans are available in both systems. +> Before you begin, ensure that the integration between Testsigma and Arcus by Testsigma is enabled and that test plans are available in both systems. --- @@ -50,7 +50,7 @@ You can link test plans between Test Management by Testsigma and Testsigma to ex --- -## **Link Test Plans in Test Management by Testsigma** +## **Link Test Plans in Arcus by Testsigma** 1. From the **Dashboard**, go to **Test Plans**. @@ -71,7 +71,7 @@ You can link test plans between Test Management by Testsigma and Testsigma to ex 1. From the left navigation bar, go to **Test Plans**. -2. Open the test plan you want to link with Test Management by Testsigma, and click **Test Plan Details** from the **Utility Panel**. +2. Open the test plan you want to link with Arcus by Testsigma, and click **Test Plan Details** from the **Utility Panel**. 3. Click **+ Link New Plans** and select **Testsigma Test Management**. The **Link Test Plan** dialog opens. diff --git a/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md b/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md index efb1890..445d269 100644 --- a/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md +++ b/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md @@ -1,7 +1,7 @@ --- -title: 'Managing Users in Testsigma & Test Management by Testsigma' -page_title: 'Manage Users in Testsigma & Test Management by Testsigma' -metadesc: 'Testsigma & Test Management by Testsigma integration also provides unified user management, allowing you to control access for both products from a single interface.' +title: 'Managing Users in Testsigma & Arcus by Testsigma' +page_title: 'Manage Users in Testsigma & Arcus by Testsigma' +metadesc: 'Testsigma & Arcus by Testsigma integration also provides unified user management, allowing you to control access for both products from a single interface.' noindex: false order: 11.2 page_id: 'manage-users-in-testsigma-and-tms' @@ -16,7 +16,7 @@ contextual_links: name: 'Interactive Demo' url: '#interactive-demo' - type: link - name: 'Add Users in Test Management by Testsigma' + name: 'Add Users in Arcus by Testsigma' url: '#add-users-in-test-management-by-testsigma' - type: link name: 'Add Users in Testsigma' @@ -29,21 +29,21 @@ contextual_links: --- -You can manage user access across both Testsigma and Test Management by Testsigma from a single interface. When inviting users, you can choose to add them to either one or both products by selecting the relevant checkbox in the invite dialog. +You can manage user access across both Testsigma and Arcus by Testsigma from a single interface. When inviting users, you can choose to add them to either one or both products by selecting the relevant checkbox in the invite dialog. -In Testsigma, you can add new users, assign project-level roles, and optionally add them to Test Management by Testsigma. Similarly, in Test Management by Testsigma, you can invite users and choose to add them to Testsigma. +In Testsigma, you can add new users, assign project-level roles, and optionally add them to Arcus by Testsigma. Similarly, in Arcus by Testsigma, you can invite users and choose to add them to Testsigma. This unified user management approach helps maintain consistent access, simplifies onboarding, and ensures seamless collaboration across both platforms. [[info | **NOTE**:]] -| You must enable the Test Management by Testsigma & Testsigma integration to manage users from both systems. +| You must enable the Arcus by Testsigma & Testsigma integration to manage users from both systems. --- > ## **Prerequisites** > -> Before you begin, ensure that the Test Management by Testsigma integration with Testsigma is enabled. +> Before you begin, ensure that the Arcus by Testsigma integration with Testsigma is enabled. --- @@ -58,7 +58,7 @@ This unified user management approach helps maintain consistent access, simplifi --- -## **Add Users in Test Management by Testsigma** +## **Add Users in Arcus by Testsigma** 1. From the **Dashboard**, click **Invite Users**. This opens the **Users** section under **Settings**. @@ -82,7 +82,7 @@ This unified user management approach helps maintain consistent access, simplifi 3. In the **Add New User** dialog: - Enter the email address. - - Select **Add User in Test Management by Testsigma** if you also want to add the user in Test Management by Testsigma. + - Select **Add User in Arcus by Testsigma** if you also want to add the user in Arcus by Testsigma. - Select the projects and assign the appropriate roles. - Click **Send Invite**. From a30e2db95676156d39bba269c0ad54ec240667c4 Mon Sep 17 00:00:00 2001 From: Bharath Krishna <118433150+bharathk08@users.noreply.github.com> Date: Tue, 18 Aug 2026 19:38:42 +0530 Subject: [PATCH 3/3] minor changes --- src/pages/docs/test-management/index.jsx | 2 +- .../test-management/introduction/overview.md | 17 +++++++++++++++-- 2 files changed, 16 insertions(+), 3 deletions(-) diff --git a/src/pages/docs/test-management/index.jsx b/src/pages/docs/test-management/index.jsx index 2e0aea9..18974fe 100644 --- a/src/pages/docs/test-management/index.jsx +++ b/src/pages/docs/test-management/index.jsx @@ -21,7 +21,7 @@ const IndexContent = () => {

- SETUP | PLAN | AUTHOR | ORGANIZE | EXECUTE | REPORT + The complete test management platform for modern QA teams.
diff --git a/src/pages/docs/test-management/introduction/overview.md b/src/pages/docs/test-management/introduction/overview.md index b92abc2..f3e9f27 100644 --- a/src/pages/docs/test-management/introduction/overview.md +++ b/src/pages/docs/test-management/introduction/overview.md @@ -12,6 +12,9 @@ contextual_links: - type: link name: 'Benefits of Using Arcus by Testsigma' url: '#benefits-of-using-testsigma-test-management' + - type: link + name: 'Quality Intelligence' + url: '#quality-intelligence' --- --- @@ -42,8 +45,18 @@ Document every test case for thorough and consistent testing. Log and track defects instantly with Jira integration. -### 🤖 **AI-Powered Productivity with ATTO (Agentic AI)** +### 🧠 **Quality Intelligence, Powered by AI** + +Generate test cases from your requirements, track coverage as you go, and get a real-time read on release readiness, all without leaving Arcus. + +--- + +## **Quality Intelligence** + +Quality Intelligence is where AI does the heavy lifting for you. Point it at your requirements, whether that's a Jira story, a Confluence page, a Figma design, or your developers' pull requests, and it generates test cases, tracks coverage against your modules, builds test plans, and can even automate execution. + +Instead of writing test cases from scratch, you review what Quality Intelligence generates, accept the ones that are accurate, and save them to your library. Coverage, test plans, and five key quality metrics, Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate, update automatically as you go, so you always know how confident you can be in your current build. -Leverage ATTO's capabilities to autonomously create tests, execute them, and report bugs. +See [Overview: QI Home](https://testsigma.com/docs/test-management/qi-home/overview/) to learn how test generation, coverage tracking, and automation work together in Quality Intelligence. ---