Docker Compose: starting script fails when some service of docker-compose project already running: Bug. Gutter grows abnormally when increasing line spacing in editor font settings: Cosmetics: IDEA-115916: Tab bug: graphical and not only. CTRL characters in terminal window can not type on MAC: Bug: IDEA-113214: Alt+Backspace, Ctrl+Right. Another maintenance release fixing two issues; the “Advanced Insert/Edit Link” button, and the “Image Map” button. R n Advanced Insert/Edit Link Button r n. There was an ajax function that did not make it into version 4.4 of WP Edit Pro. A bundle file is generated from a Compose v2 file using docker-compose bundle [-f docker-compose.yml]. It is then deployed using the docker deploy sub-command: docker deploy --file ownstack.dab. Let us try hands on creating a simple DAB for wordpress application.
Hi, thanks the feedback. The Selenium/Java search terms are standard commands, you can reed more about it in the Selenium wiki. There is “no” difference between conventional and parallel tests. The only trick is in the TestBase class in the BeforeMethode.
In parallel tests the setup of the Selenium Driver is differ from the conventional tests setup. And of course you need to start the Selenium grid in parallel tests. The testng.xml: To the testng.xml file you can write the test suits name. For example: You have a folder with name myFirstParallelTests and in the folder you have a couple of test files(Test01 and Test02).
The testng.xml file content will be the following: suite name=”My Test Suite” suite-files suite-file path=”./myFirstParallelTests.xml” /suite-files /suite Of course you need a myFirstParallelTests.xml file which contains the concrete test files path. For example: suite name=”Parallel test runs” parallel=”tests” thread-count=”2″ test name=”T01″ classes class name=”myFirstParallelTests.Test01″ /class /classes /test test name=”T02″ classes class name=”myFirstParallelTests.Test02″ /class /classes /test /suite Hope this helped. If you have any more questions, please feel free to ask! Regards, Istvan. Well, it’s tricky because there are different versions of webdriver too.
A concrete version of webdriver is support just a couple of versions of the browsers. For example the newest webdriver support the current version of Firefox (25.0), maybe the 26.0 and 27.0, backward maybe to 22.0. So if you want to test in Firefox 20 you will need another webdriver. The solution maybe to setup the different version of browsers in separate machines with the necessary webdrivers and you control the browsers with Selenium Grid. Hi Sunny, A basic tip: Try to think over your cases and make them separated as much as possible. Eg.: create new users at the start of the tests if you can, etc.
This could happen for lots of reasons: 1. Be sure that the resources on the site are always available.
Docker-compose Is Abnormally Slow Issue 1557 Docker/for-machine
The only problem I am having is with running the.xml When you say “To run the tests just right click to testng.xml, select Run As- TestNG Suite.”, I get stuck. Where should the.xml files be saved? Should they be saved to the Project?
Or to the package which I created? How exactly do I run it as a Suite? I have created suites before via Junit but that is the extent of what I know. Again, thank you for this write up. Thank you for your previous comments, I’ve found them very useful!
🙂 I am also new at Selenium and I would like to ask for a little help. What I would like to do is to create a class (named TestRunner.java) which I can tell which groups of @Test-s to run. I have 6 groups of them (now they are handled in separated classes), depending on what part of the web application they are executing.
Basically I have a smoke test, and 5 more tests for testing the several applications. So I need to be able to select which of these 6 tests I would like to run (sometimes all of them, sometimes 2 of them, etc.) and to run them in order (according to the priorities), in one browser which is started and ended by the TestRunner.java class. I hope it makes sense, I tried to be clear. 🙂 Thank you very much, Barbara. How to run the above test using Chrome. I tried with different settings but couldn’t. Help me is this regard.
Hey just follow up related to this. Overview – you may have multiple xml files which contain different entries for organizational purposes.
Then when you want to run everything, you will have a single testng.xml file which will contain entries to these individual xml suite files. For instance: When you run your testng.xml file it will run the individual xml suite files serially. You can’t run suites in parallel – correct? I believe this is what the original question was implying. Note: When SuiteA is called first, it will run as it is configured within it’s own xml file.
So if it specifies parallel execution it will run in parallel. When it completes its run, then SuiteB will run and it will run as it is configured within it’s xml file.
Hey, been researching and playing with parallel execution and wanted to get your insight. Focusing on TestNG implementation running against a Grid configuration. Parallel execution seems to be controlled by following areas: 1) TestNG, the testng,xml file and its use of the parallel=tests(etc) and thread-count=# suite attributes. So basically: If parallel=tests and you have a thread-count set to any value greater than 1 (default seems to be 5), it will attempt to kickoff that many tests at once (assuming there are that many entries in your xml file). 2) TestNG, the @DataProvider annotation and (parallel=true) setting Example: TestNG.xml contains reference to TestA and TestB. The xml file is set to parallel = tests and has a thread count of 5. So when I run the testng.xml file, 2 threads will kick off, one calling TestA and one calling TestB.
Now say TestA has a dataprovider with 5 rows of data and its configured as parallel=true. Say TestB isn’t data driven. Question: At this point does the thread count setting in testng.xml file affect how TestA runs? If not, I assume 5 TestA executions get kicked off in parallel (one for each data row) and sent to the Grid Hub, and oneTestB execution is sent to Hub. So 6 entries being sent in parallel to Hub – seem right or not? 3) Grid setup Then it just comes down to how many nodes and how their configured (OS/browser etc) to determine how many tests are actually running in parallel or are pooled. When it comes to running the test automation in parallel (Focusing on TestNG and Grid) that’s it – right?
Or are there other variables that I’m forgetting to take into account? Thanks for you expertise. Yes, it is possible. TestNG have the capability to run methods, classes and tests parallel.
However you will lose some benefits, like running your tests on different operating systems and machines all the same time. You don’t have to use Selenium Grid to run tests in parallel mode, if you don’t need these facilities and you want to run tests just on local machine. You can use any of WebDriver (InternetExplorerDriver, FirefoxDriver, ChromeDriver, HtmlDriver, OperaDriver) instead of RemoteWebDriver, if you want to ignore Selenium Grid. You don’t need to use DesiredCapabilites as well. Make sure that you configured correctly the attributes (parallel, thread-count) of element in.xml file.
The parallel attribute on the tag can take one of following values: “methods”, “tests”, “classes”, “instances”. Your tests, methods or classes should start in parallel. However specifically your example can’t run parallel with this configuration because you have just one method in one class. If you want to run test parallel with DataProvider annotation, you need to replace your to. The parallel attribute of element in file has no influence to your test with data provider.
Hi, You can simply use testng.xml to configure the number of parallel tests with parallel = true and thread-count=# while you do not use any @DataProvider annotation with parameter parallel = true. In that case Data Providers are run in their own thread pool, which is different from the thread pool used for test methods. You can also change the number of threads in data provider pool so the actual number of threads depend on the parameter thread-count=# and the number of threads from data provider pool. Otherwise there is one more thing that needs to highlight.
In testng.xml beside the parallel and thread-count there is one more parameter that has effect on the number of threads and this is parallel. It has 4 values (from testNG site: ): parallel=”methods”: TestNG will run all your test methods in separate threads. Dependent methods will also run in separate threads but they will respect the order that you specified. Parallel=”tests”: TestNG will run all the methods in the same tag in the same thread, but each tag will be in a separate thread. This allows you to group all your classes that are not thread safe in the same and guarantee they will all run in the same thread while taking advantage of TestNG using as many threads as possible to run your tests.
Parallel=”classes”: TestNG will run all the methods in the same class in the same thread, but each class will be run in a separate thread. Parallel=”instances”: TestNG will run all the methods in the same instance in the same thread, but two methods on two different instances will be running in different threads. First, thanks for the post. There aren’t too many good examples that demonstrate parallel execution /w Grid combined with TestBase class – Test class inheritence. I used your approach and I wanted to get your input about an issue I’ve run into.
Setup – Java, TestNG running against Grid configuration (1 Hub, 3 nodes – 3 physical machines) I know this is about parallel execution so hang with me. In trying your approach I first setup a single @Test. This test does the following: Goes to url. Clicks link to go to login page. Enters username, password, clicks login button.
Performs a simple assertion. Clicks link to logout.
The @Test is datadriven, using the TestNG @DataProvider, which provides 2 rows of account (username/password) values – actually both rows contain the same values. So at this point we have a single test that is data-driven.
I then modify the @DataProvider so that it is now set as (parallel=true). So at this point when the test executes, it should run in parallel. One for each row of data. When it runs I see 2 instances (parallel) being kicked off on different nodes, but their seems to be confusion. For example, I may see the username value typed in twice into one of the login pages, and the other one left blank.
It’s like the commands are being sent to the wrong node. Wondering if you have any experience with this – running in parallel, when the parallel is triggered from the Data level? Is there something even more elaborate that has to be done with the code to keep everything straight? Thanks for your input, Greg.
Hi, first thanks for your blog. I tried to use this info but I have lots of problems with this issue. My xml build in that way: in every class there are many tests that I want them to be run. My problem is that I defined the webdriver in Threadlocal like u.
Every test that run go to BeforeInvocation before it start to get a new webdriver and then need to use it in the test. My problem is that the Thread in the beforeInvocation is not the same thread in the test and this is why the browsers that opens don’t know what to do and don’t get the right url and stays blank.
Do u know how to solve it? The main idea is like this one: thanks amit.
From this I presume that you have: 1. A single class with 3 methods which call Login and call data from another XML file. You want to call several XML files from testng.xml. Answer under number 1: At this point there is no way to make methods share a single instance of webdriver, it would have to have some extra coding to control, that only one method can work on the instance at a time. Solution might be answered here: but it’s not tested by us yet. Suggestions for one of the tips above: 1) Split tests to separate classes with own login data and call them in testng.xml:
Hello Istvan, While trying to implement your idea for JUnit I get this errror: org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. At this line: threadDriver.set(new RemoteWebDriver(new URL(“dc)); I’m not using a local server, I’m running my tests locally from my IDE and then in the CI. What I need to do is be able to run them in parallel in the CI but it seems that I need to create separate threads for that, right?
Any suggestions are very apreciated. Hi Alexandra, If you want to run the test locally you have to create a local webdriver instead of creating a remote one.
Instead of the RemoteWebDriver you can safely create a FirefoxDriver or ChromeDriver. UnreachableBrowserException can appear in multiple situations: 1. The selenium client-server connection is not properly configured. You have to have selenium running on both of the machines, and connect from the client to the server. The browser you asked for is not available through grid.
Recheck the configurations, and makes sure that the browser you asked for is available on the grid. Webdriver is not updated. In the past i met with this exception when i used older webdriver libraries. Hello, Thanks for the detailed blog. I tried the steps in this blog, however I get some errors.
I am running hub and node on my mac. Looks like node is not able to register and hence the test cases are failing. Hi, I use intellij and I try to use what you explained, i have 2 problems: 1.it doesn’t recognize @BeforeMethod, can i use BeforeClass instead? Hi PT, Re-tested with the same code sample and in our case everything is working as expected. We are unable to reproduce this issue based on the exception you have posted.
Can you please provide us more details and a scenario in a simple java code? Please, check if the problem still occurs with updated selenium-grid server, firefox browser and geckodriver, as mentioned in the recent comment.
Also check if the selenium-grid has the right permissions and the ports are not blocked by a firewall. Comments are closed.
Docker for Mac Edge release notes Estimated reading time: 52 minutes Here are the main improvements and issues per edge release, starting with the current release. The documentation is updated for each release. For system requirements, see.
Release notes for edge releases are listed below, are also available. (Following the CE release model, ‘beta’ releases are called ‘edge’ releases.) You can learn about both kinds of releases, and download stable and edge product installers at. Edge Releases of 2018 Docker Community Edition 184.108.40.206-beta1-mac75 2018-09-14. Upgrades.
Linux Kernel 4.9.125. New. New version scheme. Deprecation. Removed support of AUFS. Removed support of OSX 10.11.
Bug fixes and minor changes. Fix panic in diagnose Docker Community Edition 18.06.1-ce-mac74 2018-08-29. Upgrades. Bug fixes and minor changes.
Fix local DNS failing to resolve inside containers. Docker Community Edition 18.06.0-ce-mac69 2018-07-25. Upgrades. Bug fixes and minor changes. Fix bug in experimental SOCKS server. See.
Fix bug in docker login when “Securely store Docker logins in macOS keychain” is unchecked. Fixed Docker Community Edition 18.06.0-ce-rc3-mac68 2018-07-19. Upgrades. New.
Add an experimental SOCKS server to allow access to container networks, see. Also see. Bug fixes and minor changes. AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences Reset menu) before updating to the next major update. You can check documentation to and.
Fix startup issue with aufs. Harga office home and business 2016 for mac. Fix status bug which could prevent the kubernetes cluster from starting. Fixes. Fix bug which would cause VM logs to be written to RAM rather than disk in some cases, and the VM to hang. See.
Fix network connection leak triggered by haproxy TCP health-checks. Better message to reset vmnetd when it’s disabled. See Docker Community Edition 18.05.0-ce-mac67 2018-06-07.
Upgrades. Linux Kernel 4.9.93 with CEPH, DRBD, RBD, MPLSROUTING and MPLSIPTUNNEL enabled. If Kubernetes is enabled, the upgrade will be performed automatically when starting Docker for Mac. Bug fixes and minor changes. Fix VPNKit memory leak.
Fixes. Fix com.docker.supervisor using 100% CPU. Fixes,.
Do not override existing kubectl binary in /usr/local/bin (installed with brew or otherwise). Fixes,. Detect Vmnetd install error. Fixes,.
Virtual Machine default disk path is stored relative to $HOME. Fixes, Docker Community Edition 18.05.0-ce-mac66 2018-05-17.
Upgrades. New. Allow orchestrator selection from the UI in the “Kubernetes” pane, to allow “docker stack” commands to deploy to swarm clusters, even if Kubernetes is enabled in Docker for Mac. Bug fixes and minor changes. Use Simple NTP to minimise clock drift between the VM and the host.
Fixes. Fix filesystem event notifications for Swarm services and those using the new-style -mount option. Fixes,. Fix filesystem event delivery to Kubernetes pods when the path to the bind mount is a symlink.
Fix a race between calling stat on a file and calling close of a file descriptor referencing the file that could result in the stat failing with EBADF (often presented as “File not found”). Fixes. Do not allow install of Docker for Mac on macOS Yosemite 10.10, this version is not supported since Docker for Mac 17.09.0. Fix button order in reset dialog windows. Fixes. Diagnostics are run when diagnostics window is displayed, user is proposed to upload them when available.
Docker Community Edition 18.05.0-ce-rc1-mac63 2018-04-26. Upgrades. New.
Re-enable raw as the default disk format for users running macOS 10.13.4 and higher. Note this change only takes effect after a “reset to factory defaults” or “remove all data” (from the Whale menu - Preferences - Reset). Related to. Bug fixes and minor changes. Fix Docker for Mac not starting due to socket file paths being too long (typically HOME folder path being too long). Docker Community Edition 18.04.0-ce-mac62 2018-04-12.
Upgrades. Docker Community Edition 18.04.0-ce-rc2-mac61 2018-04-09. Upgrades. If Kubernetes is enabled, the upgrade will be performed automatically when starting Docker for Mac.
New. Enable ceph & rbd modules in LinuxKit VM. Bug fixes and minor changes. Fix upgrade straight from pre-17.12 versions where Docker for Mac cannot restart once the upgrade has been performed. Fixes Docker Community Edition 18.03.0-ce-mac58 2018-03-26.
Upgrades. Docker Community Edition 18.03.0-ce-rc4-mac57 2018-03-15.
Upgrades. AUFS 20180312. Bug fixes and minor changes. Fix support for AUFS. Fixes.
Fix synchronisation between CLI docker login and GUI login. Docker Community Edition 18.03.0-ce-rc3-mac56 2018-03-13. Upgrades. Linux Kernel 4.9.87.
Bug fixes and minor changes. Fix for the HTTP/S transparent proxy when using “localhost” names (e.g.
“host.docker.internal”, “docker.for.mac.host.internal”, “docker.for.mac.localhost”). Fix daemon not starting properly when setting TLS-related options. Fixes Docker Community Edition 18.03.0-ce-rc1-mac54 2018-02-27. Upgrades. New.
VM Swap size can be changed in settings. See,. Support NFS Volume sharing.
Also works in Kubernetes. Bug fixes and minor changes. Revert the default disk format to qcow2 for users running macOS 10.13 (High Sierra). There are confirmed reports of file corruption using the raw format which uses sparse files on APFS.
This change only takes effect after a reset to factory defaults (from the Whale menu - Preferences - Reset). Related to. DNS name host.docker.internal should be used for host resolution from containers. Older aliases (still valid) are deprecated in favor of this one. (See. Kubernetes Load balanced services are no longer marked as Pending. Fix hostPath mounts in Kubernetes.
Update Compose on Kubernetes to v0.3.0 rc4. Existing Kubernetes stacks will be removed during migration and need to be re-deployed on the cluster. Docker Community Edition 18.02.0-ce-mac53 2018-02-09. Upgrades. Bug fixes and minor changes. Fix update startup failure in some cases. Fix empty registry added by mistake in some cases in the Preference Daemon Pane.
Fixes. Clearer error message when incompatible hardware is detected. Diagnostics are not proposed in the error popup in this case. Docker Community Edition 18.02.0-ce-rc2-mac51 2018-02-02.
Upgrades. If you have Kubernetes enabled, the upgrade will be performed automatically when starting Docker for Mac. Bug fixes and minor changes. Fix Kubernetes-compose integration update that was causing startup failure.
Fixes. Fix some cases where selecting “Reset” after an error did not reset properly. Fix incorrect NTP config. Fixes Docker Community Edition 18.02.0-ce-rc1-mac50 2018-01-26. Upgrades. Bug fixes and minor changes.
Added “Restart” menu item. See. Keep any existing kubectl binary when activating Kubernetes in Docker for Mac, and restore it when disabling Kubernetes. Fixes,. Fix Kubernetes context selector. Fixes Docker Community Edition 18.01.0-ce-mac48 2018-01-19. Upgrades.
Linux Kernel 4.9.75. New. The directory holding the disk images was renamed (from /Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux to /Library/Containers/com.docker.docker/Data/vms/0`).
Bug fixes and minor changes. Fix error during resize/create Docker.raw disk image in some cases. Fixes, docker/for-mac#2453, (.
Fix additional allocated disk space not available in containers. Fixes.
Vpnkit port max idle time default restored to 300s. Fixes. Fix using an HTTP proxy with authentication. Fixes. Allow HTTP proxy excludes to be written as.docker.com as well as.docker.com. Allow individual IP addresses to be added to HTTP proxy excludes. Avoid hitting DNS timeouts when querying docker.for.mac.
when the upstream DNS servers are slow or missing. Fix for docker push to an insecure registry. Fixes.
Separate internal ports used to proxy HTTP and HTTPS content. If kubectl was already installed before Docker For Mac, restore the existing kubectl when sitching Kubernetes off in Docker for Mac. Migration of Docker Toolbox images is not proposed anymore in Docker For Mac installer (still possible to migrate Toolbox images manually). Docker Community Edition 17.12.0-ce-mac45 2018-01-05. Upgrades. New.
Experimental Kubernetes Support. You can now run a single-node Kubernetes cluster from the “Kubernetes” Pane in Docker For Mac Preferences and use kubectl commands as well as docker commands. See. DNS name docker.for.mac.host.internal should be used instead of docker.for.mac.localhost (still valid) for host resolution from containers, since since there is an RFC banning the use of subdomains of localhost (See. Bug fixes and minor changes. The docker engine is configured to use VPNKit as an HTTP proxy, fixing ‘docker pull’ in environments with no DNS.
Fixes Edge Releases of 2017 Docker Community Edition 17.12.0-ce-rc4-mac44 2017-12-21. Upgrades. Bug fixes and minor changes.
Display actual size used by the VM disk, especially useful for disks using raw format. Fix more specific edge cases in filesharing settings migration.
Docker Community Edition 17.12.0-ce-rc3-mac43 2017-12-15. Upgrades. Bug fixes and minor changes.
Fix filesharing migration issue Docker Community Edition 17.12.0-ce-rc2-mac41 2017-12-13. Upgrades. New. VM disk size can be changed in settings. Bug fixes and minor changes. Avoid VM reboot when changing host proxy settings.
Don’t break HTTP traffic between containers by forwarding them via the external proxy. Filesharing settings are now stored in settings.json. Daemon restart button has been moved to settings / Reset Tab. Display various component versions in About box. Better VM state handling & error messages in case of VM crashes Docker Community Edition 17.11.0-ce-mac40 2017-11-22. Upgrades.
Docker Community Edition 17.11.0-ce-rc4-mac39 2017-11-17. Upgrades. Linux Kernel 4.9.60. Bug fixes and minor changes. Fix login into private repository with certificate issue.
New. For systems running APFS on SSD on High Sierra, use raw format VM disks by default. This increases disk throughput (from 320MiB/sec to 600MiB/sec in dd on a 2015 MacBook Pro) and disk space handling. Existing disks are kept in qcow format, if you want to switch to raw format you need to “Reset to factory defaults”. To query the space usage of the file, use a command like: $ cd /Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/ $ ls -ls Docker.raw 3944768 -rw-r-r-@ 1 user staff 6 Nov 16 11:19 Docker.raw The first number ( 3944768) is the allocated space in blocks; the larger number 6 is the maximum total amount of space the file may consume in future in bytes. Docker Community Edition 17.11.0-ce-rc3-mac38 2017-11-09.
Upgrades. Bug fixes and minor changes. Fix docker build exits successfully but fails to build image. Docker Community Edition 17.11.0-ce-rc2-mac37 2017-11-02. Upgrades. Linuxkit blueprint updated to, fixes CVE-2017-15650. Bug fixes and minor changes.
Fix centos:5 & centos:6 images not starting properly with LinuxKit VM (fixes ). Docker Community Edition 17.10.0-ce-mac36 2017-10-24. Upgrades. New. VM entirely built with Linuxkit Docker Community Edition 17.09.0-ce-mac34 2017-10-06. Bug fixes and minor changes.
Fix Docker For Mac unable to start in some cases: removed use of libgmp sometimes causing the vpnkit process to die. Docker Community Edition 17.09.0-ce-mac31 2017-09-29. Upgrades. DataKit update (fix instability on High Sierra). Bug fixes and minor changes. Fix password encoding/decoding. May require to re-login to docker cloud after this version is installed.
(Fixes:docker/for-mac#2008, docker/for-mac#2016, docker/for-mac#1919, docker/for-mac#712, docker/for-mac#1220).