Live data from Hacker News

Show HN: Kasaya – A scripting language and runtime for browser automation

github.com

11–20 of 109 posts

Re: Show HN: Kasaya – A scripting language and runtime for browser automation

#11
Would be great if this "transpiled" into a more robust and popularly supported formalism so that the functionality could be refined over time.

I could see implementing this script as being a requirement for a new feature delivered by engineering, and then having test engineering use that functionality as a foundation for more thorough qualification.

I worry that this approach by itself will fall into the same issues that Cucumber does, which is the amount of manual definition you would need to implement through what they're referring to as "macros". Over time those become as brittle as the code you intend to test.

Re: Show HN: Kasaya – A scripting language and runtime for browser automation

#13

Would be great if this "transpiled" into a more robust and popularly supported formalism so that the functionality could be refined over time. I could see implementing this script as being a requirement for a new feature delivered by engineering, and then having test engineering use that functionality as a foundation for more thorough qualification. I worry that this approach by itself will fall into the same issues…

Why do they become brittle? Because they have to be fixed every time code changes?

Re: Show HN: Kasaya – A scripting language and runtime for browser automation

#14
This looks great.

I also want to shamelessly plug something similar I am working on, Taiko, it uses javascript and comes with a REPL that generates scripts like.

  await openBrowser();
  await goto("http://todomvc.com/examples/react/#/");
  await write("automate with taiko");
  await press("Enter");
  await click(checkBox(near("automate with taiko")));
The reason we use a javascript is familiarity, IDE support and use of existing node js libraries for testing.

For anyone who's interested

https://github.com/getgauge/taiko

Re: Show HN: Kasaya – A scripting language and runtime for browser automation

#15

I am confused by the use of "WYSIWYG". It seems to be more a control console/REPL with Natural Language syntax. Edit: A killer feature would be autocomplete for things found on the page.

I was also confused by the term “English like”.

I think that better terms would be “simple” and “readable”.

Re: Show HN: Kasaya – A scripting language and runtime for browser automation

#17
post #9

Interesting but I'm not sure about the syntax. If I'm writing code, why do I want to write code in a language that is overly verbose and not that precise? Just make it code. And if it is not meant for programmers, then make it clickable+drag-and-drop. Having a compromise in this case, makes it not a solution for anyone.

I’m getting AppleScript flashbacks…

Re: Show HN: Kasaya – A scripting language and runtime for browser automation

#20

I am confused by the use of "WYSIWYG". It seems to be more a control console/REPL with Natural Language syntax. Edit: A killer feature would be autocomplete for things found on the page.

I was also confused by the term “English like”. I think that better terms would be “simple” and “readable”.

Will take this into consideration when going out of beta...
Post reply on HN