Groovy:unable to resolve class - Javax only

Product Forums Katalon TestOps
1

Hello,

I have a project on my local PC where runs smoothly. However on TestOps where I setup my agent on Linux Debian machine, when I run my project my only issue is that is Groovy:unable to resolve class of the following classes.

Groovy:unable to resolve class javax.mail.Authenticator
Groovy:unable to resolve class javax.mail.internet.InternetAddress
Groovy:unable to resolve class javax.mail.internet.MimeMessage
Groovy:unable to resolve class javax.mail.Multipart
Groovy:unable to resolve class javax.mail.internet.MimeMultipart
Groovy:unable to resolve class javax.mail.Provider
Groovy:unable to resolve class javax.mail.Message
Groovy:unable to resolve class javax.mail.Session
Groovy:unable to resolve class javax.mail.PasswordAuthentication
Groovy:unable to resolve class javax.mail.internet.MimeBodyPart
Groovy:unable to resolve class javax.mail.Transport
Groovy:unable to resolve class javax.mail.MessagingException
Groovy:unable to resolve class javax.mail.Authenticator 
Groovy:Catch statement parameter type is not a subclass of Throwable.

I check my drivers folder I had the javax jar file, I tried to replace it with javaee.jar and still no luck on the linux machine. I checked my machine I have java runtime and sdk.

Anyone had this issue before and solve it?

P.S. I have other methods where I call for example java.io.FileInputStream and works fine.

4

java version 1.8.0

5

Any screenshot to prove what you have?

6

image
image768×49 2.74 KB

image
image802×604 27.6 KB

image
image1083×533 29.8 KB

7

yes. Screenshots added

Also want to add that I tested it on Katalon Engine 7.8.2 and latest 8.2.0

And facing the same issue.

8

@duyluong

Any idea?

9

@charitos.andreou
Did you upload the script repository from Studio to TestOps?
Screen Shot 2021-11-22 at 4.03.56 PM

11

Yes, I upload my script on TestOps as you show it on your screenshot.

12

@charitos.andreou

This is an issue of the Update Script Repository that doesn’t upload external libararies to TestOps. We were planed to fix it in v8.2.5.

The workaround, for now, is to manually zip and upload your project to TestOps including the external libraries or upload your project to Git then link with TestOps.

13

Thank you for the info. You were right, it worked when I uploaded my project manually.

1 Like