Skip to content

test(at): adapt editor AT selectors for accessibility update - #517

Merged
deepin-bot[bot] merged 1 commit into
linuxdeepin:masterfrom
dengzhongyuan365-dev:master
Aug 12, 2026
Merged

test(at): adapt editor AT selectors for accessibility update#517
deepin-bot[bot] merged 1 commit into
linuxdeepin:masterfrom
dengzhongyuan365-dev:master

Conversation

@dengzhongyuan365-dev

@dengzhongyuan365-dev dengzhongyuan365-dev commented Aug 12, 2026

Copy link
Copy Markdown
Member

Log: 适配新版文本编辑器AT元素名称

Influence: 修复新版6.5.58中AT元素名称变化导致的自动化用例失败,保持32条AT用例全量通过。

Summary by Sourcery

Update automated accessibility tests to align with the renamed text editor AT elements in version 6.5.58.

Bug Fixes:

  • Fix failures in existing AT editor automation caused by changes to element names in the new text editor accessibility update.

Tests:

  • Refresh element mappings and suites in multiple v25_2500 AT modules so all 32 editor-related AT cases continue to pass against the updated editor.

Log: 适配新版文本编辑器AT元素名称

Influence: 修复新版6.5.58中AT元素名称变化导致的自动化用例失败,保持32条AT用例全量通过。

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

sourcery-ai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates AT test YAML configurations to match the renamed accessibility (AT) elements in the new text editor, ensuring existing automation suites continue to pass against version 6.5.58.

File-Level Changes

Change Details Files
Update case-to-element mappings in AT test configuration to reflect new editor AT element names.
  • Adjusted mapped case identifiers to reference updated AT element definitions for the new editor.
  • Ensured all affected modules’ cases_mapped.yaml files align with the renamed accessibility elements.
  • Kept overall case structure and counts unchanged while only updating mappings.
tests/at/modules/v25_2500_…_114347/cases_mapped.yaml
tests/at/modules/v25_2500_…_132443/cases_mapped.yaml
tests/at/modules/v25_2500_…_114345/cases_mapped.yaml
tests/at/modules/v25_2500_…_114343/cases_mapped.yaml
Align suite definitions with updated accessibility element naming for the text editor.
  • Updated .suite.yaml test suite entries to use the new AT element names where referenced.
  • Maintained existing suite composition and ordering while only changing selector/name references.
tests/at/modules/v25_2500_…_114347/yaml/...114347.suite.yaml
tests/at/modules/v25_2500_…_132443/yaml/...132443.suite.yaml
tests/at/modules/v25_2500_…_114345/yaml/...114345.suite.yaml
tests/at/modules/v25_2500_…_114343/yaml/...114343.suite.yaml
Update shared AT element definitions for editor-related tests to the new accessibility naming scheme.
  • Modified elements.yaml entries so logical element keys now correspond to the renamed editor AT elements in 6.5.58.
  • Kept element taxonomy stable (same set of elements) while only updating labels/selectors for compatibility.
  • Ensured consistency of element naming across all impacted modules.
tests/at/modules/v25_2500_…_114347/yaml/elements.yaml
tests/at/modules/v25_2500_…_132443/yaml/elements.yaml
tests/at/modules/v25_2500_…_114345/yaml/elements.yaml
tests/at/modules/v25_2500_…_114343/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

@deepin-ci-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details Needs approval from an approver in each of these files:

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

@dengzhongyuan365-dev

Copy link
Copy Markdown
Member Author

/merge

@deepin-bot
deepin-bot Bot merged commit 5dc0b3b into linuxdeepin:master Aug 12, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants