I think this is pretty close.
Right now, in one shell you run the chromedriver like;
grunt run:devChromeDriver:keepalive
And then set env vars for these parameters (running against cloud.elastic.co for example);
export SHIELD_ADMIN=elastic
export SHIELD_ADMIN_PASS=<your password here>
export SHIELD_KIBANA_USER=elastic
export SHIELD_KIBANA_USER_PASS=<your password here> (probably the same as above)
export TEST_UI_ES_HOSTNAME=7d5e38ac8bd3e6e8d4150e5e7f1a7410.us-east-1.aws.found.io
export TEST_UI_ES_PORT=9200
export TEST_UI_KIBANA_HOSTNAME=c0a34b0c406cf1752d5f1f47a8777d4a.us-east-1.aws.found.io
export TEST_UI_KIBANA_PROTOCOL=https
export TEST_UI_KIBANA_PORT=443
#$ env | grep -E '(TEST|SHIELD)' | sort
node_modules/intern/bin/intern-runner.js config=test/intern leaveRemoteOpen
It's not all working yet. Our navigateToApp function doesn't think it worked because the browser doesn't show the port if its 443 (or 80 probably) and so it doesn't match what it thinks it should be. I'll work on that.
And you MUST run the Kibana automation using the correct 5.0 branch of kibana since we've already made changes in master that break the tests (like the timepicker selector).
I think this is pretty close.
Right now, in one shell you run the chromedriver like;
grunt run:devChromeDriver:keepaliveAnd then set env vars for these parameters (running against cloud.elastic.co for example);
It's not all working yet. Our
navigateToAppfunction doesn't think it worked because the browser doesn't show the port if its 443 (or 80 probably) and so it doesn't match what it thinks it should be. I'll work on that.And you MUST run the Kibana automation using the correct 5.0 branch of kibana since we've already made changes in master that break the tests (like the timepicker selector).