Menu

1 / 4

Agentic Browser Testing with tamesu: Tell the Browser What the User Wants

DEV Community: go·Xavier Portilla Edo·3 days ago
#ieBFMqUt
#devtogo#devto#dev#btn#user
Reading 0:00
15s threshold

Introduction

End-to-end tests have a bad name, and selectors are the reason. A test clicks #btn-add-42 . Someone renames the id, and the test fails. Nothing is wrong with the shop. The test was never about the shop. It was about the HTML.

A person does not use a web page that way. A person wants something: "log in", "add the first laptop bag to the cart". They find the button by what it says.

tamesu (試す, Japanese for to try, to test ) lets you write tests that way. It is an open-source CLI written in Go. You describe a step in plain language. A browser agent (a model that reads the page and picks the next action) drives a real Chromium until the step is done. Then tamesu saves what the agent did, so the next run replays it without calling the model.

This is the first of two articles about tamesu. This one covers web apps.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.