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

Playback functional change required (Added feature) #20

Open
NagendraKuppala opened this issue Jun 11, 2018 · 1 comment
Open

Playback functional change required (Added feature) #20

NagendraKuppala opened this issue Jun 11, 2018 · 1 comment

Comments

@NagendraKuppala
Copy link

Hello,

Is there way to force SideeX to look for all the available/possible Target values for an element from the Target dropdown (ie: ID , Name, Link, CSS, XPath).

I have web application with webix, which means the elements ID's of the web page will dynamically changes every time I login to the application.
So, that is making my test case execution to fail because by default the recorder is selecting find element by ID target as the Selenium IDE element target values preferred order is ID, Name, Link, CSS and xPath.

Current execution scenario:

1)Recorder records a test case by clicking "Record" button.
2) Play back the test case by clicking on "Play or Play Suite or Play All" button. (Test case executes with the selected/shown target value)

Expected execution scenario:

  1. No change. (same as step-1 of current execution scenario)
  2. Play back the test case by clicking on "Play or Play Suite or Play All" button. (Execute test case by looping through all the available Element Target Values like (ID, Name, Link, CSS, Xpath) before test case fail due element not found exception).

If in case the element target 'ID' changed while test case play back, loop and look for next alternative element target selector from Target dropdown 'Name' (if still not found) --loop-> 'Link' --> etc . Before sending 'Element not found' error and Test case fail. If all the alternative element targets are really not found then throw 'Element not found' error and Test case fail.

Thanks in advance.

@NagendraKuppala
Copy link
Author

Hi Sideex team,

I'm not sure if you got an opportunity to look at this ticket.
Appreciated if you guys can consider this issue for the next release. It would be an added feature to Sideex and increase the stability of the test case execution without fail and also make the users job easier.

Thanks in advance.
@shinjielee @LinYunWen @vtim9907 @petermouse @baimao8437

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant