Rill
← All articles

Guides

How to test a mobile menu built by an AI agent

The Rill Team

Your coding agent adds a mobile menu. The screenshot looks fine. You tap Pricing, the right page loads, and the menu closes. Then you swipe up and the page won’t move.

When you check a change like this, follow one link and keep recording until you’ve tried to use the page you land on.

Test what happens after the tap

A menu that covers the screen can keep the page behind it from scrolling. Once the menu closes, your swipe should move the page again.

Start on the homepage in a phone-sized browser.

  1. Open the menu. Make sure you can see and tap Pricing. If you can’t reach it, record where you got stuck.
  2. Tap Pricing. Look for the heading or section you expected and check that the menu is out of the way. If the link opens another page, check the path too.
  3. Swipe up on the page. Start on the page content and see if the next section comes into view. If everything fits on one screen, you’ll need a longer page to tell whether scrolling works.
  4. Reopen and close the menu. Stay on Pricing if it uses the same header. Otherwise, pick a page with that header and more content below the fold. Tap the close button and try the same swipe again.

If scrolling fails only after the link tap, compare how the link and the close button dismiss the menu. Look for a scroll lock or an overlay that’s still in place after navigation.

Give the agent a task it can finish

Use a preview build or test page. Swap in your own path and heading.

Mobile menu check

Test on mobile. Tell me the browser and viewport you used.
Start at the homepage. Open the menu and tap Pricing.
Check that /pricing loads, the Pricing heading is visible, and the menu is closed.
Swipe up on the page. Look for the next section. If all the content fits on
one screen, mark the scroll check inconclusive.
Reopen the menu, dismiss it with the close button, and try the same swipe again.

Record the whole flow. Give me the result and a timestamp for each step.
Say where you got stuck or what you couldn’t check. Leave the code and
forms untouched.

Leave a review note someone can act on

In this synthetic example, the Pricing page has a section called “What’s included” below the fold. Watch the two swipes. The orange dot marks each touch.

Open the replay as MP4

Here’s the note I’d put next to the replay in a pull request.

Mobile menu check · Chromium with touch emulation · 360 × 800

00:02 The menu is open and Pricing is visible.

00:04 The Pricing heading appears at /pricing and the menu has closed.

00:05–00:07 A swipe up leaves the page at the top. “What’s included” stays below the fold.

00:10 The close button dismisses the reopened menu.

00:12 The same swipe brings “What’s included” into view.

Next check. Compare how the Pricing link and the close button release the page scroll lock.

Once you have a fix, start at the homepage and try the link and swipe again. If someone reported the bug in iPhone Safari, on Android, or with a screen reader, repeat the flow in that environment and name it in your note.

Try it on your own site

Give Rill Browser Check a public URL and the steps above. Start the task with “test on mobile.” Rill opens a touch-enabled Chromium browser at 360 × 800. In the replay, watch what happens on the first swipe after the menu closes. Open Rill Browser Check.