Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    sequence of the recoreded commands are not in the correct order

    when we try to record, some times the order of the recorded commands in the IDE console are not in the correct order.
    Per our manager, this is a serious issue for us. For more efficient, we dont want to verify the test cases we record but directly use them in product.
    If the order of the recorded commands are not correct, we will have to spend extra time to verify each single test.
    So, please take a look into this issue.

    thanks

    #2
    Sorry to sound like a broken record, but for us to be able to look into an issue we need the information that we request every time you post: a reproducible test case.

    Comment


      #3
      ok, here is the test case.
      from the lastest build, go to feature explorere-- tree--form --- layout--titles.
      click the Username field, enter kevin
      click Email field, enter kevin
      click Password field, enter kevin
      click Password again field, enter kevin

      but the actual recorded resut is
      Code:
      selenium.click("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=username||title=Username||value=bob||index=0||Class=TextItem]/element");
      selenium.click("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=email||title=Email||value=bob@isomorphic.com||index=1||Class=TextItem]/element");
      selenium.type("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=username||title=Username||value=bobkkk||index=0||Class=TextItem]/element", "bobkkk");
      selenium.click("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=password||title=Password||index=2||Class=PasswordItem]/element");
      selenium.type("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=email||title=Email||value=bob@isomorphic.comwww||index=1||Class=TextItem]/element", "bob@isomorphic.comwww");
      selenium.click("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=password2||title=Password%20again||index=3||Class=PasswordItem]/element");
      selenium.type("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=password||title=Password||value=eee||index=2||Class=PasswordItem]/element", "eee");
      selenium.type("scLocator=//DynamicForm[ID=\"exampleForm\"]/item[name=password2||title=Password%20again||value=qqq||index=3||Class=PasswordItem]/element", "qqq");
      But the correct order should be
      click
      enter
      click
      enter
      click
      enter
      click
      enter

      Comment


        #4
        any update?

        Comment


          #5
          The issue here is that "click" commands should not be recorded when text item based fields are clicked. We're looking into a way of having Selenium IDE not record them when SmartClient / Smart GWT based forms items are clicked. This is because Selenium IDE only records the "type" command on blur.

          To resolve this you can manually remove these click commands from your testcase.

          Comment


            #6
            thanks for the reply, but the thing is we dont want to manually modify the testcase commands, we want to use the testcases directly without touching it.
            Do it manually will consume us lots of more time, which is not efficient for our testing.

            thanks

            Comment


              #7
              any update?

              Comment


                #8
                Manual edits may be required in some circumstances (and your team was told this explicitly, up front). We will be working to reduce the number of cases over time and this particular case is being worked on now - no ETA available yet.

                Comment


                  #9
                  This should be fixed in tomorrows build.

                  Comment


                    #10
                    tried with Jun 9th build, still can see the problem

                    Comment


                      #11
                      OK, this is getting rather silly. Just to completely close this out, here is a video of the feature working properly.

                      Comment

                      Working...
                      X