search

damirarh / damirscorner-utterances

utteranc.es comments for https://damirscorner.com
0 stars 0 forks source link

/blog/posts/20170414-ModifyProtractorConfigurationForBuildServer.html #48

Open damirarh opened 1 year ago

damirarh commented 1 year ago

Imported

URL: https://www.damirscorner.com/blog/posts/20170414-ModifyProtractorConfigurationForBuildServer.html

damirarh commented 1 year ago

Imported comment written by pahim on 2017-06-08T06:27:09

Hello Damir,
Your post is pretty helpful and I am understanding most of it. I have some scripts running locally. I am trying to setup builds in teamcity to run my scripts that are in svn. I am stuck at Build Step in team city. Can you please list the the steps i need to follow to complete the Build Step in team city? Thank you so much for your help.

damirarh commented 1 year ago

Imported comment written by Damir Arh on 2017-06-08T17:10:59

I defined an NPM script in package.json to run protractor:


"scripts": {
    "tc:e2e": "protractor protractor.conf.teamcity.js"
}

This allowed me to have protractor installed only locally and still run it easily with the following command line:


npm tun tc:e2e

This cun be run as a build step in TeamCity either with command line runner or with Node.js NPM runner that comes with TeamCity.Node plugin as described in this blogpost.

damirarh commented 1 year ago

Imported comment written by Krishan Kumar on 2017-07-23T17:16:16

Hi , Thanks for article . I got "Error message: browserName phantomjs is not supported with directConnect. " . I must be missing some thing i guess ? (though i read that direct connect only supports chrome and firefox).

I tried with directConnect : false , it worked using default selenium stanalone server configuration.

damirarh commented 1 year ago

Imported comment written by Damir Arh on 2017-07-24T17:51:45

You're not missing anything, direct connect indeed doesn't work with PhantomJS. There was a mistake in the first JavaScript snippet (which I now fixed). The value of directConnect must be set to false (it is already set to true in the original configuration file I linked to above the example).

There was no mistake in the JavaScript snippet at the end of the post. It already set directConnect to false correctly.