test(at): add AT-SPI suites for deepin editor

[dengzhongyuan365-dev]

Add executable AT-SPI suites and source case file for editor cases.

新增文本编辑器AT-SPI自动化用例和原始用例文件。

Log: 新增文本编辑器AT-SPI自动化用例

Influence: 增加19条已验证通过的AT自动化用例，覆盖基础、冒烟和主菜单场景。

Summary by Sourcery

Add AT-SPI automation test assets for the deepin editor, wiring existing manual cases into executable suites grouped by modules.

Tests:

• Introduce cases_raw.yaml containing the full catalog of deepin editor manual test cases for AT-SPI automation.
• Add plan.yaml defining module groupings, case IDs, and recording guides for deepin editor accessibility tests.
• Generate per-module AT-SPI suite YAMLs and element mapping files for main editor, smoke, and main-menu scenarios to support automated execution.

[sourcery-ai]

Sorry @dengzhongyuan365-dev, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[sourcery-ai]

Reviewer's Guide

Adds AT-SPI automation suites for deepin-editor by importing manual test cases from an Excel source into structured YAML, defining module-level suite metadata, element trees, and case mappings, and registering them in a top-level AT plan.

File-Level Changes

Change	Details	Files
Introduce raw manual test case corpus for deepin-editor as YAML to serve as the single source for AT-SPI suite generation.	Add tests/at/cases_raw.yaml containing all deepin-editor cases exported from the Excel source with metadata, IDs, and step definitions. Ensure each case encodes actions/asserts, module path, and flags like needs_accessible_name to feed downstream suite generators.	tests/at/cases_raw.yaml
Register deepin-editor into the global AT-SPI plan with module segmentation and recording guidance.	Create tests/at/plan.yaml describing the deepin-editor app, grouping case IDs into logical modules (主菜单, 冒烟测试, 工作区, 安全性, 安装/卸载/启动/关机, 硬件交互). Mark which modules are verified vs pending and embed per-module recording_guide text for manual recording. Record created_at timestamps and overall app identifier for orchestration tooling.	tests/at/plan.yaml
Define per-module AT-SPI suites, element trees, and case mappings for editor modules, wiring them into the AT framework.	Add module directories under tests/at/modules for the base 文本编辑器 module (#110607), 主菜单 (#114347), and 冒烟测试 (#132443) with localized names encoded in paths. For each module, add at-tree.yaml and at-tree-annotated.yaml describing the accessible UI tree structure used by the AT runner. Add cases_mapped.yaml and cases_non_gui.yaml splitting GUI vs non-GUI cases and mapping raw case IDs to suite cases. Add element_gaps.yaml and yaml/elements.yaml to describe or track coverage of UI elements versus cases. Add yaml/*.suite.yaml and suite-cases.yaml to define suite-level metadata (names, included case IDs, and statuses) for each module.	tests/at/modules/.../at-tree-annotated.yaml tests/at/modules/.../at-tree.yaml tests/at/modules/.../cases_mapped.yaml tests/at/modules/.../cases_non_gui.yaml tests/at/modules/.../element_gaps.yaml tests/at/modules/.../suite-cases.yaml tests/at/modules/.../yaml/*.suite.yaml tests/at/modules/.../yaml/elements.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dengzhongyuan365-dev, lzwind

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dengzhongyuan365-dev]

/merge

[deepin-bot]

This pr cannot be merged! (status: unstable)

[dengzhongyuan365-dev]

/forcemerge