Auth Token is not getting refreshed due to which API is getting failed with error 401
Hirichie Auth Token is not getting refreshed automatically though I have ticked the checbox in settings too and due to which I have to intervene manually and update the token Please refer the screenshot for the sameAutomating the process to get access token
I am working on a soap automation project on which I need access token. We have to click on "Auth" tab 2. Click on "Get Access Token" 3. Click on "Get Access Token" again 4. Wait for SoapUI Browser to open to manually enter in the data and click "Login to Application " From there we now can run all the Requests solution for the Automation section in the "Get Access Token" section > Automation... Button where you can put a page 1 or page 2 script. (none of the online examples worked for Salesforce) or or b. A Groovy way to do the above or c. To Generalize - we don't want to have to manually do the above 1-4 steps Please suggest me how to automate the above 1-4 steps.
Error - org.openqa.selenium.SessionNotCreatedException: Could not start a new session
I am facing a dependency issue while calling selenium from ReadyAPI. Ready API version - 3.20.0 All selenium libraries are placed directly in ReadyAPI install directoryE:\ReadyAPI-3.20.0\bin\ext Selenium with Java version :4.1.1 (December 17, 2021) Chrome version is -Version 97.0.4692.71 Chromedriver version is that compatible with97.0.4692.71 Chromedriver.exe is placeddirectly in ReadyAPI install directoryE:\ReadyAPI-3.20.0\bin\ext Following is the Groovy script I have in my Ready API test: import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import java.util.concurrent.TimeUnit System.setProperty("webdriver.chrome.driver", System.getProperty("user.dir")+"\\ext\\chromedriver.exe"); log.info(System.getProperty('webdriver.chrome.driver')) WebDriver driver = new ChromeDriver(); driver.get("https://www.google.com"); On executing the script, i get the following error: Tue Jan 18 20:21:23 CST 2022: ERROR: org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:577) at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:246) at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:168) at org.openqa.selenium.chromium.ChromiumDriver.(ChromiumDriver.java:108) at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:104) at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:91) at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:46) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:78) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:72) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:263) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:268) at Script1.run(Script1.groovy:6) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.runAndGetResult(SoapUIGroovyScriptEngine.java:111) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:97) at com.eviware.soapui.support.scripting.groovy.SoapUIProGroovyScriptEngineFactory$SoapUIProGroovyScriptEngine.run(SoapUIProGroovyScriptEngineFactory.java:98) at com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep.run(WsdlGroovyScriptTestStep.java:159) at com.eviware.soapui.impl.wsdl.panels.teststeps.GroovyScriptStepDesktopPanel$RunAction$1.run(GroovyScriptStepDesktopPanel.java:334) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) at java.base/java.lang.Thread.run(Thread.java:831) Caused by: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start. Build info: version: '4.1.0', revision: '87802e897b' System info: host: 'SOAPUI-PRO-5', ip: '10.39.186.126', os.name: 'Windows Server 2012 R2', os.arch: 'amd64', os.version: '6.3', java.version: '16.0.1' Driver info: driver.version: ChromeDriver at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:227) at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:95) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:559) ... 25 more Caused by: java.util.concurrent.ExecutionException: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start. Build info: version: '4.1.0', revision: '87802e897b' System info: host: 'My host machine name', ip: 'My IP', os.name: 'Windows Server 2012 R2', os.arch: 'amd64', os.version: '6.3', java.version: '16.0.1' Driver info: driver.version: unknown at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395) at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2092) at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:217) ... 27 more Caused by: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start. Build info: version: '4.1.0', revision: '87802e897b' System info: host: host: 'My host machine name', ip: 'My IP', os.name: 'Windows Server 2012 R2', os.arch: 'amd64', os.version: '6.3', java.version: '16.0.1' Driver info: driver.version: unknown at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:248) at org.openqa.selenium.remote.service.DriverService.lambda$start$1(DriverService.java:202) at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1764) ... 3 more Caused by: org.openqa.selenium.net.UrlChecker$TimeoutException: Timed out waiting for [http://localhost:64319/status] to be available after 20002 ms at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:89) at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:244) ... 5 more Caused by: java.util.concurrent.TimeoutException at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204) at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:87) ... 6 moreSmartBear Talks | Meet the ReadyAPI Team - Alianna Inzana
I’m sure you want to know more about ReadyAPI!We continue introducing the members of theReadyAPIteam to you, so you can learn more about the people who are developing the best tool for API testing –ReadyAPI! Today, we will talk withAlianna Inzana, Senior Director of Product Development for API and Virtualization. Ali started her career as an analyst, where she was happy to work with digits before she dove into the world of APIs. Check out what her passion is these days, along with what we can expect fromReadyAPIin 2021. Alianna Inzana-Senior Director of Product Development for API and Virtualization at SmartBear I hope you found this video informative! Feel free to post your questions under this post, in case you have any. More video interviews are available under the Interview label. Don't forget to subscribe to the SmartBear Community Matters blog to get updates about all the great content we post here.SmartBear Talks | Meet the ReadyAPI Customer Care Manager - Anastasia Batazova
Greetings! We continue showing you the faces of the ReadyAPI Team at SmartBear. Today, we will talk with Anastasia Batazova (aka Nastya_Khovrina), the SmartBear Customer Care Manager for API Products. In this short interview, we will learn Anastasia's background and her path to becoming a Customer Care manager, Anastasia will share details about the internal processes the team uses to support ReadyAPI customers. Watch the interview:https://youtu.be/e6b1Q1KbuL0 Anastasia Batazova - SmartBear Customer Care Manager, API Products Quick links: 00:00 Introduction 00:50 Anastasia background 01:32 Which products Anastasia manages 02:16 Day to day work duties 04:00 Support Engineer vs. Support Manager 05:25 Self-Education and Team-Education 07:45 The support cases Anastasia prefers to answer 08:54 Customer Care working process 11:25 Thank you I hope you found this video informative! Feel free to post your questions under this post, in case you have any. You can watch more videos with the ReadyAPI Team here. Don't forget to subscribe to the SmartBear Community Matters blog to get updates about all the great content we post here.SmartBear Talks | Meet the ReadyAPI Project Lead - Ilya Avdeev
Greetings! We continue introducing the ReadyAPI Team to all of you. In this video, we will meet Ilya Avdeev - ReadyAPI Project Lead - and learn more about Ilya, his work, and why TestComplete is important for ReadyAPI. You can watch more videos with the ReadyAPI Team here. Ilya Avdeev-ReadyAPI Project Lead at SmartBear Quick links: 00:00 Introduction 00:39 Ilya's background 01:03 How Ilya joined SmartBear 02:12 The most rewarding part of the day to day work 03:08 Motivation to be a developer 04:18 The most memorable ReadyAPI feature that was developed 06:10 "All ReadyAPI features are my kids :)" 07:06 How we develop ReadyAPI features 10:40 Thank you I hope you found this video informative! Feel free to post your questions under this post, in case you have any. More video interviews are available under the Interview label. Don't forget to subscribe to the SmartBear Community Matters blog to get updates about all the great content we post here.
SmartBear Talks | Meet the ReadyAPI QA Lead - Nikolay Mirontsev
Greetings! This is the freshest video interview within the Inside ReadyAPI initiative. Please meet a new ReadyAPI hero - Nikolay Mirontsev, ReadyAPI QA Lead. In the interview, we talk about Nikolay's duties and the specifics of testing ReadyAPI. You will learn which approaches to testing the team prefers, as well as how the team is using ReadyAPI to test ReadyAPI. I'm sure this video will be interesting for all API testers. Watch the interviewhttps://youtu.be/K7tegwlW9RMand leave your comments below: Nikolay Mirontsev-SmartBear QA Lead for ReadyAPI Quick links: 00:00 Introduction 01:24 Nikolay's background 01:54 The path to becoming a QA Lead 02:53 Day-to-day work 03:42 Self-Education 04:31 How we test ReadyAPI 05:27 Automated tests for ReadyAPI 06:39 Monthly release cycle - specifics of testing 08:07 The most memorable ReadyAPI feature for testing 09:39 Why ReadyAPI is perfect for API testers 10:34 Thank you I hope you found this video informative! Feel free to post your questions under this post, in case you have any. You canwatch more videos with the ReadyAPI Team on this page.
