Community
Participate
Working Groups
Build Identifier: It looks like the mouse click is done on the right of the tree, so if you have a tree with long element like below, the short one will never be selected. - Folder A - Element A - Element B - Element CCCCCCCCCCCCCCCC By exemple, Element A will not be selected because the mouse click is done at the right ... Reproducible: Always
After checking, I see that I will always click on the end of the longest parent : So I you have - Folder A - Folder BBBBBBBBBBBBBBB - Entry 1 - Entry 2 - Entry 3 - E - ALPHABETIC Folder be is not selected but all the child of Folder BBBBBBBBB will be selected
Please create a regression test
We are creating an example tree for our test system to see if we can reproduce the problem.
Created attachment 201239 [details] Bug screenshot
Created attachment 201240 [details] Expected result
I attached 2 screenshot to better see the bug. The reason is simple : <Skills> and <Database> is not selected when the test suite create the folder/entry ... So the last item is always the parent of the created element ! # SELECT ROOT ub_tre_selectNode_byTextpath (Skills) ub_app_wait (firt root is selected, there are no children) # CREATE AN ENTRY UNDER SELECTED ub_grc_clickLeft_single ub_cti_replaceText ub_app_pressAnyKey_ENTER # CREATE A FOLDER UNDER ROOT < SELECT ROOT > < CREATE AN ENTRY UNDER SELECTED > The children name are longer that the parent, so the parent is not selected (in reallity the mouse click is done outside the element ...
Thank you for the extra information. Could you also specify what type of an error is displayed by Jubula (Action Error, Configuration Error - and any extra details shown about the problem), and attach the AUT Agent log?
There are no errors reported ... Test suite runs exactly without problem but of course if I want to select an element his position is wrong ...
Hello Michel, We have not been able to reproduce this problem on our example application. We are able to select e.g. Long node name - Short node name As well as: Short node name - Long node name without any problems. It seems strange that the test itself runs without error. Usually if we cannot select something, an error will occur. Please check the following: - That you have not used a click count of "0" for the parameter "NUMBER_OF_CLICKS" - That you are using the left mouse button ("1") for the MOUSE_BUTTON parameter If both of these parameters are correct, then it would be worth checking in your application whether the node length is as long as the text shown, or if it is perhaps longer than the node text. If it is longer, then you could try manually selecting to the right of the node in your tree to see if a selection occurs. Failing all else, please describe the exact path you want to select through one of the trees in the attached screenshots, as this information is somewhat unclear from the previous posts.
I don't know if this can help you, but I see that I don't have the problem on MAC. I will see with the developpers to know if this is specific to Windows 7 (I have to click in the label to select it on Windows but I can click outside the text label on MAC. I will post a comment when I have more information. Michel
Ok, thank you. I've also been assuming that you're working with an RCP application. Is this the case?
I can confirm that on Windows I have to click exactly on the text, but on Mac the item is selected also if I click outside the text (like Jubula does) ... Is this something that developpers have to correct in the development (I'm not a Java developper, my mission is to automate GUI test). Yes, I'm testing an RCP application. Thanks,
I'm not sure whether this is something that your developers will be able to change, as it is likely that the behaviour results from the SWT implementation. We used SWT version 3.4 to perform our test yesterday on a Windows 2008 machine and were able to select nodes without a problem. Perhaps you can use this information to see if it is a problem specific to your SWT version.
I just checked within Jubula itself. If I want to select a test case in the test case browser, I need to click exactly within the label (unboud_modules_concrete_[5.0] for example). If I click outside the label, It doesn't work. On mac, I don't have this limitation and I can click outside the label to select the item. This is what Jubula does during a test. Do you better understand my problem ?
I'm going to see if I can reproduce this on a Windows 7 machine this afternoon. In the meantime, could you try to find out what SWT version your application uses?
I've now tried reproducing this on a Windows 7 32 bit machine, both on our current build and on the released version. The test runs fine; all required nodes are selected. Any other information you can give us at this point is welcome - if you can attach the project as a zipped xml file (use the export function in the Test -> Export menu), a video of the test running, information on your SWT version / other environmental factors etc, then I can have a look to see if anything is wrong. Otherwise I'll have to close the issue as works for me.
Thank you Alex. I will send you those information later this week by email because I don't have the computer I run the test right now. I will ask the question about the SWT version because I don't know which version the developers use. If you have your computer with Win 7 32 bits, maybe you can take a look in the Jubula IDE. Try to select a node in the "Test Case Browser". Do you have to click exactly on the label (Actions (basic) for example) to select this node or can you click outside the label ? On mac you can click outside to select the node but on Windows, you have to click exactly on the text label. Do you see it ? I think when you made a test with Jubula, it will click outside the label... Right or not ?
Because Jubula also uses SWT, it's not a surprise that you see the same behaviour when working with it. The real question is where the AUT Agent component clicks during test execution. When I've run the test on our test system here, the click is correctly interpreted and the node is selected. For whatever reason on your system / in your SWT version / in your AUT, the click is being performed elsewhere. We'll only be able to figure out what's going on with the additional information you'll send. While I think on - if you can also send the code snippet(s) that are responsible for your tree, that may also help. Once we have the SWT version, the project and the snippet, then we should be able to build an example to reproduce your problem.
This issue has not been edited in a while so I am going to close it with "works for me" - if you have any information to be able to reproduce it, as mentioned in the previous comments, then please reopen the bug with the further details.
Created attachment 202785 [details] Jubula XML with the test case for this bug
Created attachment 202786 [details] Video recording of this bug on our app
It looks like we use SWT version 3.7
Thank you for the additional information. I'll reopen the ticket and have a look at what you've attached. The Project xml is unfortunately unopenable. Can you add it to a zip file and reattach it? Could you also elaborate on what error occurs on the failed node shown in the video by adding: a screenshot of the failed test step, selected in the test result view, showing the full properties view for that test step and the relevant part of the image view (the tree) for the error.
Created attachment 202787 [details] Jubula XML with the test case for this bug
I return a failed test step because it's not possible to select the node using the path because the path is incorrect. The problem is in the directory structure due to the fact that the parent is not selected during the creation. For example, I want to select "Skills/Database/H2" (expected result) but as you can see in the bug screenshot, the hierarchy is incorrect ... This error is just the consequence of the bug, not a bug...
Ah, ok. Thank you. What I can see from the video and the test is this: The mouse is being moved to the correct node (in the case in point, the root node), and the "select" is being marked as successful. However, no selection is taking place. Could you try out the following things for me: - Instead of using the "tree table" component for the select actions, what happens if you use the normal "tree" component (I saw that this is commented out in the test) - When selecting the root, try using preascend "0" instead of "1" - Does the problem also occur when the view for the tree does not have to scroll (i.e. it is big enough for the tree)?
That's right, the mouse is being moved to the correct node (in the case in point, the root node), and the "select" is being marked as successful. However, no selection is taking place. Please also note that in Mac it works fine. The problem is the position of the mouse because to select the note you have to click on the label. I already made those three test before reporting the bug. That's why there were commented tests steps.
So if I understand correctly, you already tried using: a. the select node action on the tree component instead of the tree table b. pre ascend 0 instead of 1 in the root node module c. the view with the tree in in a larger state so that no scrolling was necessary And none of these things had any effect on the incorrect selection of the node? If you could clarify these three points, that would be great.
Exactly, none of these things had any effect on the incorrect selection of the node. The problem is the position of the mouse when the click is done as you can see in the video. Maybe a solution would be to implement a test case to select a node and specify the position of the mouse before the click (select) is done. What do you think ?
Hello Michel, I had an idea for a workaround that may help your test at the moment: When a node is added in your tree, it is automatically selected, if I observed correctly. If this is the case, then you could see if you could write a module to select the root node using the arrow keys (left arrow key will select the parent of the currently selected node etc.) It's a workaround, but maybe it will help you to get past this point in your tests, as the issue certainly won't be fixed for SR1. Let us know how you get on with this.
Sorry, too late for SR1 by now, raised the priority for SR2
Hello Michel, Could you give me an update on the status of this issue? Does it still occur with the latest release of Jubula? Did the workaround I suggested help you at all? Another point that came up in discussion was whether or not the error is reproducible manually. We had a case a couple of weeks ago where Jubula seemed to be adding the node to the wrong parent, but it turned out to be a problem in the model of the AUT. Just to be very sure it's not that, can you perform the test steps manually and check that the error does not occur? Thanks, Alex
Hi Michael, Do you have any further information on this with reference to my previous post? Otherwise I'm afraid I'll have to close the bug. Thanks, Alex
