loadUI-cmd doesn't generate report
When i use the next command : loadUI-cmd.bat -Dloadui.msl.globals.loadFactor=100 -Dsoapui.properties=my.properties -F PDF -L 130:0:0 -l -nofx -p "d:\Repos\msl\msl\app\my-load-project.xml" -r "d:/my...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHello,
The -nofx parameter prevents loadUI from trying to load any JavaFX related packages, and it is used when launching the loadUI Agent, or Command line runner. It is automatically added when running loadUI-cmd.bat, so whether you provide it yourself or not should have no effect. The error related to the loadui-fx-interface bundle not starting it expected, and can be ignored. The reason for it is that the underlying OSGi runtime that loadUI uses attempts to load all the different bundles in a specific directory. Since the user interface depends on the JavaFX classes being present, it fails. It's not a very elegant solution to preventing the gui from loading, but the error itself is harmless, so it hasn't been a hgiht priority for us to get rid of.
Now, on to your problem regarding the report generation! As far as I know, the report generation should work on a TestCase level as well as on the Project level. When specifying a testcase with -t, does the correct test seem to run? Does it complete as expected (displaying a "TEST EXECUTION COMPLETED" message)? It sounds like it may be a bug related to generating reports for TestCases...
Regards,
Dain
eviware.com
The -nofx parameter prevents loadUI from trying to load any JavaFX related packages, and it is used when launching the loadUI Agent, or Command line runner. It is automatically added when running loadUI-cmd.bat, so whether you provide it yourself or not should have no effect. The error related to the loadui-fx-interface bundle not starting it expected, and can be ignored. The reason for it is that the underlying OSGi runtime that loadUI uses attempts to load all the different bundles in a specific directory. Since the user interface depends on the JavaFX classes being present, it fails. It's not a very elegant solution to preventing the gui from loading, but the error itself is harmless, so it hasn't been a hgiht priority for us to get rid of.
Now, on to your problem regarding the report generation! As far as I know, the report generation should work on a TestCase level as well as on the Project level. When specifying a testcase with -t, does the correct test seem to run? Does it complete as expected (displaying a "TEST EXECUTION COMPLETED" message)? It sounds like it may be a bug related to generating reports for TestCases...
Regards,
Dain
eviware.com