Unable to map objects [message #1702600] |
Thu, 23 July 2015 13:21 |
Thomas Mortimer Messages: 18 Registered: July 2015 |
Junior Member |
|
|
Hi all,
I've attempted to find an issue to this problem, but my google-fu is failing me. I've followed the cheat sheet and managed to get Jubula to map the components correctly in the adder, the green boxes came up and the system worked.
So, I've moved onto my own project and followed the steps as before, there are minor differences as I've got a server to start first and then a client. I've created a separate AUT for the server and one for the client. I start them both up, click on the down arrow next to the object mapper mode and select my client. I've highlighted my text box, buttons and none of them come up with the green highlight, no matter how much I press the ctrl+shift and Q button.
I've also tried this with just the client AUT running and have tried the observer mode to see if that picked anything up. I also saw someone said to try the "remote" AUT agent instead of the embedded one, but that hasn't worked either.
I saw some people mention the AUT log files, but haven't found a window with that information in. Does anyone have an idea what it causing this? I'm guessing it's something to do with how my application was developed, but what it is, I don't know.
Other useful information:
The project is a JavaFx project
The project is being made with the java 1.8.0_51 library
Jubula version is 8.1.0
Eclipse is 4.5.0
I'm working on Windows 8.1
If people want to see the project or something else, please ask. Hope you can help!
[Edit] I've attached the XML file from the export of Jubula
[Updated on: Thu, 23 July 2015 13:52] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Unable to map objects [message #1703112 is a reply to message #1703111] |
Tue, 28 July 2015 15:18 |
Thomas Mortimer Messages: 18 Registered: July 2015 |
Junior Member |
|
|
Hi Alex,
I've found the issue, it's this:
When exporting a runnable Jar file from Eclipse, there are some options, called library handling, that list the following:
1. Extract required libraries into generated JAR
2. Package required libraries into generated JAR
3. Copy required libraries into sub-folder next to generated JAR
I had originally selected the 2nd one due to some testing I was doing earlier, trying to fix another issue I had. I had fixed the issue another way and left it as that option and found no issues whilst running the jar file.
Jubula however doesn't like that setup and that was causing my issue, upon changing the option to the 1st one in the list and doing the extraction again, the file suddenly started working with the object mapper.
I don't fully understand how the library handling works, but changing it to the default option has now fixed my issue and hasn't caused any other problems. So you can consider it fixed from my point of view.
To answer your other question, yes it was an FXML file, but I hadn't noticed the slow load times.
Again, thank you for your help and I hope this topic helps someone else. Please let me know if you would like more information.
Tom
[Updated on: Tue, 28 July 2015 15:23] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.08797 seconds