Wenn ich versuche, Winkelmesser e2e Test in Firefox auszuführen, startet es den Browser, aber meine Testskripte nicht ausgeführt werden.Ich bin nicht in der Lage, Winkelmesser Test in Firefox ausführen, aber in Chrom läuft es gut
Ich verwende Windows Server 2012 R2 Maschine mit Firefox-Version 46.0.1 und Selenium 2.53.0.
Es gibt mir die folgende Fehlermeldung:
Using FirefoxDriver directly...
[launcher] Running 1 instances of WebDriver
code\ui\dgui\node_modules\protractor\node_modules\selenium-webdriver\http\util.js:89
Error('Timed out waiting for the WebDriver server at ' + url));
^
Error: Timed out waiting for the WebDriver server at http://127.0.0.1:58798/hub
Ich versuchte, läuft Selenium Standalone
code\ui\dgui\node_modules\protractor\selenium>java -jar selenium-server-standalone-2.53.0.jar
09:37:21.214 INFO - Launching a standalone Selenium Server
09:37:21.285 INFO - Java: Oracle Corporation 25.91-b14
09:37:21.285 INFO - OS: Windows Server 2012 R2 6.3 amd64
09:37:21.293 INFO - v2.53.0, with Core v2.53.0. Built from revision 35ae25b
09:37:21.332 INFO - Driver class not found: com.opera.core.systems.OperaDriver
09:37:21.332 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered
09:37:21.336 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped:
registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform WIN8
09:37:21.336 INFO - Driver class not found: org.openqa.selenium.htmlunit.HtmlUnitDriver
09:37:21.336 INFO - Driver provider org.openqa.selenium.htmlunit.HtmlUnitDriver is not registered
09:37:21.434 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub
09:37:21.434 INFO - Selenium Server is up and running
ich npm run e2e
Befehl bin mit meinem Test auszuführen
meine Config-Datei:
exports.config = {
allScriptsTimeout: 30000,
suites: {
test Suit: 'e2e/TestSuites/Tests/*.js',
},
multiCapabilities: [
// We will want to eventually include the following options to split out tests to multiple instances
{'browserName': 'firefox'}
],
// only for firefox and chrome - IE will require using a selenium server
directConnect : true,
// make sure that the baseURL reflects the configuration of the web server
baseUrl: 'http://10.26.5.13:8000/',
framework: 'jasmine2',
jasmineNodeOpts: {
defaultTimeoutInterval: 30000
},
onPrepare: function() {
var jasmineReporters = require('jasmine-reporters');
browser.driver.manage().window().maximize();
return browser.getProcessedConfig().then(function(config) {
var browserName = config.capabilities.browserName;
var junitReporter = new jasmineReporters.JUnitXmlReporter({
consolidateAll: true,
savePath: 'tests/test-results',
// this will produce distinct xml files for each capability
filePrefix: browserName + '-xmloutput',
modifySuiteName: function(generatedSuiteName, suite) {
// this will produce distinct suite names for each capability,
// e.g. 'firefox.login tests' and 'chrome.login tests'
return browserName + '.' + generatedSuiteName;
}
});
jasmine.getEnv().addReporter(junitReporter);
});
},
resultJsonOutputFile: 'tests/test-results/output.json'
};
ist es, weil Selen Standalone läuft http://127.0.0.1: 4444/wd/Hub und Winkelmesser sucht WebDriver Server bei http://127.0.0.1:58798/hub – ssharma
wenn das so wie kann ich WebDriver Server-Standort in Protractor – ssharma
Meine config-Datei aktualisieren: multiCapabilities: [ {‘ browser ': 'firefox'}, // {' browser ': 'Chrom'} ], DirectConnect-: true, – ssharma