Karma not running a specific test file. Instead, it run all test files - karma-jasmine

According to https://stackoverflow.com/a/45350941/4148175 part A I should be able to run a specific test file by "karma start --grep my-test-file.js". I tried but it run two test files I have.
According to https://stackoverflow.com/a/29151264/4148175 I should firstly start karma and then run the specific file but after I started karma I also have my two files triggered and when I try run the spesific file I get that the port isn't answering.
As far as I understood, I must setup autoWatch: true and singleRun: true and it is that way in my karma.conf.js
Console:
# karma start
03 07 2019 14:02:29.713:WARN [filelist]: Pattern "C:/_d/samples/../node_modules/#webcomponents/webcomponentsjs/webcomponents-bundle.js" does not match any file.
03 07 2019 14:02:29.730:INFO [karma-server]: Karma v4.1.0 server started at http://0.0.0.0:9876/
03 07 2019 14:02:29.731:INFO [launcher]: Launching browsers Chrome, Firefox with concurrency unlimited
03 07 2019 14:02:29.739:INFO [launcher]: Starting browser Chrome
03 07 2019 14:02:29.754:INFO [launcher]: Starting browser Firefox
03 07 2019 14:02:35.891:INFO [Chrome 75.0.3770 (Windows 10.0.0)]: Connected on socket R657DrSW7GAKGkPxAAAA with id 98561767
**** certain test from a file
**** another test from other file
Chrome 75.0.3770 (Windows 10.0.0): Executed 6 of 6 SUCCESS (0.096 secs / 0.01 secs)
Firefox 67.0.0 (Windows 10.0.0): Executed 6 of 6 SUCCESS (0.073 secs / 0.017 secs)
TOTAL: 12 SUCCESS
mycompany#DESKTOPF C:\_d\samples\how-to-test-web-component
# karma run -- --grep=text.component.test.js
03 07 2019 14:03:02.469:ERROR [runner]: There is no server listening on port 9876
Karma.conf.js
module.exports = function(config) {
config.set({
basePath: "",
frameworks: ["jasmine"],
files: [
"node_modules/#webcomponents/webcomponentsjs/webcomponents-bundle.js",
{ pattern: "**/*.test.js", type: "module", included: true },
{ pattern: "**/*.js", type: "module", included: false }
],
exclude: [],
preprocessors: {},
reporters: ["spec"],
port: 9876,
colors: true,
logLevel: config.LOG_INFO,
autoWatch: true,
browsers: ["Chrome", "Firefox"],
singleRun: true,
concurrency: Infinity
});
};
To summarize: what I am doing wrong or missing in order to test via karma just the tests found in a specific file?

Related

Getting error in jenkins with test coverage after upgrading from Angular 9 to Angular14

Can someone please point me how to debug this issue further. Get below error when jenkins job is run and the application is one Angular 14.
[32m13 10 2022 23:01:01.881:INFO [karma-server]: [39mKarma v6.4.1 server started at http://localhost:9876/
[32m13 10 2022 23:01:01.884:INFO [launcher]: [39mLaunching browsers ChromeHeadless with concurrency unlimited
[32m13 10 2022 23:01:01.887:INFO [launcher]: [39mStarting browser ChromeHeadless
[32m13 10 2022 23:01:03.202:INFO [Chrome Headless 63.0.3239.132 (Linux x86_64)]: [39mConnected on socket ajz1GfKScPy5uAgXAAAB with id 803388
Chrome Headless 63.0.3239.132 (Linux x86_64): Executed 0 of 0[32m SUCCESS[39m (0 secs / 0 secs)
[1A[2K[31mChrome Headless 63.0.3239.132 (Linux x86_64) ERROR[39m
An error was thrown in afterAll
Uncaught SyntaxError: Unexpected token {
SyntaxError: Unexpected token {
Uncaught SyntaxError: Unexpected token .
SyntaxError: Unexpected token .

Making Dockerized Flask server concurrent

I have a Flask server that I'm running on AWS Fargate. My task has 2 vCPUs and 8 GB of memory. My server is only able to respond to one request at a time. If I run 2 API requests at the same, each that takes 7 seconds, the first request will take 7 seconds to return and the second will take 14 seconds to return.
This is my Docker file (using this repo):
FROM tiangolo/uwsgi-nginx-flask:python3.7
COPY ./requirements.txt requirements.txt
RUN pip3 install --no-cache-dir -r requirements.txt
RUN python3 -m spacy download en
RUN apt-get update
RUN apt-get install wkhtmltopdf -y
RUN apt-get install poppler-utils -y
RUN apt-get install xvfb -y
COPY ./ /app
I have the following config file:
[uwsgi]
module = main
callable = app
enable-threads = true
These are my logs when I start the server:
Checking for script in /app/prestart.sh
Running script /app/prestart.sh
Running inside /app/prestart.sh, you could add migrations to this file, e.g.:
#! /usr/bin/env bash
# Let the DB start
sleep 10;
# Run migrations
alembic upgrade head
/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2019-10-05 06:29:53,438 CRIT Supervisor running as root (no user in config file)
2019-10-05 06:29:53,438 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2019-10-05 06:29:53,446 INFO RPC interface 'supervisor' initialized
2019-10-05 06:29:53,446 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-10-05 06:29:53,446 INFO supervisord started with pid 1
2019-10-05 06:29:54,448 INFO spawned: 'nginx' with pid 9
2019-10-05 06:29:54,450 INFO spawned: 'uwsgi' with pid 10
[uWSGI] getting INI configuration from /app/uwsgi.ini
[uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
;uWSGI instance configuration
[uwsgi]
cheaper = 2
processes = 16
ini = /app/uwsgi.ini
module = main
callable = app
enable-threads = true
ini = /etc/uwsgi/uwsgi.ini
socket = /tmp/uwsgi.sock
chown-socket = nginx:nginx
chmod-socket = 664
hook-master-start = unix_signal:15 gracefully_kill_them_all
need-app = true
die-on-term = true
show-config = true
;end of configuration
*** Starting uWSGI 2.0.18 (64bit) on [Sat Oct 5 06:29:54 2019] ***
compiled with version: 6.3.0 20170516 on 09 August 2019 03:11:53
os: Linux-4.14.138-114.102.amzn2.x86_64 #1 SMP Thu Aug 15 15:29:58 UTC 2019
nodename: ip-10-0-1-217.ec2.internal
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 2
current working directory: /app
detected binary path: /usr/local/bin/uwsgi
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Python version: 3.7.4 (default, Jul 13 2019, 14:20:24) [GCC 6.3.0 20170516]
Python main interpreter initialized at 0x55e1e2b181a0
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 1239640 bytes (1210 KB) for 16 cores
*** Operational MODE: preforking ***
2019-10-05 06:29:55,483 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-05 06:29:55,484 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Tests fail immediately with unknown error: DevToolsActivePort file doesn't exist when running Selenium grid through systemd

I've been trying to change the way I start the Selenium grid service from a shell script in .rclocal to a systemd service, but it is not working. The script is this:
#!/bin/bash
java -jar /opt/selenium-server-standalone.jar -role hub -hubConfig hubconfig.json
xvfb-run --server-args="-screen 0 2048x1536x24" java -jar /opt/selenium-server-standalone.jar -role
node -nodeConfig nodeconfig.json
I created two different services as follows:
(Stackoverflow won't let me put the contents of the services as it says it is not properly formated)
The services are starting correctly:
selenium-hub
● selenium-hub.service - Selenium service
Loaded: loaded (/etc/systemd/system/selenium-hub.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2019-10-01 15:53:10 UTC; 2min 41s ago
Main PID: 23803 (java)
CGroup: /system.slice/selenium-hub.service
└─23803 /bin/java -jar /opt/selenium-server-standalone.jar -role hub -hubConfig /home/selenium/hubconfig.json
Oct 01 15:53:12 vm java[23803]: 15:53:12.163 INFO - Selenium build info: version: '3.9.1', revision: '63f7b50'
Oct 01 15:53:12 vm java[23803]: 15:53:12.164 INFO - Launching Selenium Grid hub on port 4444
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.384:INFO::main: Logging initialized #2790ms to org.seleniumhq.jetty9.util.log.StdErrLog
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.492:INFO:osjs.Server:main: jetty-9.4.7.v20170914, build timestamp: 2017-11-21T21:27:37Z, git hash: 82b8fb23f757335bb3329d540ce37a2a2615f0a8
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.524:INFO:osjs.session:main: DefaultSessionIdManager workerName=node0
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.524:INFO:osjs.session:main: No SessionScavenger set, using defaults
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.529:INFO:osjs.session:main: Scavenging every 660000ms
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.538:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler#60704c{/,null,AVAILABLE}
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.562:INFO:osjs.AbstractConnector:main: Started ServerConnector#1fe20588{HTTP/1.1,[http/1.1]}{0.0.0.0:4444}
Oct 01 15:53:13 vm java[23803]: 2019-10-01 15:53:13.562:INFO:osjs.Server:main: Started #2968ms
Oct 01 15:53:13 vm java[23803]: 15:53:13.562 INFO - Selenium Grid hub is up and running
Oct 01 15:53:13 vm java[23803]: 15:53:13.562 INFO - Nodes should register to http://1.2.3.4:4444/grid/register/
Oct 01 15:53:13 vm java[23803]: 15:53:13.562 INFO - Clients should connect to http://1.2.3.4:4444/wd/hub
Oct 01 15:53:14 vm java[23803]: 15:53:14.797 INFO - Registered a node http://1.2.3.4:5555
selenium-node:
● selenium-node.service - Selenium nodes
Loaded: loaded (/etc/systemd/system/selenium-node.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2019-10-01 15:53:10 UTC; 6min ago
Main PID: 23813 (xvfb-run)
CGroup: /system.slice/selenium-node.service
├─23813 /bin/sh /bin/xvfb-run --server-args="-screen 0 2048x1536x24" java -jar /opt/selenium-server-standalone.jar -role node -nodeConfig /home/selenium/nodeconfig.json
├─23856 java -jar /opt/selenium-server-standalone.jar -role node -nodeConfig /home/selenium/nodeconfig.json
├─24326 /usr/local/bin/chromedriver --port=1713
├─24327 /usr/local/bin/chromedriver --port=26741
├─24328 /usr/local/bin/chromedriver --port=20065
├─24329 /usr/local/bin/chromedriver --port=6459
├─24331 /usr/local/bin/chromedriver --port=15872
├─24332 /usr/local/bin/chromedriver --port=29475
├─24333 /usr/local/bin/chromedriver --port=30216
├─24334 /usr/local/bin/chromedriver --port=6955
├─24558 /usr/local/bin/chromedriver --port=2425
├─24559 /usr/local/bin/chromedriver --port=19304
├─24560 /usr/local/bin/chromedriver --port=12150
├─24561 /usr/local/bin/chromedriver --port=26147
├─24562 /usr/local/bin/chromedriver --port=16545
├─24570 /usr/local/bin/chromedriver --port=12780
├─24602 /usr/local/bin/chromedriver --port=10959
├─24603 /usr/local/bin/chromedriver --port=8970
├─24753 /usr/local/bin/chromedriver --port=13438
├─24754 /usr/local/bin/chromedriver --port=15725
└─24772 /usr/local/bin/chromedriver --port=28829
Oct 01 15:55:19 vm xvfb-run[23813]: Starting ChromeDriver 77.0.3865.40 (f484704e052e0b556f8030b65b953dce96503217-refs/branch-heads/3865#{#442}) on port 15725
Oct 01 15:55:19 vm xvfb-run[23813]: Only local connections are allowed.
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.112 INFO - /session: Executing POST on /session (handler: BeginSession)
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.113 INFO - Capabilities are: Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.114 INFO - Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm-usage, window-siz
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.115 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.BeginSession#53702c02
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.115 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.BeginSession#4ae12041
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.116 INFO - /session: Executing POST on /session (handler: BeginSession)
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.117 INFO - Capabilities are: Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.118 INFO - Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm-usage, window-siz
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.118 INFO - /session: Executing POST on /session (handler: BeginSession)
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.120 INFO - Capabilities are: Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.120 INFO - Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm-usage, window-siz
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.121 INFO - /session: Executing POST on /session (handler: BeginSession)
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.123 INFO - Capabilities are: Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.123 INFO - Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm-usage, window-siz
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.124 INFO - /session: Executing POST on /session (handler: BeginSession)
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.139 INFO - Capabilities are: Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm
Oct 01 15:55:19 vm xvfb-run[23813]: 15:55:19.139 INFO - Capabilities {browserName: chrome, goog:chromeOptions: {args: [enable-automation, disable-infobars, disable-notifications, no-sandbox, --disable-dev-shm-usage, window-siz
Oct 01 15:55:19 vm xvfb-run[23813]: Starting ChromeDriver 77.0.3865.40 (f484704e052e0b556f8030b65b953dce96503217-refs/branch-heads/3865#{#442}) on port 26147
Oct 01 15:55:19 vm xvfb-run[23813]: Only local connections are allowed.
Oct 01 15:55:19 vm xvfb-run[23813]: Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
However all tests fails with the same error:
OpenQA.Selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.9.1', revision: '63f7b50', time: '2018-02-07T22:42:28.403Z'
The problem with DevToolsActivePort is derived from /dev/shm being too small and sometimes crashing the browser (https://stackoverflow.com/a/50642913/5364231, https://bugs.chromium.org/p/chromium/issues/detail?id=736452#c64) so I already added --disable-dev-shm-usage to the capabilities.
The problem, I think, resided in the service selenium-hub not being able to communicate with selenium-node. Any help is greatly appreciated.
Thumb rule
A common cause for Chrome to crash during startup is running Chrome as root user (administrator) on Linux. While it is possible to work around this issue by passing --no-sandbox flag when creating your WebDriver session, such a configuration is unsupported and highly discouraged. You need to configure your environment to run Chrome as a regular user instead.
This error message...
OpenQA.Selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.9.1', revision: '63f7b50', time: '2018-02-07T22:42:28.403Z'
...implies that the ChromeDriver was unable to initiate/spawn a new WebBrowser i.e. Chrome Browser session.
Your main issue is the incompatibility between the version of the binaries you are using as follows:
You are using the latest chromedriver=77.0
Presumably you are using chrome= 77.0.
Your Selenium Client version is 3.9.1 of 2018-02-07T22:42:28.403Z which is almost 1.5 years older.
So there is a clear mismatch between the Selenium Client v3.9.1 , ChromeDriver v77.0 and the Chrome Browser v77.0
Solution
Ensure that:
JDK is upgraded to current levels JDK 8u221.
Selenium is upgraded to current levels Version 3.141.59.
ChromeDriver is updated to current ChromeDriver v77.0 level.
Chrome is updated to current Chrome Version 77.0 level. (as per ChromeDriver v77.0 release notes)
Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
If your base Web Client version is too old, then uninstall it and install a recent GA and released version of Web Client.
Take a System Reboot.
Execute your #Test as non-root user.
Reference
You can find a couple of detailed discussions in:
org.openqa.selenium.WebDriverException: unknown error: DevToolsActivePort file doesn't exist while trying to initiate Chrome Browser
unknown error: DevToolsActivePort file doesn't exist error while executing Selenium UI test cases on ubuntu
Outro
Here is the link to the Sandbox story.
Sometimes this Happens when Chrome is Updated to newer version but driver binaries are still older. Make sure that Chrome browser and ChromeDriver have the same version

selenium-side-runner is failing for Chrome, ran through fine with Firefox

I'm trying out the command line runner of Selenium IDE selenium-side-runner on a .side file.
I can open this .side file in Selenium IDE and run the test suite, it can execute just fine, but when running the command line runner i get this error.
myuser#mycomputer [10:02:36] $ selenium-side-runner --debug selenium/seleniumtesting.side
debug: Could not load /Users/myuser/projects/selenium/.side.yml
debug: { capabilities: { browserName: 'chrome' },
params: {},
runId: 'a508a80619537b4ac9c18368857f84f2',
path: '/usr/local/lib/node_modules/',
server: undefined,
timeout: 15000,
baseUrl: undefined }
info: Running selenium/seleniumtesting.side
debug: jest worker args
debug: 0=--no-watchman, 1=--testMatch, 2={**/***/*.test.js,**/***.test.js}
debug: jest work opts
debug: cwd=/Users/myuser/projects/selenium/side-suite-seleniumtesting, stdio=inherit
FAIL ./BasicFullCheckoutflow.test.js (6.314s)
Basic Full Checkout flow
✕ 2. Add product to the cart (3035ms)
✓ 3. Checkout (1530ms)
● Basic Full Checkout flow › 2. Add product to the cart
StaleElementReferenceError: stale element reference: element is not attached to the page document
(Session info: chrome=73.0.3683.103)
(Driver info: chromedriver=2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.14.3 x86_64)
at Object.checkLegacyResponse (../../../../../../usr/local/lib/node_modules/selenium-side-runner/node_modules/selenium-webdriver/lib/error.js:585:15)
at parseHttpResponse (../../../../../../usr/local/lib/node_modules/selenium-side-runner/node_modules/selenium-webdriver/lib/http.js:533:13)
at Executor.execute (../../../../../../usr/local/lib/node_modules/selenium-side-runner/node_modules/selenium-webdriver/lib/http.js:468:26)
UPDATE: This is only happening for chrome webdriver, when i run with firefox it went through fine
selenium-side-runner -c "browserName=firefox" selenium/seleniumtesting.side
Try in headless mode with below options:-
selenium-side-runner -c "browserName=chrome chromeOptions.args=[headless,no-sandbox,disable-dev-shm-usage]" selenium/seleniumtesting.side

SeleniumHQ htmlSuite Run Plugin not clicking

I have a jenkins set up on a windows 2012 R2 server. We have added the plugin SeleniumHQ htmlsuite run plugin. We can execute the call manually on the server and everything runs fine. When we run it from Jenkins we get this error:
2017-07-19 10:41:46.603:INFO::main: Logging initialized #8197ms to org.seleniumhq.jetty9.util.log.StdErrLog
2017-07-19 10:41:46.666:INFO:osjs.Server:main: jetty-9.4.z-SNAPSHOT
2017-07-19 10:41:46.697:INFO:osjsh.ContextHandler:main: Started o.s.j.s.h.ContextHandler#fbd1f6{/tests,null,AVAILABLE}
2017-07-19 10:41:46.713:INFO:osjs.AbstractConnector:main: Started ServerConnector#1c0f706{HTTP/1.1,[http/1.1]}{0.0.0.0:39902}
2017-07-19 10:41:46.713:INFO:osjs.Server:main: Started #8313ms
Jul 19, 2017 10:41:48 AM org.openqa.selenium.server.htmlrunner.CoreTestCase run
INFO: |open | http://10.33.2.51/User/AccessSignin/Start | |
Jul 19, 2017 10:41:51 AM org.openqa.selenium.server.htmlrunner.CoreTestCase run
INFO: |type | id=UsernameField | badroutingtesting |
Jul 19, 2017 10:41:51 AM org.openqa.selenium.server.htmlrunner.CoreTestCase run
INFO: |clickAndWait | id=SubmitNext | |
Jul 19, 2017 10:41:52 AM org.openqa.selenium.server.htmlrunner.CoreTestCase run
INFO: |click | id=PasswordField | |
SmallTest.html
SmallTest</td></tr>
</tbody></table>
2017-07-19 10:41:53.057:INFO:osjs.AbstractConnector:main: Stopped ServerConnector#1c0f706{HTTP/1.1,[http/1.1]}{0.0.0.0:39902}
2017-07-19 10:41:53.057:INFO:osjsh.ContextHandler:main: Stopped o.s.j.s.h.ContextHandler#fbd1f6{/tests,null,UNAVAILABLE}
Jul 19, 2017 10:41:53 AM org.openqa.selenium.remote.ErrorCodes toStatus
INFO: HTTP Status: '404' -> incorrect JSON status mapping for 'unknown error' (500 expected)
Jul 19, 2017 10:41:54 AM org.openqa.selenium.server.htmlrunner.HTMLLauncher mainInt
WARNING: Test of browser failed: *firefox
org.openqa.selenium.WebDriverException: quit
It seems to me that it's not executing the click or it's not able to get to the next page. Same things happens for IE and Chrome. Could it be a permissions issue? Or is it a configuration with Jenkins? I'm a bit stumped