| ▲ | Show HN: Deterministic UI testing that checks backend logs, not just the UI(get-verirun.duely.in) |
| 2 points by shad0w008 7 hours ago | 2 comments |
| |
|
| ▲ | sightspinner 5 hours ago | parent [-] |
| seems interesting. do I understand correctly that after you record once you get a script that you can use it as a test (whether that be for you or you agent)? If you make a change (e.g a button name update) do you need to rerecord it entirely? |
| |
| ▲ | shad0w008 4 hours ago | parent [-] | | Thank you. Once you record something, you get a json file stored in your repo under .verirun/workflows/ which can be replayed again and again either by you or the agent. If you change the name of the button, you need to rerecord. Because the name of the button and where it exists on the codebase is how verirun identifies it. If you however change anything else related to the button, you do not need to re record. There is also a feature where the tool generates an interaction map of the ui elements. The agent can use that map to write its own workflows and place them into .verirun/workflows/ which can be run just like any other recording. Hope that answered your question :) |
|
