Issue with Mounting Network Drive in TestEngine
Hello SmartBear Community, I'm encountering an issue with running my ReadyAPI tests via TestEngine that involves mounting a network drive. While the same tests run successfully in ReadyAPI, they fail when executed through TestEngine. Even when the network drive is available in the machine, with Testengine I'm getting an error "FileNotFoundException" when trying to read files from it. But with ReadyApi my script works correctly. This is an example of script : import groovy.json.JsonSlurper import groovy.io.FileType import java.util.logging.Logger // Définition du chemin du dossier contenant les fichiers JSON def chemindudossier = "Y:\\Regression\\1_FADETS\\4_COMM\\communication\\" // Création d'un nouvel objet JsonSlurper pour lire les fichiers JSON def jsonSlurper = new JsonSlurper() // Initialisation de trois compteurs pour compter le nombre total d'éléments JSON, le nombre d'éléments qui ont la structure attendue, et le nombre de "Tué" def totalCount = 0 // Parcourir tous les fichiers JSON dans le répertoire new File(chemindudossier).eachFileRecurse (FileType.FILES) { file -> // Lire le contenu du fichier JSON def content = file.text // Parser le contenu du fichier JSON def data = jsonSlurper.parseText(content) // Vérifier que chaque élément a la structure attendue totalCount += data.size() } log.info("Le nombre de communication est : $totalCount") //message d'erreur si le totalCount=0 if (totalCount == 0) { log.severe("Erreur : Aucun lien entre personne physique et telephone n'a été trouvé.") } Based on the documentation of Testengine, I did understand that there is a groovy restrictions on reading/writing files. I tried this 2 solutions that they propose and didn't work : 1- Added -Dgroovy.allow.all=true in ReadyAPITestEngine.vmoptions file 2- Edited readyapi-testengine.bat to include the -Dgroovy.allow.all=true flag: "%JAVA%" %JAVA_OPTS% -Dgroovy.allow.all=true -cp "%CLASSPATH%" com.smartbear.ready.testserver.ReadyApiTestServerMain %* Could you please help me to find a solution to my problem? I'm really stack and cannot progress in my tests! Thanks!
Is it possible to integrate the Azure TestPlan Test cases and the ReadyAPI tests ?
I have created manual test cases in Azure devops Test Plan. I have automated the manual test case functionality using ReadyAPI. Now i want to link the Azure Test Plan test cases while running the ReadyAPI tests via the Azure pieplines. Is it possible to do so ? I am using the Azure devops extension named "ReadyAPI Test for Azure Devops" and "Publish Test Results" in my pipeline.TestEngine external JAR files - error - unable to resolve class
Background - We have test engine hosted on some linux server and we execute tests suing CURL cmd or POSTMAN. Given some external JARs When we add external JARs in /bin/ext folder of test engine server and re-start the test engine And run the tests using curl command from locally or using POSTMAN Then it throws error for groovy script test step saying unable to resolve class <className present in external JARs> on import statement itself. We have also configured .vmoptions of test engine server to read ext JARs but still it throws error. Locally, In ReadyAPI, we are placing those JARs in /bin/ext/ folder and it works perfectly fine. Any solution to this problem?How to use the External JAVA libraries with Test Engine hosted on Linux
We are using the Test Engine to run our Ready API test suites and this server is a Linux machine. We are referring the java library (com.jcraft.jsch.*) within groovy script and this is used for file upload. this works fine while running the test in local with the Ready API application but while the same test with Test Engine, this suites fails as Test Engine is not able to find the the reference of java library(refere below error). Can you help us with below questions * Is there a default location which the Test Engine looks for external library reference? * Is there a way to have our own custom path for external reference and let the Test Engine refer this path? We looked into the official documentation, it has the details of path for Ready API but not for Test Engine
Test suite fails with error Failing due to failed test step\njava.security.AccessControlException
We have recently updated to ReadyAPI 3.49 and noticed that our build pipeline keeps failing, the test pass with 100% success rate but I see there is suite level failure with errorFailingduetofailedteststep\njava.security.AccessControlException:accessdenied(\"java.util.PropertyPermission\"\"*\"\"read,write\") We rolled back to an older version and that fixed the issue.Test Engine floating license gets automatically checked out
Hi, Our company uses a floating TestEngine license for running ReadyAPI test scripts during microservice deployments. Have noticed multiple times that the license gets checked out automatically due to inactivity and this fails the deployment with the message. Is there a way to disable this feature and never check-out? "ReadyAPI TestEngine license is not installed or has expired"TestEngine API to get the transaction details returns 404 - Intermittent Issue
We are running the Ready API tests in TestEngine and generating the report in JSON format. The JSON report doesn't returns the test's request and response. So we are using the CURL to get the details of failed tests's request and response using below TestEngine API. We use the details of failed transaction to debug a test and fix accordingly. As mentioned in the TestEngine documnetation (https://support.smartbear.com/testengine/docs/tutorial/get-result.html) we are using the TestEngine API to get the transaction details,below curl is been executed as a part of automation bash script to get the transaction details curl -u username:password http://localhost:8080/api/v1/testjobs/<testJobId>/transactions/<transactionId> Sometimes the above TestEngine API call returns 404 response as below (this is intermittent issue). But after sometime, the same above API works fine and returns the transaction details {"code":404,"message":"No transaction log found for testjobId: <testJobId> and transactionId: <transactionId>"} Help us in fixing this intermittent issue
