I ran the jx compliance tests, and now when I run the command to get the results, I get this :
FAILED BeforeSuite Kubernetes e2e suite
I really don't know what I'm meant to do with that information, it doesn't really seem to tell me what I can do to remedy the situation.
Related
I've developed a framework which runs selenium tests with no problem on my local computer.
I also have developed a pipeline on Bamboo to execute those tests. It does, problem is I have no chrome browser installed on bamboo and I get the error saying "There is no chrome binary" obviously. There is no chance to install anything on bamboo, so I need to run these tests with no browser (also headless).
I've checked this: https://github.com/browserless/chrome
Sounds good to what I want to achieve but I don't know how to do it.
Do I need to run docker by command and then point my driver to the port or what?
Can anyone shed some light? I pretty lost and there are not much examples (or I don't know how to find them)
Thanks!!
Currently, I have an automation framework that consists of the following stack:
Python
Pytest Framework (and pytest-xdist parallel mechanized)
Selenium
Allure report system
Jenkins
I'm going to add a docker containerization system as well, to run tests using it on a windows server.
I'm running my tests using pytest's internal parallel run (pytest-xdist) functionality using 'workers'
the run command looks like this:
os.system("pytest -v -s --alluredir="'C:\AllureReports\Data'" --html=report.html --developer=dmitriy --timeout=60 --self-contained-html --dist=loadfile -n=3 -m=regression")
As you can see '-n=3' is the number of 'nodes' that the suite will be executed. In other words, the regression suite will run in a parallel run of 3 nodes.
Can you tell me if it is possible to avoid using Selenium-Grid mechanized, and use this pytest's internal parallel run system instead -> pytest-xdist, and how?
Will appreciate relevant technical articles or explanations of how it can be done.
I have gone over this question - pytest-xdist vs selenium hub
but got only a really overview impression which is not enough
I need to integrate my protractor scripts on Jenkins . My code is in Bit bucket and i configured the details on my project in Jenkins.
My Jenkins server is on Linux so i have used Execute shell .
Below are the steps i mentioned in execute shell in order to run.
npm install
webdriver-manager update
webdriver-manager start
protractor conf.js
Initialising WebDriverServlet
20:23:34.444 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444
Selenium server is up and running but it got stuck there and unable to execute next step.
.................................
I have also tried executing
npm install
protractor conf.js
by commenting selenium address on conf.js
For which m getting the below error
I/launcher - Running 1 instances of WebDriver
[20:02:30] I/local - Starting selenium standalone server...
[20:02:32] I/local - Selenium standalone server started at .........
Unable to create new service: ChromeDriverService
I need help on how to run the scripts on jenkins. Any help will be appreciated. Thanks in adavnce
I can tell what your problem is, but nor ready to provide a solution
so when you run webdriver-manager start it starts a process. When that process is running, you can't run another one, until you exit this one. When you do it manually, you're using 2 terminal windows, right?
so theoretical solution - you need to look up how to run commands in parallel on linux and this page has many https://www.slashroot.in/how-run-multiple-commands-parallel-linux
Another option that I'm using is to set directConnect: true in config file. This way you don't even need to start a server, protractor will do it for you. And honestly I don't know why not everyone is using it...
I am trying to run some tests in Travis CI using Docker (and docker-compose).
A search on "run docker in Travis" does yield several how-to-do results, but none of these seem to be running remotely on Travis CI (travis-ci.com), instead I assume are on local Travis.
The answers to the closest question I found, Can travis-ci run docker? , have not helped me so far.
The problem I encounter is that Travis CI runs Ubuntu 12.04 on an outdated kernel and installing Docker requires updating the kernel and rebooting - but 'sudo reboot' will cause the virtual machine to be destroyed and leads to an infinite cycle of [install kernel -> reboot -> install_kernel ...]
Just wanted to drop in a quick note that Docker support for Travis CI is now official: http://blog.travis-ci.com/2015-08-19-using-docker-on-travis-ci/
It's support Docker and Docker-compose.
https://github.com/moul/travis-docker claims support for Docker in Travis. It apparently uses User Mode Linux to achieve this. I haven't tried this yet.
I know it does not help you with travis-ci but I build my docker image on circle-ci. Also Circle-CI just upgraded to docker 1.6.2.
My build file can be found here:
https://github.com/blacklabelops/jenkins/blob/master/circle.yml
I am unable to run a docker container in a Travis continuous integration job.
https://travis-ci.org/buildbot/buildbot/builds/36547150
pkg/installation_tests/testall.sh
Segmentation Fault or Critical Error encountered. Dumping core and aborting.
pkg/installation_tests/testall.sh: line 16: 7343 Aborted docker build $dir
make: *** [docker_install_tests] Error 1
My guess is that there are missing kernel stuff in the travis workers, but it is difficult to tell.
As of August 2015, Travis CI officially supports Docker.
See Using Docker in Builds for usage details.
Sorry, while we currently support Docker as an alternative virtualization platform, we don't directly support running Docker inside of the current setup, at least directly.
However, there are workarounds that could help you there from the fine folks at Docker themselves: https://github.com/jpetazzo/sekexe
In case you have not yet solved the problem yourself, here https://github.com/rocker-org/rocker/blob/56cb59cc262e9d2c02f9e11cfacab65f0b659c5f/.travis.yml#L10-L24 you can find a practical example of the solution suggested above.