| Unable to Execute SimpleAdder Project [message #897581] |
Tue, 24 July 2012 15:09  |
 Peter Hancox
Messages: 14
Registered: July 2009 |
Junior Member |
|
|
Just installed and started working with Jubula feature within eclipse. I've been working through the "SimpleAdder" project in the CheatSheet. Everything has gone fine up to the point of trying to execute the test suite.
I had to install the stand alone version in order to get the test application, however, all the work following the cheat sheet was done in my standard eclipse installation after installing the Jubula feature from Junos update site.
I am using the embedded AUT agent and the AUT starts fine. Could perform object mapping without any issues.
When I come to the final step of launching the test suite, nothing happens. I am in the "Functional Test Specification" perspective and eclipse doesn't offer to change to the "Functional Test Execution" perspective.
The probable cause is that the test suite has the test case flagged with an error of "Test Data for this node is incomplete". So I'm guessing it isn't even trying to start the test because of this?
In the Test Case Browser, all of the lowest level references to the unbound_modules_concrete_[6.0] library are missing the parameter values. In the test case editor, these values were specified (and still exist) in the parent node. The value cannot be set in the lowest level node. This would seem to make sense as the lowest level node would appear to be a "template" that is then customised by its parent.
So this seems "reasonable" except, because the parameter IS set for the parent, the Test Case Browser shouldn't be showing an error. Note that no error is shown in the Test Case Editor view.
Since this is my first experience with Jubula, I'm not sure what is normal and what isn't? Can anyone comment on whether this error condition is likely to be causing my problem and what else I can do to diagnose the issue?
Thanks for any help.
BTW Environment is Eclipse Junos 64-bit on Windows 7
[Updated on: Tue, 24 July 2012 15:18] Report message to a moderator |
|
|
|
|
| Re: Unable to Execute SimpleAdder Project [message #897923 is a reply to message #897704] |
Wed, 25 July 2012 12:52  |
Peter Hancox
Messages: 14
Registered: July 2009 |
Junior Member |
|
|
Hi Alex, thanks for your response.
I've fired up my standard Eclipse environment and attached to the same Jubula database that worked successfully with the standalone version and it continues to work OK. Made a simple edit to the test case and still OK.
Don't think I had any of the possible issues you suggested on the original plugin failure. I did however, have a few goes at importing the sample project. This time around the library test steps look a bit different I think. Whereas in the failed attempt, the parameter value for the library step was empty and unchangeable, it now has a value (e.g., "=TEXT") and unchangeable.
Perhaps in my initial stumbling around to import the example project I got the project database corrupted in some way.
Anyway, don't seem to have any problems now so I'm about to change the database to PostgreSQL and continue my evaluation.
Did notice, however, that after running the first test suite, the status bar reports "No connection to AUT". This occurs for both standalone and plugin versions but doesn't appear to cause any problems. Is this a bug or expected behaviour?
REGARDS
Peter
|
|
|
|
|
|
|
|
| Re: Unable to Execute SimpleAdder Project [message #898654 is a reply to message #898651] |
Fri, 27 July 2012 05:50 |
Peter Hancox
Messages: 14
Registered: July 2009 |
Junior Member |
|
|
Not sure where the locale is folmerly set but "Format:" under "Region and Language" is set to "English (Australian)".
I doubt the difference between "English (United States)" and "English (Australian)" is going to make much difference. So unless it's easy to configure the unbound modules I'll just change the project language in Jubula project.
Found this issue discussed briefly in the forum http://www.eclipse.org/forums/index.php/mv/msg/240598/726396/#msg_726396 back in September 2011.
Given the error messages aren't particularly helpful in identifying the problem, and I expect it could well impact a number of first time users, is it worth while getting this into the FAQ? And/Or the cheat sheet.
I've created another thread in relation to screenshot image storage in PostgreSQL.
Many thanks for your help.
[Updated on: Fri, 27 July 2012 05:53] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03920 seconds
] 
Search
Help
Register
Login
Home
