Q7

Reappearing message box in AUT

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2.3
  • Fix Version/s: 1.2.x
  • Component/s: Runtime
  • Labels:
  • Test Mode:
    Manual

Description

more info will be attached soon

  1. ATT78460.log
    13/Nov/12 1:08 PM
    27 kB
    komaz
  2. Error Log.rtf
    08/Aug/12 1:42 PM
    1001 kB
    komaz
  3. File Adapter Text Box Global Variable Does Not Exist.test
    13/Nov/12 1:08 PM
    2 kB
    komaz
  4. Never Ending Popup.swf
    08/Aug/12 1:42 PM
    3.34 MB
    komaz

Activity

Hide
sergey added a comment - 08/Aug/12 6:18 PM

If attached log file contains information really related to the problem, it may be a bug in the recording component. Somehow set-dialog-result lose its parameter list and that somehow triggers the dialog "looping". The only question is "how?", it is very unlikely to lose parameters in RecordingAspect or SWTEventRecorder. Even more, I have artificaly recreated this unexpected situation in Q7 interface, section + button + SWT message dialog + no parameters to set-dialog-result sent from RecordingAspect, the test just fails, no looping.

If it is not an SWT MessageDialog, there are some signs it may not (get-window recorded), that may be some problem in event flow simulation. In any case, it is painful to debug such things without access to actual AUT. We need it.

Show
sergey added a comment - 08/Aug/12 6:18 PM If attached log file contains information really related to the problem, it may be a bug in the recording component. Somehow set-dialog-result lose its parameter list and that somehow triggers the dialog "looping". The only question is "how?", it is very unlikely to lose parameters in RecordingAspect or SWTEventRecorder. Even more, I have artificaly recreated this unexpected situation in Q7 interface, section + button + SWT message dialog + no parameters to set-dialog-result sent from RecordingAspect, the test just fails, no looping. If it is not an SWT MessageDialog, there are some signs it may not (get-window recorded), that may be some problem in event flow simulation. In any case, it is painful to debug such things without access to actual AUT. We need it.
Hide
komaz added a comment - 13/Aug/12 2:54 PM

The issue in error log is not related to the original issue – I was able to reproduce this log entry by manually typing and executing this command in control panel:
set-dialog-result MessageBox

So the problem is somewhere else

Show
komaz added a comment - 13/Aug/12 2:54 PM The issue in error log is not related to the original issue – I was able to reproduce this log entry by manually typing and executing this command in control panel: set-dialog-result MessageBox So the problem is somewhere else

People

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

Dates

  • Created:
    08/Aug/12 1:27 PM
    Updated:
    31/Jan/13 1:47 PM