Checking API Status in TestComplete
Introduction I first saw the need to verify the state of an API several years ago with an application that used an address validation API in several of it's operations. If this API was down or did not respond in a timely manor, many of the automated test cases would run and fail. In this case, and in others, I have found that doing a simple call to the API to check the returned status code allowed me to skip, fail or log a warning with a logical message instead of allowing the application to fail with another less direct error message due to the API issue. The aqHttp Object The TestComplete aqHttp object and it's methods are very useful for performing simple checks like this and are also useful for other more complex tasks like leveraging an API to return a test data set or even verifying a certain data is returned prior to running tests against the UI that depend on the data. Sending and Receiving HTTP Requests From Script Tests More Complete API Testing Most proper API testing should be done using a tools like ReadyAPI or SoapUI. Both of these tools will integrate with TestComplete or can be used alone and will provide much more capabilities and automation options. Integration With ReadyAPI and SoapUI Code Example Here I have provided a working example of how to code a Get request using 'aqHttp.CreateRequest' to confirm an API returns a status code of 200 and it will log the returned records. function sendGetRequest() { let resourcePath ="https://restcountries.com/v3.1/all" let resourceQuery = "?fields=name,capital"; let url = resourcePath + resourceQuery; try { // Send GET request let response = aqHttp.CreateRequest("GET", url, false).Send(); // Check for successful response if (response.StatusCode === 200) { // Parse JSON response let allData = JSON.parse(response.Text); Log.Message("Total records received: " + allData.length); // Process each record allData.forEach((record, index) => { Log.Message("Record " + (index + 1) + ": " + JSON.stringify(record)); }); return true; // Send a bool back to the calling function. } else { throw new Error("Failed to fetch data. Status code: " + response.StatusCode); } } catch (error) { Log.Error("Error during request or data processing: " + error.message); } } Enhancements You could accept parameters for the resourcePath and resourceQuery. Parameterize the logging loop run or remove it. Return the JSON to the calling function for use. Perform other tasks based on the return code. Conclusion With the growing use of API calls in desktop applications and the fact that APIs are almost the foundation of any web site checking an API before a test case run is almost a requirement for consistent test runs and good error logging. This small script can bring big rewards to your test runs and reports. Cheers! I hope you find it as useful as I have! If you find my posts helpful drop me a like! 👍 Leave a comment if you want to contribute or have a better solution or an improvement. 😎 Have a great day
TestComplete Allure Jenkins Integration
Did any one tried TestComplete Allure Jenkins Integration. I am unable to see Test steps when using /exportsummary.Its working fine but showing basic detail and when using /exportlog then its unable to parse xml file. I want to see TestLog also in Allure html file.
Use Variables in the sql connectionstring
Hi there, I'm using 2 environments and 2 databases: 1 to create the testcases and 1 to execute them I want to check the results with DBTables Custom queries (SSMS) and I have i.e. next connectionstring: How CAN I make this string Variable ? When I login at the ALPHA-environment I want in the string ALPHA and server01 When I login at the BETA-environment I want in the string BETA and server02 Greetings, Sjef van Irsel
VS 2019 - Failed to initialize the TFS API Library
When we try to access the Server Path and add a Server location to access the Online Repo getting an error as Steps to reproduce: 1) Navigate to Tools -> Options -> Source Control and select 'Current Source Control Plugin ' as 'Microsoft Visual Studio 2019' [already installed locally and Source path / Workspace is set] 2) Navigate to File -> Source Control -> Open From Team Foundation Server... 3) Click on the ... button at the 'Server Path:' section.
java.lang.NoClassDefFoundError error message when integrating with Selenium/Maven/TestNG project
Hi Team, I have a selenium project developed in Selenium Java, Maven and TestNG framework. The framework is like all the dependencies are in one maven project and all the framework related classes are in another project which is dependent on dependencies project. And my application automation project which is developed in selenium java, maven and testng which is dependent on framework maven project and dependencies project. When I am integrating this with Test Complete, I am able to copy all src folder, testng xml files, pom.xml into test complete project directory and able to compile it and all the classes are in target\classes directory with no errors. and also added all the dependencies into target\dependency folder And i have created UnitTesting item and added TestNG and provided the values as mentioned below. But when I am running the class in test complete, it is compiling successfully but giving me the error as NoClassDefFoundError. I have added the target\classes and dependencies explicitly in Java Bridge also but it is throwing me the same error. Error: FAILED: testscripts.smoke.SmokeTest1.createNewCompanyContactAndOrg java.lang.NoClassDefFoundError: framework/utils/ApplicationLauncher at testscripts.smoke.SmokeTest1.createNewCompanyContactAndOrg(SmokeTest1.java:15) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139) at org.testng.internal.invokers.TestInvoker.invokeMethod(TestInvoker.java:664) at org.testng.internal.invokers.TestInvoker.invokeTestMethod(TestInvoker.java:228) at org.testng.internal.invokers.MethodRunner.runInSequence(MethodRunner.java:63) at org.testng.internal.invokers.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:961) at org.testng.internal.invokers.TestInvoker.invokeTestMethods(TestInvoker.java:201) at org.testng.internal.invokers.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:148) at org.testng.internal.invokers.TestMethodWorker.run(TestMethodWorker.java:128) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at org.testng.TestRunner.privateRun(TestRunner.java:819) at org.testng.TestRunner.run(TestRunner.java:619) at org.testng.SuiteRunner.runTest(SuiteRunner.java:443) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:437) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:397) at org.testng.SuiteRunner.run(SuiteRunner.java:336) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:95) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1301) at org.testng.TestNG.runSuitesLocally(TestNG.java:1228) at org.testng.TestNG.runSuites(TestNG.java:1134) at org.testng.TestNG.run(TestNG.java:1101) at org.testng.TestNG.privateMain(TestNG.java:1461) at org.testng.TestNG.main(TestNG.java:1425) Caused by: java.lang.ClassNotFoundException: framework.utils.ApplicationLauncher at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) ... 28 more =============================================== Command line test Tests run: 1, Failures: 1, Skips: 0 =============================================== [INFO ] 2024-12-09 14:40:19,918 framework.utils.DriverHelper:128 - Stopping Win app driver [INFO ] 2024-12-09 14:40:19,938 framework.core.FrameworkScript:162 - Quitting driver =============================================== Command line suite Total tests run: 1, Passes: 0, Failures: 1, Skips: 0 =============================================== As per the error it is not able to find the ApplicationLauncher class during run time. But the class file is present in target\classes folder. I have tried recompiling again and again but the result is same. PS: I am able to run the selenium project outside the test complete without any issues.Question about ReadyAPI test item
Is there any way, either in the GUI of the ReadyAPI test item or a script, to make the path to the ReadyAPI project file (XML) something like Project.ConfigPath + file name.xml. I know you can use this in scripts but I am not sure how to do this in conjunction with the ReadyAPI test item. The issue I am facing is having the file on a network drive is intermittently not working and if I make it a local path (C:\Projects\ReadyAPI), everyone on the team would need the file in that same location and it wouldn't be in source control.
