AngularJs Protractor Html Reporter Fails Config Parser - angularjs

I am trying to use protractor html screenshot reporter but it's failing to require in the the config file. Here's my config:
//Configuration for Protractor
var HtmlReporter = require('protractor-html-screenshot-reporter');
var reporter = new HtmlReporter({
baseDirectory: '/screenshots',
takeScreeenShotOnlyForFailedSpecs: true
});
exports.config = {
//Address of Selenium server
seleniumAddress: 'http://localhost:4444/wd/hub',
//framework: 'jasmine2',
chromeOnly: false,
multiCapabilities: [
{'browserName': 'chrome'}
],
//URL of the application
baseUrl: 'http://localhost:80',
cache: false,
//Spec pattern
specs: ['**/specs/*-spec.js'],
onPrepare: function () {
//browser.driver.manage().window().maximize();
browser.driver.manage().window().setSize(480, 800);
browser.driver.manage().window().setPosition(400, 100);
jasmine.getEnv().addReporter(reporter);
},
//Options passed to Jasmine-node
jasmineNodeOpts: {
includeStackTrace: true,
showColors: true,
defaultTimeoutInterval: 30000,
isVerbose: true,
}
};
I have both protractor and the protractor html screenshot report installed globally . Here's the error protractor is throwing:
[13:48:23] E/configParser - error code: 105
[13:48:23] E/configParser - description: failed loading configuration file protractor-config.js
Any help would be most helpful!!
UPDATE:
I moved to the require call inside the onPrepare in the config and I getting the proper error:
[14:27:15] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[14:27:15] I/launcher - Running 1 instances of WebDriver
[14:27:18] E/launcher - Error: Error: Cannot find module 'protractor-html-screenshot-reporter'
Seems like it can't find the node module. Anyone else seeing this issue?
UPDATE2:
So, I think I found my problem. I was installing like this:
npm install -g protractor-html-screenshot-reporter
Which seems to be the cause the fail. Installing with this command:
npm install protractor-html-screenshot-reporter --save-dev
Works! For whatever reason installing globally doesn't work but installing locally does, which is a bit of a downer :( If anyone knows how to get this to work with the screenshot reporter installed globally let me know how :)

Related

e2e testin with jasmine protractor "no specs found"

I'm new testing with protractor, but I cant run my tests.
My protractor.config.js:
exports.config = {
allScriptsTimeout: 99999,
// The address of a running selenium server.
seleniumAddress: 'http://localhost:4444/wd/hub',
// Capabilities to be passed to the webdriver instance.
capabilities: {
browserName: 'chrome'
},
baseUrl: 'http://localhost:8080/',
framework: 'jasmine',
// Spec patterns are relative to the current working directly when
// protractor is called.
specs: ['.src/test/e2e/login.e2e.spec.js'],
// Options to be passed to Jasmine-node.
jasmineNodeOpts: {
showColors: true,
defaultTimeoutInterval: 30000,
isVerbose: true,
includeStackTrace: true
}
};
and this is the test I'm trying to run:
'use strict';
describe('my app', function() {
beforeEach(function () {
browser.get('index.html');
});
it('should automatically redirect to / when location hash is empty', function() {
expect(browser.getLocationAbsUrl()).toMatch("/");
});
});
And this is the error I get:
I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[13:20:49] I/launcher - Running 1 instances of WebDriver
Started
No specs found
Finished in 0.001 seconds
[13:20:50] I/launcher - 0 instance(s) of WebDriver still running
[13:20:50] I/launcher - chrome #01 passed
[13:20:50] The following tasks did not complete: e2e
[13:20:50] Did you forget to signal async completion?
I'm running webdriver-manager and my app server. My jasmine version is: 2.5.2
and my protractor version is:
4.0.9
Any idea of what I'm doing wrong??
Thanks!!!
I realized what was my problem (thanks to the comments that helped me to realize).
I was running my test with a gulp task I made:
function e2e() {
gulp.src(["/src/test/*.js"]).pipe(protractor({
configFile: "conf/protractor.config.js",
args: ['--baseUrl', 'http://localhost8080']
})).on('error', function (e) {
throw e;
});
}
I dont know why this: gulp.src(["/src/test/*.js"])wasnt getting to acces to my test files, so I changed it for: gulp.src(["src/test/e2e/login.e2e.spec.js"])
I know its not the best solution,but enough to survive...

Timeout error after adding untrackOutstandingTimeouts:true in protractor conf

My protractor conf looks like this:
exports.config = {
seleniumServerJar: "../node_modules/protractor/selenium/selenium-server-standalone-2.51.0.jar",
seleniumPort: 4444,
baseUrl: baseUrl,
specs: specs,
untrackOutstandingTimeouts:true,
jasmineNodeOpts: {
showColors: true,
defaultTimeoutInterval: 3600000
},
framework: "jasmine2"
}
I am trying perform action on angular page but fails with error -
Failed: Timed out waiting for Protractor to synchronize with the page after 150 seconds.
Please see https://github.com/angular/protractor/blob/master/docs/faq.md.
The following tasks were pending:
- $http: /api/v1/query/tail/242ac110002-8/1h?t=1456925874600
I have added untrackOutstandingTimeouts:true in protractor conf, still I am getting above error.
Protractor Version - 3.1.1
Node version - 4.3.1
Selenium-webdriver - 2.51.0
Thanks in advance!
Able to solve above problem using browser.ignoreSynchronization
browser.get('/');
browser.ignoreSynchronization=true;
//Go to page where $http and $timeout is added
//Perform any action, steps here
browser.sleep(5000); //This can be replace with wait condition
browser.ignoresynchronization=false

protractor "ERROR - Unable to start a WebDriver session"

I have some it tests on my single-page-app written in angular.
the tests are in protractor.
they ran during the build before, but now that I moved all of them to a branch something got broken and when I run the tests I'm getting:
Running "protractor:normal" (protractor) task
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://172.31.9.226:23730/wd/hub
ERROR - Unable to start a WebDriver session.
c:\projects\blog-manager\node_modules\protractor\node_modules\selenium- webdriver\lib\atoms\error.js:113
var template = new Error(this.message);
^
Warning: Protractor test(s) failed. Exit code: 1 Use --force to continue.
Aborted due to warnings.
Process finished with exit code 6
the conf file is as follows:
'use strict';
module.exports.config = {
allScriptsTimeout: 60000,
baseUrl: 'http://localhost:9000/',
specs: [
process.cwd() + '/test/spec/e2e/**/*.js'//,
// process.cwd() + '/test/e2e/spec/**/*.js'
],
framework: 'jasmine',
capabilities: {
browserName: 'chrome',
"chromeOptions": {
binary: "C:/Program Files (x86)/Google/Chrome/Application/chrome.exe",
args: [],
extensions: [],
}
},
onPrepare: function () {
// Disable animations so e2e tests run more quickly
var disableNgAnimate = function () {
angular.module('disableNgAnimate', []).run(function ($animate) {
$animate.enabled(false);
});
};
browser.addMockModule('disableNgAnimate', disableNgAnimate);
// Store the name of the browser that's currently being used.
browser.getCapabilities().then(function (caps) {
browser.params.browser = caps.get('browserName');
});
},
jasmineNodeOpts: {
defaultTimeoutInterval: 300000
}
};
any suggestions on how to solve this would be much appreciated.
Thanks!
According to alecxe's answer it's chrome binary issue which can be solved by installing chrome in same place as chromedriver expects to be or specifying the executable path to the binary settings.
capabilities: {
"browserName": "chrome",
"chromeOptions": {
binary: "D:/Program Files/Chrome/chrome.exe",
args: [],
extensions: [],
}
},
See his answer here
Even though you are setting the executable path correctly it seems little off to me binary: "C:/Program Files (x86)/Google/Chrome/Application/chrome.exe",
Is this correct?
Alternatively, I would try this

Setting Protractor baseUrl dynamically

In our end-to-end tests, we dynamically generate the URL endpoint for us to test against. In our Protractor configuration, I was hoping to use beforeLaunch or onPrepare to retrieve the URL endpoint and set it to baseUrl before running our tests. However it seems no matter what I try, Protractor runs tests with the wrong baseUrl, not the one I set in beforeLaunch or onPrepare.
We're using Protractor version 1.4.0. This is a simple configuration file demonstrating the issue:
exports.config =
directConnect: true
framework: 'jasmine'
jasmineNodeOpts:
isVerbose: true
showColors: true
includeStackTrace: true
suites:
login: 'login/**/*.coffee'
full: '**/*.coffee'
capabilities:
browserName: 'chrome'
beforeLaunch: ->
setBaseUrl 'https://test-url.com'
onPrepare: ->
setBaseUrl 'https://test-url.com'
setBaseUrl = (baseUrl) ->
exports.config.baseUrl = baseUrl
Thanks for the help!
It looks like calling browser.baseUrl = "https://test-url.com" does the trick in onPrepare

Protractor - Cucumber : Annoying ECONNREFUSED Errors while working as expected

I'm trying to integrate Cucumber with protractor, While the setup is working as expected (the test fail and succeed normally), I'm getting annoying ECONNREFUSED errors that makes my feedback unreadable.
Question 1: What't ECONNREFUSED's error exact meaning? I don't really understand the feedback and I couldn't find good documentation for it.
Question 2: What could be the problem with my setup? Is my setup proper?
Question 3: Has anyone run BDD tests in vagrant box with cucumber over protractor? Example code please :)
Dependencies
npm i protractor cucumber selenium-webdriver chai chai-as-promised express grunt-protractor-runner protractor-cucumber --save-dev
As you see I'm running my commands via grunt inside a vagrant box. The vagrant box has only firefox, I'm not sure if that's a problem, protractor was running just fine before.
Terminal Feedback
[vagrant#vagrant web-src]$ grunt protractor:singlerun
Running "protractor:singlerun" (protractor) task
Using the selenium server at http://localhost:4444/wd/hub
Feature: Blog
As a user
I want to visit blog
So that I can stay informed about a topic
Scenario: A disclaimer scenario # tests/e2e/cucumber/features/Blog.feature:6
/var/www/miyagi/web-src/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:131
var session = webdriver.promise.controlFlow().execute(function() {
^
Error: ECONNREFUSED connect ECONNREFUSED
at <anonymous>
at <anonymous>
at <anonymous>
at <anonymous>
at <anonymous>
at <anonymous>
==== async task ====
WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (/var/www/miyagi/web-src/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:131:49)
at Function.webdriver.WebDriver.createSession (/var/www/miyagi/web-src/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:111:30)
at Builder.build (/var/www/miyagi/web-src/node_modules/protractor/node_modules/selenium-webdriver/builder.js:106:20)
at HostedDriverProvider.getDriver (/var/www/miyagi/web-src/node_modules/protractor/lib/driverProviders/hosted.js:63:9)
at /var/www/miyagi/web-src/node_modules/protractor/lib/runner.js:241:41
at _fulfilled (/var/www/miyagi/web-src/node_modules/protractor/node_modules/q/q.js:797:54)
at self.promiseDispatch.done (/var/www/miyagi/web-src/node_modules/protractor/node_modules/q/q.js:826:30)
at Promise.promise.promiseDispatch (/var/www/miyagi/web-src/node_modules/protractor/node_modules/q/q.js:759:13)
at /var/www/miyagi/web-src/node_modules/protractor/node_modules/q/q.js:573:44
>>
>> Test failed but keep the grunt process alive.
Done, without errors.
[vagrant#vagrant web-src]$
Protractor Config
// conf.js
exports.config = {
seleniumAddress: 'http://localhost:4444/wd/hub',
specs: ['../cucumber/features/*.feature'],
multiCapabilities: [{
browserName: 'firefox'
}],
onPrepare: function() {
var width = 1024;
var height = 600;
browser.driver.manage().window().setSize(width, height);
// implicit and page load timeouts
browser.manage().timeouts().pageLoadTimeout(40000);
browser.manage().timeouts().implicitlyWait(25000);
// for non-angular page
browser.ignoreSynchronization = true;
},
framework: 'cucumber',
cucumberOpts: {
require: '../cucumber/features/*.steps.js',
format: 'pretty'
}
};
Grunt task
protractor: {
options: {
configFile: '<%=tests %>/e2e/protractor/config.js', // Default config file
noColor: false, // If true, protractor will not use colors in its output
keepAlive: true
},
auto : {
keepAlive: true // If false, the grunt process stops when the test fails.
},
singlerun: {}
},
Feature
Feature: Blog
As a user
I want to visit blog
So that I can stay informed about a topic
Scenario: A disclaimer scenario
Given I visit blog
Then I should see a disclaimer
Steps
//http://chaijs.com/
var chai = require('chai');
//https://github.com/domenic/chai-as-promised/
var chaiAsPromised = require('chai-as-promised');
chai.use(chaiAsPromised);
var expect = chai.expect;
module.exports = function() {
var url = 'http://dev.com/search',
searched = url + '#/?q=food&page_number=1&sort=relevance',
driver,
resultsA, resultsB, resultsC,
page,
site;
this.Given(/^I visit blog$/, function(callback) {
browser.get(url);
driver = browser.driver;
browser.getTitle()
.then(function ( title ) {
expect(browser.getTitle()).to.eventually.equal(arg1).and.notify(callback);
});
});
this.Then(/^I should see a disclaimer$/, function(callback) {
element( by.css ( '.disclaimer' ) )
.isDisplayed()
.then(function (el) {
expect(el).to.have.length(1);
callback();
});
});
};
Cheers
You never mentioned setting up a local selenium server. Did you forget it?
./node_modules/protractor/bin/webdriver-manager update
./node_modules/protractor/bin/webdriver-manager start
Just let that run in its own terminal window, and try running your tests again.
Any chance you already have another instance of webdriver running? Or a firewall that is blocking the connection?
This is a working example that I found. However it is in .coffee
https://github.com/whyvez/angular-cucumber-example

Resources