=============== ROOT CAUSE =====================
Caused by: java.lang.SecurityException: class "module-info"'s signer information does not match
signer information of other classes in the same package.
For trouble shooting, please visit: https://docs.katalon.com/katalon-studio/docs/troubleshooting.html
================================================
09-03-2021 06:39:13 PM Verification
Elapsed time: 0.432s
Verification FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Keyword runFeatureFile was failed (Root
cause: java.lang.SecurityException: class "module-info"'s signer information does not match signer
information of other classes in the same package
If you read the mentioned docs carefully, the JRE can be changed to compile and run test projects
However, katalon himself still needs openjdk8 to run (I think the windows version came with an embedded java for runtime)
there is no mention there to upgrade java, only to use an alternate JRE rather than the default set for OS on linux (or other than the embedded version for mac and windows)
did you read the previous post?
for the rest, you are right.
no resolution from user side, therefore no possible solution from katalon comunity.
cheers!
Because Oracle removed jaxb-api since Java 11 so we just need to add jakarta.xml.bind-api-2.3.3 in Library Management >> implementation group: ‘jakarta.xml.bind’, name: ‘jakarta.xml.bind-api’, version: ‘2.3.3’
Another thing for security exception >>> we should declare all of step definitions in packages NO step definition should be in default package and then update default packages for Step Definition in Test Listeners: Follow this documentation strictly Working with BDD feature files in Katalon Studio | Katalon Docs
I won’t suggest it. In my experience, it is a good tool at the start but eventually, it is hard to maintain and it scales badly. It is useful to know it if you come to a team, which already uses it and wants to migrate from it to let’s say Selenium I would suggest you learn selenium (if did not already), Cypress, or Playwright. UI-based codeless tools are all the hype for non-technical testers at the start until you need to maintain it, it is a nightmare then.