saucelabs

问题 I want to run my automation suite (implemented using Selenium Webdriver (Java) + TestNG + Maven) in parallel against multiple browser capabilities. I can run it in parallel for different capabilities using below sample testng.xml <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd"> <suite thread-count="5" name="Functional Test Suite" parallel="tests"> <test name="Windows-FF-37.0" preserve-order="true" > <parameter name="browser" value="Firefox"/> <parameter name="version" value="37.0"/>

问题 I'm using QAF Automation framework with Selenium Web Driver, Java, TestNG and been successful in executing one test at a time, remotely on Sauce labs. But my test executes for Windows OS, when I want it to execute on Mac OS. Not sure why windows is being selected by default. The only properties I provided are: remote.server=http://username:ACCESS_KEY@ondemand.saucelabs.com:80/wd/hub remote.port=80 driver.name=chromeRemoteDriver Where should I mention in QAF Framework? multiple OS - Windows or

问题 I am using specflow with NUnit on Saucelabs. I need to run features files in parallel . But I read somewhere that you cannot run in parallel if you are using ScenarioContext/FeatureContext which I am currently using in almost every test scenario. Is it true ? If true , what alternative can I use for multi threading. Please note that there is no dependency between the features or between the testcases in features. Can anyone provide a code snippet to help me implement parallel execution.

问题 I have existing selenium tests written in Robot IDE Framework that I'm trying to run in Sauce Labs. I'm using the sample test from this tutorial to see if I can get at least one test running. http://datakurre.pandala.org/2014/03/cross-browser-selenium-testing-with.html The test passes locally, and passes all the tests on Sauce Labs, but then times out and gives and error, "Test did not see a new command for 90 seconds. Timing out. error" because it's not disconnecting Remote Web Driver. I've

问题 I'm just starting out with intern/saucelabs. Whenever I try a remote test, I'm getting Error: failed to connect to tunnel VM. My intern.js has environments: [ { browserName: 'firefox', version: '28'}, ], tunnel: 'SauceLabsTunnel', tunnelOptions: { username: 'foo', accessKey: 'xxxxxxxxxxxx-xxxx-xxxx-xxxx-xxxx' }, Execution log $ intern-runner config=theintern/intern-sauce.js Listening on 0.0.0.0:9000 Starting tunnel... Using no proxy for connecting to Sauce Labs REST API. *********************

问题 Issue Trying to install a Firefox browser extension during remote execution of Selenium tests on Saucelabs. When executing the tests locally, the extension is installed and active in Firefox, but in remote execution on Saucelabs the extension does not appear in the list of installed extensions. Following the steps outlined in this Saucelabs support article. Setup Selenium.Support v2.48.2 or v2.49.0 Selenium.WebDriver v2.48.2 or v2.49.0 Windows 10 or 7 Firefox 43 C# test setup private static

问题 I am having some trouble with TestNG annotations, and I haven't found a good answer either on stackoverflow or in the testng documentation. What I'm trying to do is add a testng listener as well as parameters from a testng.xml file to a "test base" superclass. All testng tests will inherit the superclass. This will alleviate a lot of code redundancy in the testng test class files. But when I have the @Listeners and @Parameters annotation in the superclass, and not the class that contains the

问题 So -- I can, from my laptop do the following: testcafe "saucelabs:Chrome@70.0:Windows 10" tests/settings/users.js This will, connect to SauceLabs, to launch the test (or multiple tests, works either way), to hit back against our development server. (IP's have been whitelisted, it all works). I can also, of course, login to sauce labs, open a "live testing" browser and connect to this environment/login etc. Thus, the "SauceLabs =-> My environment" is fine. If I try to run a build on circleci

问题 I have a angular application for which I wrote e2e tests using protractor. I am running my tests on saucelabs. There is a small issue with my page for instance. If my browser is not maximized some of the css gets messed up ( i do plan on fixing this in the future), and this would definitely fail some of my test cases that I wrote. However if my browser is maximized everything is perfect. Now the issue is when I run my test on saucelabs even though the browser looks maximized (according to

问题 I've been dealing to try to automate against Mobile my protractor tests. I've read most of the blogs around the web, I reached this one which is the "official" for Appium with Saucelabs: https://docs.saucelabs.com/tutorials/appium/#mobile-web-application I followed instructions there, and configured my config.js file as this var testName = 'Testing'; //Change Project's name here in order to be identified in BrowserStack exports.config = { // The address of a running selenium server.