ReadyAPI - Soap NG Pro - Run headless on TeamCity CI - Console Installation - Licence
Hello, We are trying to improve our continuous integration process and the automation of tests execution. For this we would like to set up a smoke test suite which would be easily executable from a TeamCity instance which means that it has to run headless. As a current status we arrived to make it work on a local machine. We noticed that we are forced to have a local installation of ReadyAPI together with a configured hermesJMS to bundle it into our maven build using the 'ready-api-maven-plugin' since we did not find any version of the plugin containing an embedded version of ReadyAPI. To setup the same build on the TeamCity build we only have some linux agents with limited access and no serverx (no ui - headless). We did not find anything in the documentation regarding the installation of ReadyAPI using console + how to setup a licence using console as well.. Could youindicate us how to achieve this without any UI!? Please find below our current maven configuration: ... <plugin> <groupId>com.smartbear</groupId> <artifactId>ready-api-maven-plugin</artifactId> <version>1.7.0</version> <executions> <execution> <id>functionalTests</id> <phase>test</phase> <goals> <goal>test</goal> </goals> <configuration> <optOutUsageStatistics>true</optOutUsageStatistics> <projectFile>${project.build.testOutputDirectory}/soapui/${soapuiProject}</projectFile> <printReport>true</printReport> <reportFormat>HTML</reportFormat> <testFailIgnore>true</testFailIgnore> <junitReport>true</junitReport> <outputFolder>${project.build.directory}/surefire-reports</outputFolder> <testFailIgnore>true</testFailIgnore> <exportAll>false</exportAll> <environment>${environment}</environment> <globalProperties> <globalProperty>hermesConfig=${hermesConfig}</globalProperty> <globalProperty>someProp=${someProp}</globalProperty> </globalProperties> <readyApiProperties> <property> <name>soapui.home</name> <value>${soapui.home}</value> </property> </readyApiProperties> </configuration> </execution> </executions> </plugin> ... Thanks a lot!Tasks set at running state even when test run is complete
Hi, We have a master project that start our UI tests (slave project with different tests group) on different hosts (VM). We have a task for each VM. We are using TeamCity to start our tests. There is a queue with our UI Tests and after two other project: WebTesting and LoadTests. But sometimes one of thetest group on a VM is complete but the task doesn't come back as idle and stays at running state. This is an issue as TestExecute (running the Master Project) will keep on waiting for all tasks to finish, but since one task is stuck at running state, TestExecute will not stop. Then the other project WebTesting and LoadTests in the queue will not start because TestExecute is still running. Do you have any solution about that ? Why our tasks are staying sometimes on running state after our tests are done ? Thank you for your answers, CamilleScreen resolution of a VM using RDP with TestComplete
Hi, To test our desktop application we have a Master project that runs the Slave project on different VMs. We are using TeamCity to start our tests. On a TestManagement machine (VM)we have a Build Agent that is running as Service. This Build Agent starts the Master project with TestExecute. This project connects withRDP to different VM to run our UI Tests (Slave project)of our App.We are using Network Suite and run our tests on Hosts (VMs) like it is suggest here: Using Network Suite. But we have an issue with the screen resolution that is used to run our UI Tests. The resolution is too low. This page Running tests via RDP gives an explanation: "When running tests on a remote computer that participates in distributed testing, TestComplete creates a Remote Desktop session and automatically sets the master computer's screen resolution on the remote computer. This is done to avoid possible problems with test running." So TestExecute will use the master computer's screen resolution. But TeamCity Agent is run as a service on a VM (TestManagement machine) and there is no screen resolution because it's an headless machine and not like a real user that will connect with RDP to this VM and start the Master Project. I assume TestExecute will then use the default screen resolution (something like 640x480) as the resolution for the RDP connection. But this is too low to run our tests, some object are not on the screen and we have many issues... Is there a way to change the resolution used by the RDP connection that TestExecute / TestComplete will create ? The tricky part is that the Master project is started from a service on an headless machine... Thank you for your answers, Camille
