DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to confirm a like or count changes by exactly one with DSH Android

Tap a row action in a list and check that its counter moved by exactly plus or minus one.

Authorization notice. DSH Android is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA product tester checking that a like, follow, or favorite button updates its count correctly in a feed.

The problemManually confirming that a counter changed by the right amount on each row is tedious and easy to misread.

The outcomeThe row is tapped at a known position and the counter change is verified automatically.

What you need first

  • A DeepSeek Harness (DSH) host, tested by the author with DSH 0.1.5-rc.1
  • adb available on the machine so the plugin can resolve it
  • A running Android emulator or a USB-connected Android phone
  • For builds: a Gradle project that has ./gradlew

Steps

  1. Call android_ui_rows on the streamed device to read the list as rows, each with an index and a counter key.
  2. Pick the row index and the counter key you want to test from that output.
  3. Call android_tap_row with that index and expect_count set to the counter key with delta 1.
  4. Read the verification in the result, which checks the counter moved by exactly the expected amount.
  5. If the key is unknown, the tap is refused, so copy the key exactly as listed.

Prompt for your agent

Using the dsh-android plugin, call android_ui_rows on the streamed device, then call android_tap_row with index <row index> and expect_count set to {key: <counter key from the listing>, delta: 1}. Expected output: a result showing the counter's before and after values and whether it moved by exactly 1. Verify the result reports a match before marking the test as passed.

Caveat. The counter parsing depends on the label format the app uses, so an unusual label may not produce a counter key.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page