LoadUI has gone mad

Hi,

This is fixed internally, but we haven't got our nightly-builds of 2.0.0 to build properly yet.

In the meantime, you can replace Ramp.groovy (found in [loadUI installation folder]\script-components) with this:


Regards

Henrik
SmartBear Software

Hi, I did this and initially it solved the problem. But this morning its just the same as before I changed it, although the new groovy file is still in the script components folder?
So I deleted the ramp component on the loadui test case and put it back in again. (I can see the old original ramp.groovy in the generators to choose from - so I know I'm selecting the correct one), this time no requests at all are being generated.

Is there anyway I can go back to using 1.5 for the time being?

Also, I've noticed a post about table logs not working in distributed mode. Mine now don't work in normal mode, nothing is stored away in the .loadui directory like before and I'm sure there was much more in the way of settings on a table log beforehand, now I only have 'Advanced'.

Hi,

The TableLog component should have 3 settings tabs: General, Logging, and Advanced. There are no known bugs which affect the table log in local mode, only the mentioned problem with distribution, for which a fix will be available shortly. I'd recommend against downgrading to 1.5, as there are known issues with several of the Components that have been or will be fixed in 2.0. From what you're describing it sounds like there may be an issue preventing components from correctly loading. What about if you create a brand new Project, and add the components there. Do they function any differently? If so it might be an issue with your project file. In that case, would it be possible for you to send the file to us so that we can investigate it?

Regards,
Dain
SmartBear Software

When I start a brand new project the generator seems to work ok, but the table log is still the same.

Also I dont think that when make alterations they are saved. It saves things within a test case, but at the project level, if I remove a test and save the project, it's there again when I load it back up.

Now I've run it again........and it's back to the crazy request levels.
I have emailed my loadui project. Its called WHPath01. It only got one test case in it now, but you can see the problems.
Thanks

Hi,

I've been able to reproduce the problem with test cases not being deleted properly, but everything else seems to save correctly. I tested the project you sent, and aside from not having the soapUI Project used in the soapUI Runner, the components looked like they were working as they should. Can you try uninstalling and re-installing loadUI Pro? You shouldn't have to touch the .loadui directory, so you shouldn't have to re-activate the license or anything, it should just work. Make sure that the installation directory in Program Files is completely gone before re-installing though.

Regarding the saving issue, this will be fixed in the next available nightly build for loadUI 2.0.x.

Regards,
Dain
SmartBear Software

I've reinstalled LoadUI2.0 now and still the same. I've attached a picture of the table log and the settings dialogue.

Hi,

By the look of things, there really seems to be a problem with the loading of the component, are you sure there's no error in the System log?

Regards,
Dain
SmartBear Software

I've managed to get this from the system log which seems to mention table log.

Hi,

Ok, I see what's wrong now. We missed including an updated dependency used by this component, and for some reason the auto-downloading of this is failing (I'm not sure why this is). The next nightly build will have this dependency included, which should fix your problem. However, until then you can download the attached zip file and extract it to your .loadui/.groovy/grapes directory. Once done the TableLog should function correctly.

Regards,
Dain
SmartBear Software

Yay, that looks at lot better.
Thanks for your help with this.