search

reportportal / agent-java-soapui

Apache License 2.0
4 stars 7 forks source link

Getting error while building the gradle project. No support for ReadyAPI Version 2.7.0 #10

Open iamakshayshar opened 5 years ago

iamakshayshar commented 5 years ago

Follow the same setup provided in the ReadMe section of the gradle project, but getting issue while project is build. Also this version of the project is not supporting 2.7.0 version of ReadyAPI. Please help

f4br3 commented 5 years ago

@Aksh165 Could you leave more information about your build issue? Because as i could see everything works fine. Untitled11

f4br3 commented 5 years ago

@Aksh165 About ReadyAPI support, I'm currently using this agent with 2.7.0 version and it correctly sends logs to the ReportPortal. But every time you need to set test suite to run from your ReadyAPI project, somehow it not works when you want to run whole ReadyAPI project with all test suites at a time, i think it's a bug.

@DzmitryHumianiuk Could somebody take a look on it?

DzmitryHumianiuk commented 5 years ago

@f4br3 it also can be a limitation of Free version against PRO version

staind825 commented 5 years ago

I've also tried pulling the project into Eclipse and cannot build. Not sure whats going on: buildissue

image

f4br3 commented 5 years ago

@DzmitryHumianiuk Completely sure, this is agent problem, because i'm using SoapUI Pro version in ReadyAPI and i don't have any limitations in it.

DzmitryHumianiuk commented 5 years ago

@f4br3 ok. Will take a look next week

DzmitryHumianiuk commented 5 years ago

@staind825 is it a Gradle related issue?

f4br3 commented 5 years ago

@staind825 Something wrong with your Gradle here, i think it happens not only in current project.

iamakshayshar commented 5 years ago

@f4br3 Hey, If this work for you. would you mind helping me with the .zip file. I will extract the all the jar files and place them to the SOAPUI_HOME/bin/ext and SOAPUI_HOME/bin/listeners.

I will try following the other steps in ReadMe section.

iamakshayshar commented 5 years ago

@Aksh165 Could you leave more information about your build issue? Because as i could see everything works fine. Untitled11

Capture

This is the issue I am getting while building the gradle project from my laptop.

f4br3 commented 5 years ago

@Aksh165 No problem, here is the .zip that you need - soapui-4.0.0-SNAPSHOT-full.zip

f4br3 commented 5 years ago

Capture

This is the issue I am getting while building the gradle project from my laptop.

This issue related to your network, because Gradle trying to get all of the imports needed to build a project, but it cannot be resolved via DNS.

iamakshayshar commented 5 years ago

Capture This is the issue I am getting while building the gradle project from my laptop.

This issue related to your network, because Gradle trying to get all of the imports needed to build a project, but it cannot be resolved via DNS.

Yup that may be the scenario. I will work with the team here in my office. Also thanks for the .zip file, i can work with this as of now.

iamakshayshar commented 5 years ago

@Aksh165 No problem, here is the .zip that you need - soapui-4.0.0-SNAPSHOT-full.zip

Will this work with ReadyAPI 2.7.0 version also ?

f4br3 commented 5 years ago

Will this work with ReadyAPI 2.7.0 version also ?

But every time you need to set test suite to run from your ReadyAPI project, somehow it not works when you want to run whole ReadyAPI project with all test suites at a time, i think it's a bug.

Correct, but because of the bug (i hope it will be fixed soon) only as how i describe it above. You just need to run your tests by separate test suites, not like whole project run.

f4br3 commented 5 years ago

@f4br3 ok. Will take a look next week

@DzmitryHumianiuk Do you already have any information about this issue?

DzmitryHumianiuk commented 5 years ago

@f4br3 still in next sprint. team postponed this, since we have code freeze for v5

jainriteshkumar17 commented 5 years ago

i have tried adding the properties from report portal in the custom properties of individual test suite in ready API but didn't work. are we sure about same zip being used for soap UI and ready API or there could be some difference as Soap UI is free ware and Ready API is a licensed one.

f4br3 commented 5 years ago

i have tried adding the properties from report portal in the custom properties of individual test suite in ready API but didn't work.

You need to add these properties as 'Custom Properties' for the project, not like properties of individual test suite.

are we sure about same zip being used for soap UI and ready API or there could be some difference as Soap UI is free ware and Ready API is a licensed one.

I'm sure that there is no difference for this .jar between SoapUI and ReadyAPI.

f4br3 commented 5 years ago

@f4br3 still in next sprint. team postponed this, since we have code freeze for v5

@DzmitryHumianiuk Any approximate time when this sprint will happens and bug will be fixed?

lio972 commented 5 years ago

Hi i have issue with soapui. Nothing is sent to rp; When i modify soapui logging file to add appender etc... i even get exception

Wed Aug 14 14:30:59 CEST 2019:INFO:log4j:ERROR Could not create an Appender. Reported error follows.
java.lang.ClassNotFoundException: com.epam.ta.reportportal.soapui.log.SoapUILogAppender
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
    at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:174)
    at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150)
    at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163)
    at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425)
    at org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:345)
    at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:827)
    at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712)
    at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:604)
    at org.apache.log4j.xml.XMLWatchdog.doOnChange(DOMConfigurator.java:861)
    at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:88)
    at org.apache.log4j.helpers.FileWatchdog.<init>(FileWatchdog.java:57)
    at org.apache.log4j.xml.XMLWatchdog.<init>(DOMConfigurator.java:853)
    at org.apache.log4j.xml.DOMConfigurator.configureAndWatch(DOMConfigurator.java:584)
    at com.eviware.soapui.DefaultSoapUICore.initLog(DefaultSoapUICore.java:492)
    at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:136)
    at com.eviware.soapui.DefaultSoapUICore.<init>(DefaultSoapUICore.java:132)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.createSoapUICore(AbstractSoapUIRunner.java:216)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:192)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:137)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:112)
    at com.eviware.soapui.tools.SoapUITestCaseRunner.main(SoapUITestCaseRunner.java:122)
log4j:ERROR Could not parse file [D:\sources\Program Files\SmartBear\SoapUI-5.5.0\SoapUI-5.5.0\bin\soapui-log4j.xml].
java.lang.NullPointerException
    at java.util.Hashtable.put(Unknown Source)
    at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:151)
    at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163)
    at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425)
    at org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:345)
    at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:827)
    at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712)
    at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:604)
    at org.apache.log4j.xml.XMLWatchdog.doOnChange(DOMConfigurator.java:861)
    at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:88)
    at org.apache.log4j.helpers.FileWatchdog.<init>(FileWatchdog.java:57)
    at org.apache.log4j.xml.XMLWatchdog.<init>(DOMConfigurator.java:853)
    at org.apache.log4j.xml.DOMConfigurator.configureAndWatch(DOMConfigurator.java:584)
    at com.eviware.soapui.DefaultSoapUICore.initLog(DefaultSoapUICore.java:492)
    at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:136)
    at com.eviware.soapui.DefaultSoapUICore.<init>(DefaultSoapUICore.java:132)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.createSoapUICore(AbstractSoapUIRunner.java:216)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:192)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:137)
    at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:112)
    at com.eviware.soapui.tools.SoapUITestCaseRunner.main(SoapUITestCaseRunner.java:122)
lio972 commented 5 years ago

I've build the project with gradle, done the install in soapui 5.5 folder en configure my project with the parameter

image

i've connected to RP as an admin and created a project named soapui. But not activity can be detected in RP

image

f4br3 commented 5 years ago

Hi i have issue with soapui. Nothing is sent to rp; When i modify soapui logging file to add appender etc... i even get exception

@lio972 Hmmm, i don't think, that you need to modify something in soapui-log4j.xml file, just revert this file back to default, add soapui-4.0.0-SNAPSHOT-all.jar to ext folder and reportportal-listeners.xml to listeners folder, double-check all properties, restart SoapUI, then try to run it again.

jainriteshkumar17 commented 5 years ago

is there some different provisions for report portal hosted on https protocol.

because i am not able to see the report in RP whil same thing when i am doing with http i am able to get the same but that is on a different server. https is not woking.

Can someone throw some light on this.

iamakshayshar commented 5 years ago

Hello @f4br3 & @DzmitryHumianiuk DzmitryHumianiuk, We are looking if there are some other configuration needs to be done if report portal is hosted on https secure network.

As of now, we have setup everything on report portal sandbox sever and our ReadyAPI (TestSuite report) and SOAPUI (project report) are getting added to the portal. But when I have moved the setup to Production which is a secured network (https), we are facing issue.

Would really appreciate your help on this.

DzmitryHumianiuk commented 5 years ago

@Dexter-Clone what kind of issue you faced?

most likely you have to add certificate into your ReadyAPI as well.

iamakshayshar commented 5 years ago

@DzmitryHumianiuk It just that execution from SOAPUI is finished but the reports are not published on ReportPort.

I will let you know if I face any issues once I will add the certificates for ReadyAPI & SOAPUI and add those to project properties.

iamakshayshar commented 5 years ago

@DzmitryHumianiuk Got this thing working after I have installed certificate for ReadyAPI. Thank you.

Requesting you to please let us know when the fix would role out which @f4br3 reported in this conversation, https://github.com/reportportal/agent-java-soapui/issues/10#issuecomment-516325285

lio972 commented 5 years ago

hi @f4br3 i've spent 3 day on reportportal, looking for a production plateform for my client. I finally give up. Too complicated, so few information. I'll stick to ELK and Allure.io. I done what you proposed by doesn't work. Neither jenkins or soapui send valuable data.

Your project ReportPortal look great. I think that i'll have a look in a few years.

Take care.

jaysidd commented 2 years ago

@DzmitryHumianiuk It just that execution from SOAPUI is finished but the reports are not published on ReportPort.

I will let you know if I face any issues once I will add the certificates for ReadyAPI & SOAPUI and add those to project properties.

@DzmitryHumianiuk Got this thing working after I have installed certificate for ReadyAPI. Thank you.

Requesting you to please let us know when the fix would role out which @f4br3 reported in this conversation, #10 (comment)

Hi, can you please provide steps on adding the certificate in SOAPUI for report portal.