sorry, i should have said that more clearly in the original post. thanks for clicking, though! if you were to use something like this in the future, what is the most important thing it needs to have or do?
Discussion
Well, I guess it depends what you're trying to make it do. Are you trying to just make it do ui testing without making people write selenium? If so then that enough is enough for me to use it.
Idk if you've ever used azure devops, but the ideal setup would be like that where I could create test cases nested within test plans nested within test suites and then either schedule or manually kick them off.
If this tool does what I think you're trying to make it do, I think you just might kill the entire QA sector of the industry lol.
"Are you trying to just make it do ui testing without making people write selenium?"
that is (part of the) dream.
but also: build the world largest testing network. anything, anywhere, anytime. nbd. :)
.... and yeah, support ai prompts and not require expert selenium knowledge. (it's gets a little tricky in distributed network wondering where the inference/translation from prompt into code happens... execution nodes could be running local llms... but hardware requirements for good local llm gets expensive)
v1 probably has most utility for simple, quick uptime health-checks using headless browsers just pinging a url, but i don't plan to stop there.
We should collaborate. I built that simple POC for testing nostr apps with selenium mostly with ai since it had been a few years since I wrote pure selenium, but that wasn't enough for open sats. Planning to reapply next quarter and spend Fridays dedicated to open source projects to work towards that goal and test automation is gonna be my main focus.
Maybe we can sync our setups for the ai portion, and then I can start to build out the test case/plan/suite tooling using the kanban/issues formatting nip and start creating those for specific nostr clients using your tool and be your Guinea pig?