"composer update" is something you should only do as project maintainer, when you want to check for newer versions of your dependencies, or after you changed anything in your composer.json file (i.e. added / modified / removed dependencies). This command not only will download dependencies, but also create a new "composer.lock" file.
On all other cases (deployment, testing) it is best to use "composer install" which only reads the "composer.lock" file. In this way, you are sure that every machine gets the exact same version. And as a nice bonus is much faster than the "composer.update" command :-)
This pull adds the base for testing Weblinks component with an Firefox automated browser via Selenium and Codeception Framework.
See it in action in the following video: https://www.youtube.com/watch?v=gpsZVZCsawg
This pull will launch the tests in Travis, however you can run the tests in your local machine too. Find the instructions at: README.md
