Forum Discussion

eelzinga's avatar
eelzinga
Occasional Contributor
15 years ago

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_output_dir" -t "myTestCase"

There won't be any output generated (pdf) in the my_output_dir folder.
When i remvoe the -t command it will generate the pdf. Is this only available when running a 'complete' project instead of a testcase?

Also when i add -nofx i would expect not to see the next stacktrace on startup :


ERROR: Error starting file:/D:/Apps/loadUI-1.0/bundle/loadui-fx-interface-1.0.1.jar (org.osgi.framework.BundleException: Unresolved constraint in bundl
e com.eviware.loadui.fx-interface [25]: Unable to resolve 25.0: missing requirement [25.0] package; (package=com.eviware.loadui.fx) - [25.0] package; (
package=com.eviware.loadui.fx))
org.osgi.framework.BundleException: Unresolved constraint in bundle com.eviware.loadui.fx-interface [25]: Unable to resolve 25.0: missing requirement [
25.0] package; (package=com.eviware.loadui.fx) - [25.0] package; (package=com.eviware.loadui.fx)
        at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3421)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:1754)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1188)
        at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
        at java.lang.Thread.run(Thread.java:619)


Or is the -nofx parameter not related to this stacktrace ?

2 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hello,

    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
  • eelzinga's avatar
    eelzinga
    Occasional Contributor
    15 years ago
    ------------------------------------
    TEST EXECUTION COMPLETED
    FINAL RESULTS: 00:10:00 Samples: 48 Failures: 2
    ------------------------------------

    and no report is created, so i guess it's a bug