Closed corevo closed 4 years ago
Looking forward to the python version. Thanks for developing this tool
Looking forward to the python version. Thanks for developing this tool
likewise! Python or Javascript would be greatly appreciated.
+1, can't wait for python. Thanks for all the hard work!
I'm just about to embark on a large suite of tests - how long do you think the export is going to be? As I dont want to commit to all these and have to move off to Katalon or some such? great work as always!!
@jonesp100 It depends on the language (since we're going in the order listed above, unless others are able to contribute as well), and even then it's hard to know since we're an open source project and timetables & competing priorities can be unpredictable for both contributors and maintainers -- so we can't publicly commit to a timeline.
If your objective is to run your tests cross-browser, in parallel, and/or on CI, then do be sure to check out the Selenium IDE command-line runner while you wait. Details available here.
@tourdedave thanks for the response - appreciate you cant commit but do you have a rough timeline - first language - 1 month, 2 months....? Thanks!
Hey @corevo, just out of curiosity is it also planned to have a code import sort of thing along the export available. What I mean with that is once you export a code, and do minor modifications according to the style its exported, are you able to re-import it as a side project in Selenium IDE?
Moreover, with regards to the export behavior, do you plan to have a customizable export template per language or is it going to be a fixed set of definitions?
What do you recommend, how would be the best to move forward the issue of exporting into PHP, please?
@jonesp100 ¯_(ツ)_/¯
@zewa666 No plans for code import at the moment. The initial MVP for code export will just be as-is -- not customizable.
@BaluErtl We're building code export so others can easily contribute other languages. PHP is a tricky one, though, since it's not an officially support language binding. Because of that it's unlikely we'd incorporate it into the mix. But we've discussed the option of making code export for additional languages available through plugins, which could be a nice option to make PHP available if someone wanted to contribute it.
@tourdedave having the code-export configurable via plugins would on the other hand also allow to customize the style of how things get exported. So besides Java
then there could be an additional plugin to export to Java using 8 spaces
, don't crucify me for that heretical example ;).
Thanx a lot @corevo ! Looking forward for good news about junit export!
Looking forward to the python version. Thanks for developing this tool
Me to!
@tourdedave the .side files aren't affected by this, are they? So we can still edit our tests there.
and i am also really looking forward to this! :)
Yes, if you keep the .side
files you can load them in to the IDE change them and re-export them.
Great , waiting for C# exporting.
Thank you all.
waiting for java exporting , thank you !
waiting for python export :)
waiting for python export :) too.
等待python导出
Export to Java is great!
Why not allow users to specify their own export actions? Instead of hardcoding this in js files rather allow a config which can be modified to cater for different permutations of various frameworks.
so for a click i can opt to use a specific bit of code, specified in a text file for the click, instead of all these repetitive lines being exported. Just an idea... would then solve all "languages" issues as this would be abstracted and we can key/value pair the stuff.
fyi- Just for confirmation, is export to Java Working?
@sah-anshu Yes, export is available for Java JUnit.
@stebli Code export is doing a lot more than just exporting individual commands. Allowing user customizations through a separate file isn't enough to solve for all languages -- especially if it puts the burden onto the user. But it's an interesting idea - thanks!
@tourdedave @stebli I think this would be best solved by good guidance on how to create plugins to export code in different languages/test frameworks.
@tourdedave Is this being added to the Browser plugin/extension in the next release as well, or only via passing those parameters to the CLI tool?
Also, in case you didn't see my post on ide-77, since I saw how close you were getting with this, I've finally gotten around to writing a blog post about the "Durable Selector" approach our team has been using for several months now: http://bcmoney-mobiletv.com/blog/2019/04/27/selenium-ide-side-parser-for-durable-selectors/
Simply record ".side" format and import into our Java Test Suite, I think its a nice setup. Included a simple Maven project with the essentials, feel free to use it however you see fit!
@tourdedave @stebli I think this would be best solved by good guidance on how to create plugins to export code in different languages/test frameworks.
is this an option right now? Will it be limited to JS?
The plan is to allow 3rd party plugins to export code, we will be exporting to the official bindings, this way you could write a plugin to export to webdriver.io or such.
The plan is to allow 3rd party plugins to export code, we will be exporting to the official bindings, this way you could write a plugin to export to webdriver.io or such.
awesome. await that functionality....veery useful
Do anyone know when exporting to java will be fixed on the new selenium IDE
Eagerly Waiting for Python Code Export.
@upenk910 What do you mean? Java export is available in the latest version (3.6.0).
i don't see the option can you tell me where is option to export in java the test case
On Wed, May 1, 2019, 7:10 AM Dave Haeffner notifications@github.com wrote:
@upenk910 https://github.com/upenk910 What do you mean? Java export is available in the latest version (3.6.0).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SeleniumHQ/selenium-ide/issues/592#issuecomment-488267533, or mute the thread https://github.com/notifications/unsubscribe-auth/AL6UVVIQHZYSPFUSNQWNF2LPTGCDDANCNFSM4G23OS3A .
just right click on your test and there will be an export option. I have just exported one example test to java so I can confirm it is working
Thanks, since to GUI of the selenium IDE has changed from the previous versions, i couldn't find it.
On Wed, May 1, 2019, 8:33 AM rori4 notifications@github.com wrote:
just right click on your test and there will be an export option. I have just exported one example test to java so I can confirm it is working [image: image] https://user-images.githubusercontent.com/22402693/57019320-cae7e000-6c2e-11e9-9235-23c969c15cd7.png
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SeleniumHQ/selenium-ide/issues/592#issuecomment-488283117, or mute the thread https://github.com/notifications/unsubscribe-auth/AL6UVVKQKF6WFTBRVII4XWTPTGL2FANCNFSM4G23OS3A .
The docs have been updated to cover code export and include instructions for contribution a new language/framework.
https://www.seleniumhq.org/selenium-ide/docs/en/introduction/code-export/
The docs have been updated to cover code export and include instructions for contribution a new language/framework.
https://www.seleniumhq.org/selenium-ide/docs/en/introduction/code-export/
Hi tourdedave,
I followed these instructions but do not see the new item in the export list. Is this a complete guide? I see issues (i.e. missing aliases under code-export\node_modules\xxx) that arent mentioned in the guide if i just look at the folder structures.
To have it show up in the list you need to be sure to complete step 5. If you're getting build warnings then try cd
ing into your package and running yarn build
.
step 5
have done that yes...
yarn build yields
yarn build yarn run v1.16.0 $ babel -d dist src --ignore=test src/command.js -> dist/command.js src/hook.js -> dist/hook.js src/index.js -> dist/index.js src/location.js -> dist/location.js src/selection.js -> dist/selection.js ✨ Done in 0.92s.
when running yarn build:ext:prod from root i do see these warnings, could they be the issue?
WARNING in ./neo/stores/seed.js 17:496-509 "export 'CommandsArray' was not found in '../models/Command' @ ./neo/stores/seed.js @ ./neo/containers/Panel/index.jsx @ ./neo/containers/Root/index.jsx @ multi react-hot-loader/patch ./neo/containers/Root
WARNING in ./neo/stores/seed.js 17:535-548 "export 'CommandsArray' was not found in '../models/Command' @ ./neo/stores/seed.js @ ./neo/containers/Panel/index.jsx @ ./neo/containers/Root/index.jsx @ multi react-hot-loader/patch ./neo/containers/Root
No, those warnings are OK. Can you publish your fork and send a link?
Unfortunately not(did not fork) , company is locked down and we cant remote/upstream to github.
Can you create a gist with the contents of your selenium-ide/packages/code-export/src/index.js
? The code export UI is built using the availableLanguages
object in that file. That's the first place I'd look.
@stebli That looks correct.
Make sure that 1) you've added your package as a dependency in code-export
(e.g., here) and 2) you're able to run yarn
from the root of the project before building the extension (e.g., yarn build:ext:prod
or yarn watch
).
I've updated step 1 in the docs to include these bits.
Check on all fronts. Still no new export item. yarn build:ext:prod completes successfully with only the warnings listed above. I tried deleting the build folder and rebuilding/re-adding to chrome, no difference.
@stebli Can you open a new issue? It will be better to track the progress there.
@tourdedave https://github.com/SeleniumHQ/selenium-ide/issues/689 created.
\o/ Thanks!
I just submitted a PR for Python support (e.g., #719).
It will be available in the next release.
FYI - code export for Python was released yesterday.
@tourdedave, the python export is awesome, thanks to you and everyone else involved!
We've just started working on exporting to languages, we will continually update this thread with new information as it becomes available.
Languages:
We are aware that this feature is very important to the community, but we'd kindly ask to keep all conversation here, until a language is released and then any bug found should raise a ticket.
We would like to avoid splitting the same conversation into multiple threads.