Forum Discussion

sharajan's avatar
sharajan
Occasional Contributor
2 years ago
Solved

Listener events not getting registed when running through maven

I have a java utility created by implementing the 

TestRunListener,

ProjectRunListener

TestSuiteRunListener

 

The utililty jar when placed in soapui /ext is able to register the events and thereby create the reports when running the test suite.

 

The same utility when running through maven soapui plugin is not registering any events:

 

1) I placed the utility in the <maven project>/ext location

2) created xml file in the <maven project>/listener location

3) Used the soapui maven plugin 5.7 to run the scripts

4) the scripts run, and in the logs I see it registered the listener classes for suite, project and the test step

 

However after the script execution I do not see the report file generated, I tried to add debug lines by flushing to the soapui logs as

well as the system out. nothing printed out proving those methods(beforeRun , afterRun) were not even called

 

Can someone provide some pointers here if the soapui listeners work with soapui maven plugin ?

  • Hi Zgibanez,

     

    I had the same issue for logging as you do until I found the setting below.

    1. When editing a pipline, go the the TC test adapter installer.
    2. Search for the "Save logs for" option.
    3. Select the desired option

    4. Click on the i icon

    5. Link the TestComplete log to the test result

    After you run the pipeline you will get the logs just as in TestComplete itself. To find the logs open the pipeline who is finished and select the "Tests" tab.

    Your screen will look like this.

    Small tip: select the aborted filter en select the passed filter. This way you will also see the logs of passed tests.

    Select the testrun below, and in the attachments tab you will find the logs, and you will be able to download the logs.

    And your logs will look like the one from TC itself


    I am not sure if you are able to customize this outcome but this is way more detailed then the log created by Azure itself.


    I hope this is what you are looking for!

31 Replies