Q7

Widget is disposed during recording

Details

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

Description

Quote from mail:

I have a problem that happens when recording a test case for my AUT:

My AUT produces a GEF graph.

When I am not recording my actions, and when I click on a node on the graph, I get in the Properties view information related to that view.

But when I am recording my actions, and I click on the node, I get nothing in the Properties view. And when I click inside it (i.e.: inside the properties view), I get the following error:

I think that error is not related to my AUT, since it happens only when I am in recording mode.

Looks like there's no enough information, probably need to request logs and schedule a meeting

Activity

Hide
komaz added a comment - 18/Jan/13 5:56 PM

Update from customer:

I noticed that there is a difference in the AUT behavior while in recording mode and while in normal operation.

This difference in behavior can make some of the AUT’s functionalities unreachable or can make the effect of some of my actions temporary.

For example,

I may be editing a graph in an editor, but I notice that the asterisk “*” that should appear when I am doing so, doesn’t appear while I am doing my changes.

And even if I save that editor using “Ctrl+S”, and then close that editor and re-open it again, I don’t find my changes there !

This may cause some functionalities unreachable.

Another problem is that some “locking” behavior happens on the graph nodes automatically without my request, while this locking doesn’t happen when I am not in recording mode.

I can elaborate on that more using an example in the online meeting, but try to consider this in your testing environment for Q7.

Show
komaz added a comment - 18/Jan/13 5:56 PM Update from customer:
I noticed that there is a difference in the AUT behavior while in recording mode and while in normal operation. This difference in behavior can make some of the AUT’s functionalities unreachable or can make the effect of some of my actions temporary. For example, I may be editing a graph in an editor, but I notice that the asterisk “*” that should appear when I am doing so, doesn’t appear while I am doing my changes. And even if I save that editor using “Ctrl+S”, and then close that editor and re-open it again, I don’t find my changes there ! This may cause some functionalities unreachable. Another problem is that some “locking” behavior happens on the graph nodes automatically without my request, while this locking doesn’t happen when I am not in recording mode. I can elaborate on that more using an example in the online meeting, but try to consider this in your testing environment for Q7.

People

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

Dates

  • Created:
    14/Jan/13 8:09 PM
    Updated:
    07/Mar/13 11:51 AM
    Resolved:
    07/Mar/13 11:51 AM

Time Tracking

Estimated:
4h
Original Estimate - 4 hours
Remaining:
4h
Remaining Estimate - 4 hours
Logged:
Not Specified
Time Spent - Not Specified