go-rod / wayang Goto Github PK

Basically, wherever an action is requested, we can substitute it with an action, as well as vise versa. This will make the language a lot more advanced and give access to unique features

CSS Selectors can be a lot simpler to write. CSS Selectors are more convinient in general

An important selector that can help improve testing. Still need to figure out the semantics on how we should implement this.

This can be nice when doing text comparisons.

The store can become a lot more versatile and make it possible to use for more complex operations if we can also start to query it.

Support Shadow DOM. Like iFrames, this is an important part of many websites. Supporting them is important.

Still need to work on specifics. How can we refer to files to upload? Do we query the local directory? Implementation suggetions are welcome.

Trace mode is a great feature of https://github.com/go-rod/rod. We should really support it.

The project is in need of adding mroe tests. The current smoke tests are relatively basic and not feature complete

Can be important for testing more complicated forms. Still working on implementation. Perhaps have a list of items to tick?

We are having scripts recorded using Checkly Recorder. Is it possible to use these steps and convert them into wayang - from which we can run it using go-rod?

If yes, any pointers on this. If not, should we manually rewrite all these steps/scripts into go code separately..

Btw, the idea behind wayang is wonderful - to have a language neutral way to capture the steps, which we can later use it with different tools..

Makes it so that the CLI method for running programs becomes a bit simpler. Possible items could be:

• headless mode
• trace mode
• timeout
• slowmotion

This is an important feature that can be nice for when elements don't exist, and we want to escape from just panicking and quitting altogether.

iFrames are very important for some websites, and having the ability to test them is imperative.

Complete the documentation for how the language works.

Add information for how to contribute to documentation, as well as maintaining it.