search

golemhq / golem

A complete test automation tool
http://golem-framework.readthedocs.io/
MIT License
489 stars 77 forks source link

Converting Katalon/Selenium IDE recordings into Golem test scripts #216

Open Sunil-Rathore opened 3 years ago

Sunil-Rathore commented 3 years ago

This Feature should be implement like below.

  1. user should have an option on test code script page for convert Katalon/Selenium IDE recording python script into Golem test script.

need to add one button on test code script page where user can upload katon/selenium IDE python script and after upload it should convert into golem test script and will display on test code script pge.

through command it should be like golem convert katalonscript.py

Sunil-Rathore commented 3 years ago

@luciano-renzi what you thinking to implement this one I will go ahead to implement this feature.

luciano-renzi commented 3 years ago

I would give priority to importing from Selenium IDE rather than the other one. I think that would be a far more helpful feature. But it's up to you.

I see the Selenium IDE can export a single test as a pytest file or an entire project as a .side file (which looks like json). Which of these were you trying to use?

Sunil-Rathore commented 3 years ago

it will better we can use export .side file which look like json and can convert into golem scripts.

luciano-renzi commented 3 years ago

In that case it should be better if the importer creates each test in the side file if a test with the same name does not yet exist in Golem otherwise it should ignore it

Sunil-Rathore commented 3 years ago

@luciano-renzi yes this feature almost completed but what u think about if project name already exists. actually side will import with first new project name and after test and suite inside created project.

there is below three different way to handle this one. if project already exist then it will not import again. if project already exist and user want to add newly test and suite in the existing project. if project already exist and user want to replace the already exist test or suite in existing project.

let me know your comments which one is good as of now.

luciano-renzi commented 3 years ago

if project does not exist, a new project should be created. for each test if a test with same name exist, show warning. it could have a --overwrite flag to replace existing test with new one.