Add HMNextAuto - HarmonyOS NEXT UI automation framework

[ziguiway]

Add HMNextAuto to UI Testing section.

• HMNextAuto - Python-based UI automation framework for HarmonyOS NEXT
• API compatible with uiautomator2, supports XPath, image recognition, performance monitoring and notification management

Summary by Sourcery

Documentation:

• Document the HMNextAuto Python-based UI automation framework, including its compatibility with uiautomator2 and key capabilities.

[semanticdiff-com]

Review changes with  

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds HMNextAuto, a Python-based UI automation framework for HarmonyOS NEXT, to the README’s UI Testing section as a new listed resource with a descriptive one-line summary.

File-Level Changes

Change	Details	Files
Add HMNextAuto as a new UI testing resource entry in the README with a brief capability description.	Insert a new bullet in the UI Testing list referencing the HMNextAuto GitHub repository. Describe HMNextAuto as a Python-based UI automation framework for HarmonyOS NEXT. Note API compatibility with uiautomator2 and list key supported features such as XPath, image recognition, performance monitoring, and notification management.	README.md

---

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.

[qodo-code-review]

Review Summary by Qodo

Add HMNextAuto UI automation framework to README

✨ Enhancement 📝 Documentation

Walkthroughs

Description

• Add HMNextAuto to UI Testing section
• Includes framework description with key features

Diagram

flowchart LR
  README["README.md"] -- "Add HMNextAuto entry" --> UITesting["UI Testing Section"]
  UITesting -- "Framework details" --> Features["XPath, Image Recognition,<br/>Performance Monitoring"]

Loading

File Changes

1. README.md 📝 Documentation +1/-0

Add HMNextAuto framework documentation entry

• Added HMNextAuto entry to UI Testing section
• Included link to GitHub repository
• Documented framework features: XPath, image recognition, performance monitoring, notification
 management
• Noted API compatibility with uiautomator2

README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Unsorted UI Testing entry ☑ 🐞 Bug ⚙ Maintainability

Description

The new HMNextAuto bullet is appended to the end of the “UI Testing” list, breaking the section’s
alphabetical ordering and reducing discoverability/maintainability of this curated list.

Code

README.md[269]

+- [HMNextAuto](https://github.com/ziguiway/hmnextauto) - Python-based UI automation framework for HarmonyOS NEXT. API compatible with uiautomator2, supports XPath, image recognition, performance monitoring and notification management.

Evidence

The “UI Testing” section is ordered alphabetically by project name (e.g., aria-testing → Flybirds →
Golem → helium → Lost Pixel … → splinter → squape). The newly added “HMNextAuto” (HM…) should appear
between “helium” (he…) and “Lost Pixel” (Lo…), not after “squape” (sq…).

README.md[252-270]
README.md[241-250]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The `HMNextAuto` entry is placed at the end of the `## UI Testing` list, which breaks the list’s alphabetical order.
### Issue Context
The surrounding items in `## UI Testing` are alphabetized by name; keeping this ordering helps readers find entries and reduces merge conflicts when multiple items are added over time.
### Fix Focus Areas
- README.md[252-270]
### Expected change
Move the `HMNextAuto` bullet so it appears between `helium` and `Lost Pixel`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider shortening and aligning the HMNextAuto description with the style of neighboring entries (e.g., avoid a long multi-clause sentence and optionally drop the trailing period) to keep the list concise and consistent.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider shortening and aligning the HMNextAuto description with the style of neighboring entries (e.g., avoid a long multi-clause sentence and optionally drop the trailing period) to keep the list concise and consistent.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request adds HMNextAuto, a Python-based UI automation framework for HarmonyOS NEXT, to the README. The reviewer noted that the list is organized alphabetically and suggested moving the new entry to its correct position to maintain consistency.

[gemini-code-assist]

The items in the UI Testing section are organized alphabetically. HMNextAuto should be moved to its correct alphabetical position to maintain consistency with the rest of the list. It should be placed after helium and before Lost Pixel (around line 257).

[llamapreview]

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR only contains documentation changes (1 files)

Technical Context:

Documentation changes typically include:

• Markdown/RST file updates
• API documentation
• Code comments
• README updates
• Documentation in /docs directory
• License and contribution files

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team

[ziguiway]

The pre-commit failure is a DNS resolution issue for �wesome.re (existing link in README), not related to this change. Could a maintainer re-run the checks?