Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.side-format specification #77

Closed
j4x0 opened this issue Jan 6, 2018 · 7 comments
Closed

.side-format specification #77

j4x0 opened this issue Jan 6, 2018 · 7 comments

Comments

@j4x0
Copy link

j4x0 commented Jan 6, 2018

Is there any (final) specification of the .side-format available yet? I would like to write a small interpreter for the .side files.

@corevo
Copy link
Member

corevo commented Jan 8, 2018

I'm planning on adding a few backwards compatible changes (a few new keys at project level).
Then I'll be naming it as version 1 of the .side format.

@beatngu13
Copy link

Any news regarding the .side format specification? I'm working on a test generator and I would like to create .side-based test suites/cases, so that I can use the Selenium IDE for playback, code export, etc.

@bcmoney
Copy link

bcmoney commented Jan 31, 2019

Please don't make that switch to YAML if possible or still considering hah... I've developed a custom Java parser and it would be a pain to have to re-implement!!!

PM me on Selenium Slack @ bcop if anyone's interested in code for that, or I might just throw a blog article together... pretty basic stuff with Jackson... by simply adding comments with specific names we're able to ensure more durable selectors using Annotation-based selector lookups from SeleniumIDE recordings rather than putting any selectors directly in Page Objects.

@tourdedave
Copy link
Contributor

A blog post would be great! We could cross-post it on the new SIDE blog, just send us a canonical link.

@corevo
Copy link
Member

corevo commented Jan 31, 2019

@bcmoney we won't be converting side to yml, what I was thinking about is if WebExtensions at some point would give filesystem access and CWD, we could break side to multiple files again, and have a "real" save mechanism, at which point saving multiple files makes more sense in yml.
Bottom line, as long as it's a single file it will stay json, if we find a way to break it into multiple files that would be backwards incompatible anyway, so in that case we will strongly consider moving to yml, or any markup language that is more approachable than json.

@bcmoney
Copy link

bcmoney commented Apr 27, 2019

@corevo & @tourdedave sorry for the delay, couldn't find much time between my home demands with kids, teaching engagement I've got going on now, and my regular 9-5 gig... but here's the example Durable Selectors annotation and SIDE parser in Java:
http://bcmoney-mobiletv.com/blog/2019/04/27/selenium-ide-side-parser-for-durable-selectors/

I hope it could be of some use to folks, especially as I saw that Java export capability is possibly going into the next SeleniumIDE release? Cheers and thanks again for everything you do on this project!

@bcmoney bcmoney mentioned this issue Apr 29, 2019
5 tasks
@beatngu13
Copy link

Is there a reason why this has been closed? If there is no specification yet, is there anything we as an OSS community can do to help?

@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants