baseUrl doesn't work in protractor.conf.js

[paulreeve]

Hey there,

I have a pretty rich suite of protractor tests now. I am now trying to automate my protractor tests across different environments. This obviously prompts a configuration challenge. I have coded my way around baseUrl not working by using the onPrepare option. This isn't ideal though. Is there any reason my tests don't automatically prefix the baseUrl to my relative paths when doing a ptor.driver.get('/myState')?

Thanks in advance.

[manevpe]

Why don't you pass the baseUrl through the command line like so "--baseUrl=https://dev_env.my_site.com/#/" ?

[paulreeve]

Hey, yeah good suggestion. I thought about that. I'm using the protractor grunt runner and it seems that the protractor.conf.js has no awareness of such parameters by the time it is run.
If baseUrl actually worked, it'd be perfect. I was more wondering what it would take to get that to work.I could debug protractor I guess and see where it fails.

[juliemr]

baseUrl is working in configuration files, it is used in Protractor's own test suite - the problem is that the base webdriver doesn't know about it. Since ptor.driver is accessing the base webdriver instance, there's no way for that to know about the baseUrl. You can do it manually:

ptor.driver.get(url.resolve(ptor.baseUrl, '/myState'));

[paulreeve]

Ah useful. Thanks. I never managed to get ptor.get to work. Some other people had the same issue (http://stackoverflow.com/questions/19391813/protractor-fails-to-find-angular/19568828#19568828).
I guess this would also solve the problem as I would not be referencing the base webdriver instance.