# Mobile GPS location, chat-driven device presets, and PR page pagination

> 10 updates: Set a GPS location for mobile device presets, Agents identify list and table items by content, not position, Archive test plans through the…

Source: https://qa.tech/changelog/2026-06-22

---
10 updates shipped on June 22, 2026.

In this release

1.  01[Set a GPS location for mobile device presets](#2026-06-22-mobile-device-preset-gps-location)Highlight
2.  02[Agents identify list and table items by content, not position](#2026-06-22-agents-track-items-by-content)
3.  03[Archive test plans through the chat assistant](#2026-06-22-archive-test-plans-from-chat)
4.  04[Change-review Action now updates the GitHub PR check](#2026-06-22-change-review-action-updates-pr-check)
5.  05[Console and network logs visible on the final assessment step](#2026-06-22-console-network-logs-on-assessment-step)
6.  06[Custom Fields documented, and configs explained as variables](#2026-06-22-custom-fields-docs-configs-as-variables)
7.  07[Device preset egress regions now available in chat](#2026-06-22-device-preset-egress-regions-in-chat)
8.  08[Device preset settings visible before enabling mobile testing](#2026-06-22-device-preset-settings-visible-before-enabling)
9.  09[PR Review check unblocks GitHub auto-merge](#2026-06-22-pr-review-check-unblocks-auto-merge)
10.  10[Pagination and PR number search on the Pull Requests page](#2026-06-22-pull-requests-page-pagination-and-search)

1.  Highlight
    
    Featured this release
    
    ## Set a GPS location for mobile device presets
    
    Mobile tests can now start with a specific GPS location – pick a region, enter custom coordinates, or use the device default.
    
    The device preset editor for iOS and Android on [mobile testing](https://qa.tech/product/mobile-testing) now includes a Location control. Default lets the device report its own location; Region picks a country or US state and fills in the coordinates automatically; Custom accepts any latitude and longitude with an optional label. The GPS is applied to the device before your app boots, so apps that read location on launch see it immediately. Network capture and traffic routing are unaffected.
    
    [\# Direct link](#2026-06-22-mobile-device-preset-gps-location)
    
2.  Update 02 of 10
    
    ## Agents identify list and table items by content, not position
    
    Verifications on rows in a list or table are more reliable, even on long tests where earlier screenshots are pruned.
    
    When a test deletes, updates, or otherwise acts on a specific row in a list or table, the agent later has to confirm the outcome. Agents now anchor that verification to an item's distinguishing text rather than its position, and correctly recognize that a different row shifting into where the acted-on one was is evidence of success. This makes list and table operations noticeably more robust on longer [web tests](https://qa.tech/product/web-testing) where earlier screenshots are pruned to stay within context limits.
    
    [\# Direct link](#2026-06-22-agents-track-items-by-content)
    
3.  Update 03 of 10
    
    ## Archive test plans through the chat assistant
    
    Ask the assistant to clean up old test plans and it now follows through, including cancelling their scheduled runs.
    
    The chat assistant could already create, rename, and modify test plans, but had no way to remove them – asking it to "archive the Smoke Tests plan" would fail. You can now ask it to archive one or several plans at once. Scheduled runs attached to the archived plans are cancelled automatically so they stop firing. The test cases inside remain intact.
    
    [\# Direct link](#2026-06-22-archive-test-plans-from-chat)
    
4.  Update 04 of 10
    
    ## Change-review Action now updates the GitHub PR check
    
    Triggering a review via the change-review GitHub Action or POST /v1/chat/change-review now moves the PR check from "Auto-review is off" to an active review – even when auto-review is turned off for the project.
    
    If your project has "Auto-review on pull requests" disabled and you kick off reviews on demand via the GitHub Action or the API, the GitHub check previously stayed stuck on "Auto-review is off" for the duration. It now correctly transitions to "QA.tech is reviewing this PR" as soon as the review starts, and reaches a pass or fail verdict when it completes. The merge gate works as expected regardless of how the review was triggered.
    
    [\# Direct link](#2026-06-22-change-review-action-updates-pr-check)
    
5.  Update 05 of 10
    
    ## Console and network logs visible on the final assessment step
    
    The tracer inspector now stays visible when you select the final assessment step, showing the full session's network and console logs alongside the verdict.
    
    On the test result page, selecting the final "Assess" step used to hide the Console, Network, Page, Test & Agent, and Graph inspector panels – you had to click a specific intermediate step to see them. The inspector now remains available on the assessment step, surfacing the entire run's network and console output, including any network errors, right below the verdict text.
    
    [\# Direct link](#2026-06-22-console-network-logs-on-assessment-step)
    
6.  Update 06 of 10
    
    ## Custom Fields documented, and configs explained as variables
    
    The Configs docs page now covers the Custom Fields config type and explains how configs work as reusable variables.
    
    The Custom Fields type – key-value pairs that the agent receives as `key: value` lines during each test run – is now documented at docs.qa.tech. The page also explains that configs are QA.tech's approach to variables: there's no `{{variable}}` placeholder syntax; the agent resolves config values from their name, description, and stored content at run time.
    
    [\# Direct link](#2026-06-22-custom-fields-docs-configs-as-variables)
    
7.  Update 07 of 10
    
    ## Device preset egress regions now available in chat
    
    Create or update a device preset through chat and set its egress region in the same request.
    
    When the device preset settings UI gained egress region support, the chat agent lagged behind – you could configure a region in settings but not through chat. The agent now accepts an egress region on preset creation and edits, validates it against your plan's enabled regions (listing valid choices if you pick an unavailable one), and auto-fills locale and timezone from the region's defaults unless you override them. Listing your presets now shows each one's current egress region too.
    
    [\# Direct link](#2026-06-22-device-preset-egress-regions-in-chat)
    
8.  Update 08 of 10
    
    ## Device preset settings visible before enabling mobile testing
    
    iOS and Android device preset sections now appear in Settings → Device Presets even when mobile testing isn't enabled on your account.
    
    Previously, the iOS and Android sections were hidden entirely if [mobile testing](https://qa.tech/product/mobile-testing) wasn't active for your account. They're now always visible: default presets are displayed alongside a "Talk to support" prompt so you can see what's available before committing. The "Create preset" button stays disabled and custom preset edit and delete actions are blocked until mobile testing is active on your account.
    
    [\# Direct link](#2026-06-22-device-preset-settings-visible-before-enabling)
    
9.  Update 09 of 10
    
    ## PR Review check unblocks GitHub auto-merge
    
    QA.tech PR Reviews set as a required status check no longer stall GitHub's auto-merge when a review concludes without changes requested.
    
    GitHub auto-merge requires every required check to end in a recognized terminal state. When a QA.tech review concluded inconclusively – a "comment" verdict, or a review manually unblocked via "Unblock merge" – the check was left in a state GitHub did not count as complete, causing auto-merge to stall. The check now concludes with "skipped", the non-blocking terminal state GitHub recognizes for required checks, so you can keep QA.tech [PR reviews](https://qa.tech/product/pr-testing) as a required status check without blocking auto-merge.
    
    [\# Direct link](#2026-06-22-pr-review-check-unblocks-auto-merge)
    
10.  Update 10 of 10
     
     ## Pagination and PR number search on the Pull Requests page
     
     The Pull Requests page now handles large lists with 25-per-page pagination and lets you jump to any PR by number.
     
     Page navigation appears automatically when your project has more than 25 synced pull requests. The current page is stored in the URL (`?page=2`), so links stay shareable and the browser back button works as expected. Switching any filter – state, repository, or search text – resets to page 1. To find a specific PR, type its number (with or without a `#`) in the search box.
     
     [\# Direct link](#2026-06-22-pull-requests-page-pagination-and-search)
     

## Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

[Get a demo](https://qa.tech/demo)

[QA.tech](https://qa.tech/)

SOC 2 Type 2 compliant

![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png)

### Product

-   [Platform overview](https://qa.tech/product)
-   [AI QA Testing](https://qa.tech/ai-qa-testing)
-   [Web Testing](https://qa.tech/product/web-testing)
-   [Mobile Testing](https://qa.tech/product/mobile-testing)
-   [PR Testing](https://qa.tech/product/pr-testing)
-   [MCP](https://qa.tech/product/mcp)
-   [Use cases](https://qa.tech/use-cases)
-   [Changelog](https://qa.tech/changelog)

### Compare

-   [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress)
-   [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright)
-   [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl)
-   [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf)
-   [AI vs Human QA](https://qa.tech/saas)

### Resources

-   [Docs](https://docs.qa.tech/)
-   [Blog](https://qa.tech/blog)
-   [Events](https://qa.tech/events)
-   [Pricing](https://qa.tech/pricing)
-   [Case Studies](https://qa.tech/case-studies)

### Company

-   [About](https://qa.tech/about-us)
-   [Partnerships](https://qa.tech/partnerships)
-   [Press](https://qa.tech/press)
-   [Contact Us](https://qa.tech/contact)
-   [Privacy Policy](https://qa.tech/privacy-policy)
-   [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf)
-   [Security & Compliance](https://trust.qa.tech/)

### Social

-   [](https://www.linkedin.com/company/qa-tech-ai/)
-   [](https://x.com/getqatech)
-   [](https://www.instagram.com/getqatech/)

© 2025 QA.tech. All rights reserved