简体   繁体   中英

protractor in connection with selenium keeps connecting to localhost

I have a setup of my angular-app and a separate selenium server as docker-compose setup

my protractor setting looks like this

const { SpecReporter } = require('jasmine-spec-reporter');

exports.config = {
    allScriptsTimeout: 11000,
    specs: [
        './e2e/**/*.e2e-spec.ts'
    ],
    capabilities: {
        'browserName': 'chrome'
    },

    directConnect: false,
    baseUrl: 'http://user-frontend:4200/',
    seleniumAddress: 'http://selenium:4444/wd/hub',
    framework: 'jasmine',
    jasmineNodeOpts: {
        showColors: true,
        defaultTimeoutInterval: 30000,
        print: function() {}
    },
    onPrepare() {
        require('ts-node').register({
            project: 'e2e/tsconfig.e2e.json'
        });
        jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
    }
};

now I run the command to run the end2end tests using protractor:

ng e2e --no-serve

All my tests are failing, and when I debug the selenium server and take screenshots, I see it is trying to connect to itself (localhost) instead of back to the application host baseUrl: 'http://user-frontend:4200/',

在此处输入图片说明

any Idea what I am doing wrong here?

您确定未在其他位置设置browser.baseUrl (或browser.get() )吗?

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM