Q7

drag-set-data is not recorded while doing DND

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.2.16
  • Fix Version/s: 1.2.18
  • Component/s: Recording
  • Labels:
  • Test Mode:
    Manual

Description

One of our test engineers, Rich, had encountered a problem with Q7 playback with the EBI object 'Database Adapter' when performing a Drag N Drop operation.
Using existing Drag N Drop ECL code as basis that does work with our Ruleset object I was able to figure out what was missing from the initial Recording and applied the required ECL code to get the script to playback successful.

So we do have a workaround currently with v1.2.16 in order to get these test cases automated.

I just wanted to inform you of possible problem with the recording when interacting with the widgets associated with these particular objects so that hopefully future versions of Q7 won't require a workaround to be applied after the recording is completed.

So attached are widget details about the two trees in play and their associated tree items.
Also, there is a video showing an example of the initial recording, the playback failure associated with that ECL code, and finally the edits applied to get the playback to be successful.
Finally, I have included a copy of the script seen in the video.

Activity

Hide
sergey added a comment - 04/Mar/13 1:15 PM

It follows from the log that the DropAccept event is coming after DragSetData, we ignore such sequence. I see two ways to fix it:

1. The easy one – simply record all DragSetData events.
2. The true way – record only latest DragSetData, but that requires complete analyzes of generated ECL commands, since DragSetData events are interleaved with other recorded events. Also, that may be error prone because of uncertainty about what DragSetData used by final Drop.

Show
sergey added a comment - 04/Mar/13 1:15 PM It follows from the log that the DropAccept event is coming after DragSetData, we ignore such sequence. I see two ways to fix it: 1. The easy one – simply record all DragSetData events. 2. The true way – record only latest DragSetData, but that requires complete analyzes of generated ECL commands, since DragSetData events are interleaved with other recorded events. Also, that may be error prone because of uncertainty about what DragSetData used by final Drop.
Hide
komaz added a comment - 02/Apr/13 7:36 AM

Sergey, please comment which way has been chosen to fix this issue, probably we'll need this info in future

Show
komaz added a comment - 02/Apr/13 7:36 AM Sergey, please comment which way has been chosen to fix this issue, probably we'll need this info in future
Hide
sergey added a comment - 02/Apr/13 8:08 AM

I have chosen the option #2.

Show
sergey added a comment - 02/Apr/13 8:08 AM I have chosen the option #2.

People

  • Assignee:
    sergey
    Reporter:
    sergey
Vote (0)
Watch (0)

Dates

  • Created:
    26/Feb/13 4:13 PM
    Updated:
    02/Apr/13 8:08 AM
    Resolved:
    06/Mar/13 3:43 PM