UnitTester appears to cause 4D to crash

[KAS]

Is anyone else seeing this. 4D crashes when dragging from the
explorer into a method.

Here are the steps that will cause the issue.

1.  It only happens when UnitTester GUI is running.  
2.  It also only happens if you click on a method that is not
highlighted in Explorer and try to drag it without releasing the mouse
button.
3.  Highlight a method first and release mouse button and then
reselect and drag does work.
4. I can't reproduce this problem unless UnitTester GUI is running.

I have tried this on two different DB with the same results.

I created a new db and installed just the Unittester component and
created 2 methods.  I could recreate the problem.  I don't think it
happens 100% of the time put pretty close.

Any thoughts?

Ken

[Mark Schaake]

Hi Ken,

I have not been able to reproduce this, though I have yet to test on
v11.7. On both v11.6 and v12 I was not able to reproduce.

I strongly suspect that this is really a 4D bug and not a UnitTester
bug. The reason being is that UnitTester does not interact to the
Design Environment in any way other than through Rob Laveaux's API
Pack plugin (to create methods and open the method editor).

Even if I can reproduce the bug, there is no way to debug it as your
issue occurs within the Design Environment process (which is not
traceable by us).

If you want to try to investigate further, you may create a component
that can open a window. Then, launch the window in your host DB (that
does not contain UnitTester), and see if you experience the same
behavior (that 4D crashes when you are dragging your method).

Best,

Mark

[Kenneth Spence]

I would agree that this may be a 4D bug. You can't reproduce in v12 and v11.6 so I was hoping someone else could reproduce in v11.7 and then I would be more inclined to file a bug with 4D.

I have had the crash as well when dragging in Test Application mode. I have not really tested this very much.

I will try and create the component as you suggest and see what happens.

Thanks,
Ken

> --
> UnitTester: unit testing and test-driven development for 4D.
> www.unittester4d.com
>
> You received this message because you are subscribed to the Google
> Groups "UnitTester" group.
> To post to this group, send email to unitt...@googlegroups.com
> To unsubscribe from this group, send email to
> unittester+...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/unittester?hl=en

[Kenneth Spence]

Mark,
I created a TEST component that just opened a window with Dialog and the form only had a cancel button in it.

I created a TEST2 database that had two tables in it and one method. I put the TEST component in the TEST2 DB and opened the window. No problems with dragging methods from explorer.

I also put this component in with the DB I have been having troubles with UnitTester. I removed Unittester. I ran the method to open the TEST component window and was able to drag with no problems.

Got any other ideas. So far only does it with UnitTester GUI running.

I am using Foundation but not sure why there would be an issue there.

Ken
On Aug 11, 2010, at 5:55 PM, Mark Schaake wrote:

[KAS]

I am finding that UnitTester is affecting my DB in the test
application mode as well. I have some lists boxes on one page and if
I drag even within the same list box 4D will crash if UnitTester is
running. It will show a green circle with a + in it and stays that
way until it crashes. When UnitTester is not running there are no
problems and the green circle with the + only shows for a second and
then disappears and all works as expected.

There is definitely an issue with UnitTester. I just can't tell if it
is a 4D issue related to something UnitTester is doing or is just
UnitTester?

Would someone else please see if this happens for you with 11.7.

Thanks
Ken

[KAS]

I think this is an issue with 11.7 only. I converted my DB that I was
having trouble with to v12 and I so far have not been able to
reproduce the problem.

I will submit a but to 4D and see what happens. Hopefully they can
use the demo version of UnitTester to reproduce.

Ken