Execute parallel Test with Selenium Server
I'm new to TestComplete and try to set up a private Selenium Grid server to run parallel test but encounter error as Selenium Server exit. Selenium jar and Java JVM directories have been inputted Can anyone guide me how to integrate Selenium Server14Views0likes1CommentADO Microsoft-Hosted Agent unable to navigate control
Hello, I am trying to get an ADO pipeline to run a Keyword test, and it is failing to do so. The Keyword test has one enabled step, to navigate to https://www.subzero-wolf.com/ in the Chrome browser. This step functions perfectly when it is run locally on my computer (there's not much that could go wrong). The pipeline has three steps in it: one which installs the Visual Studio Test Platform; one which installs the test runner, in this case I am using TestExecute; and the final VSTest step, which is in charge of running the Keyword Tests. The first two steps succeed just fine, but on the last step the pipeline throws the error that the test was "Unable to navigate to the https://... page" The pipeline agent is an MS-Hosted agent, called 'windows-latest'. I have a feeling that there is something wrong with the environment we are running the test in, but I don't have enough knowledge to determine what should be added or removed. I would be happy to provide you with any further information I can give you about the state of the pipeline. Thank you for your assistance!Solved61Views0likes5CommentsFailed to update the interface: [ Invalid QName value: Can't resolve prefix 'xs]
Hi, I get this error when trying to update the API definition in the existing project (we use Swagger): Failed to update the interface: [ org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid QName value: Can't resolve prefix 'xs' ] Full error log: Thu Dec 08 10:12:27 EST 2022: ERROR: org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid QName value: Can't resolve prefix 'xs' org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid QName value: Can't resolve prefix 'xs' at org.apache.xmlbeans.impl.values.JavaQNameHolder.parse(JavaQNameHolder.java:140) at org.apache.xmlbeans.impl.values.JavaQNameHolder.set_text(JavaQNameHolder.java:158) at org.apache.xmlbeans.impl.values.XmlObjectBase.update_from_wscanon_text(XmlObjectBase.java:1180) at org.apache.xmlbeans.impl.values.XmlObjectBase._check_dated(XmlObjectBase.java:1331) at org.apache.xmlbeans.impl.values.XmlObjectBase.check_dated(XmlObjectBase.java:1283) at org.apache.xmlbeans.impl.values.JavaQNameHolder.getQNameValue(JavaQNameHolder.java:185) at com.eviware.soapui.config.impl.RestParameterConfigImpl.getType(Unknown Source) at com.eviware.soapui.impl.rest.support.XmlBeansRestParamsTestPropertyHolder$XmlBeansRestParamProperty.getType(XmlBeansRestParamsTestPropertyHolder.java:462) at com.eviware.soapui.impl.rest.support.XmlBeansRestParamsTestPropertyHolder$XmlBeansRestParamProperty.setType(XmlBeansRestParamsTestPropertyHolder.java:481) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.initParam(UpdateDefinitionManager.java:78) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.updateParamList(UpdateDefinitionManager.java:170) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.updateMethod(UpdateDefinitionManager.java:187) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.tryUpdateExistMethod(UpdateDefinitionManager.java:245) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.updateMethodList(UpdateDefinitionManager.java:260) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.updateResourceNode(UpdateDefinitionManager.java:285) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.tryUpdateExistingNode(UpdateDefinitionManager.java:299) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.tryUpdateChildResourceNodes(UpdateDefinitionManager.java:317) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.updateResourceNodeBase(UpdateDefinitionManager.java:333) at com.eviware.soapui.impl.rest.support.UpdateDefinitionManager.updateDefinition(UpdateDefinitionManager.java:364) at com.eviware.soapui.impl.rest.actions.service.UpdateRESTServiceWizard.perform(UpdateRESTServiceWizard.java:190) at com.eviware.soapui.impl.rest.actions.service.UpdateRESTServiceWizard.perform(UpdateRESTServiceWizard.java:1) at com.eviware.soapui.support.action.swing.SwingActionDelegate.actionPerformed(SwingActionDelegate.java:200) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1972) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2313) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:374) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1028) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1072) at java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297) at java.desktop/java.awt.Component.processMouseEvent(Component.java:6626) at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3389) at java.desktop/java.awt.Component.processEvent(Component.java:6391) at java.desktop/java.awt.Container.processEvent(Container.java:2266) at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5001) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833) at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4948) at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4575) at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4516) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2310) at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2780) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:773) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716) at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:746) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:744) at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:743) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)Solved1.2KViews0likes4CommentsIs 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.206Views1like1CommentUnable to auto-login to Azure Agent
Hi Community, I am using a self-hosted agent and I am triggering runs through a pipeline. I have setup the auto-logon/ Interactive mode in the agent. I am currently manually logging into the agent and then triggering the pipeline. and then in the pipeline disabling the user session and things are working as expected. My requirement is to auto-login to the Agent so that session would be opened after triggering the pipeline and then disable the user session which i already have in the pipeline.. I've seen in the smartbear tutorial the below info, An interactive user session must be opened on your test agent. You can open the session manually, or, if you use Team Foundation Server 2018 or later, you can configure your agent to run with the auto-logon enabled to open the session automatically when it starts. You enable the auto-logon when you configure your agent. To learn about configuring agents, seedocs.microsoft.com/en-us/azure/devops/pipelines/agents/. Can someone help me with this. Thanks & Regards, Nandini107Views0likes3CommentsAzure batch node DistributedCOM error when running SessionCreator
Hi, I am having an issue with running SessionCreator on Azure. Our automation setup uses Azure Batch to run Tasks on nodes. Each task will run the test project using SessionCreator on the node. The problem we are running in to, is that when the second task runs on a node, at some point the automation will stop running. Looking at our custom logs we can see that just after one of the automated tests runs, a DistributedCOM error occurs: The above issue is happening regularly on the second Task that runs (second run off SessionCreator) on the same node. I am wondering has anyone encountered anything like this before? I am still unsure if this is a SessionCreator issue or an Azure issue. Thanks for any advice!Solved44Views0likes4Comments