正在加载视频...

视频加载失败

E2E tests can be generated automatically now. Argent lets you record Flows (sequences of interactions) and replay them later. Generating tests becomes part of the loop, making sure UI regressions never happen. 🛡️ Try it out now with the /argent-create-flow skill!

34,312 次观看 • 2 个月前 •via X (Twitter)

13 条评论

wcastand 的头像
wcastand2 个月前

Ahah watching agent device and argent tweeting the same feature the same day since day one is kind of funny 😁 Amazing tools both

Rodolfo Silva → salao365.com 的头像
Rodolfo Silva → salao365.com2 个月前

By by maestro :P

Ashish 的头像
Ashish2 个月前

Wow

gollyjer 的头像
gollyjer2 个月前

We LOVE Argent at @AwesomeLabsLLC

Anan7Tweets 的头像
Anan7Tweets2 个月前

How quick is the replay

AI Mastery Guide 的头像
AI Mastery Guide2 个月前

Recording flows to auto generate tests is a smart workflow.

Bharath 的头像
Bharath2 个月前

Does this support maestro?

Julien Active 的头像
Julien Active2 个月前

Recording flows instead of writing tests manually is a 10x shift. Mobile interaction patterns are too complex for manual E2E.

Yerassyl Ospan 的头像
Yerassyl Ospan2 个月前

hu, nice one. but we fully automated via , it takes fully lifecycle

AI Apps API 的头像
AI Apps API2 个月前

Recording flows kills the writing cost, which is the part everyone complains about. The maintenance cost is the harder half, since a recorded flow pins itself to whatever selectors existed at record time and the first redesign turns the whole library red at once. Does replay resolve elements by role or accessible name, or by the DOM path it captured?

Mark 的头像
Mark2 个月前

Can we collectively create a standard spec for writing these flows that are agnostic to the runner? I vote no proprietary files, let’s make a standard maestro, argent, agent-device, X tool’s runner all perform well at. Determinism is necessary.

Naish Bowness 的头像
Naish Bowness2 个月前

is this the same as maestro mcp or dif?

fulltimelinux 的头像
fulltimelinux2 个月前

This is cool

相关视频