|
3 | 3 | [](https://travis-ci.com/magento/magento2-kubernetes-devbox)
|
4 | 4 | <!--[](./LICENSE)-->
|
5 | 5 | [](http://semver.org/spec/v2.0.0.html)
|
6 |
| -<!--[](https://github.com/paliarush/magento2-devbox-for-developers/releases/latest)--> |
| 6 | +<!--[](https://github.com/paliarush/magento2-vagrant-for-developers/releases/latest)--> |
7 | 7 |
|
8 | 8 | * [What You get](#what-you-get)
|
9 | 9 | * [How to install](#how-to-install)
|
|
33 | 33 | * [Redis for caching](#redis-for-caching)
|
34 | 34 | * [Reset environment](#reset-environment)
|
35 | 35 | * [Switch NodeJS Versions](#switch-nodejs-versions)
|
| 36 | + * [DevBox tests](#devbox-tests) |
36 | 37 | * [FAQ](#faq)
|
37 | 38 |
|
38 | 39 | ## What You get
|
@@ -320,7 +321,7 @@ bash m-composer update
|
320 | 321 | ### Running Magento tests
|
321 | 322 |
|
322 | 323 | Not available yet.
|
323 |
| -<!--See [draft](https://github.com/paliarush/magento2-devbox-for-developers/issues/120)--> |
| 324 | +<!--See [draft](https://github.com/paliarush/magento2-vagrant-for-developers/issues/120)--> |
324 | 325 |
|
325 | 326 |
|
326 | 327 | ## Environment configuration
|
@@ -394,31 +395,26 @@ n <version>
|
394 | 395 |
|
395 | 396 | Note: See [Working with npm](https://www.npmjs.com/package/n#working-with-npm) if after switching versions with `n`, `npm` is not working properly.
|
396 | 397 | -->
|
| 398 | + |
| 399 | +### DevBox tests |
| 400 | + |
| 401 | +The tests are executed on every PR on Travis CI. It is possible to configure the same tests to run on the forked repository. |
| 402 | + |
| 403 | +An extended testsuite is executed nightly on the master branch. On every PR by default only basic smoke tests are executed. |
| 404 | +It is possible to execute an extended testsuite on every PR build by uncommenting `RUN_EXTENDED_TEST_SUITE=true` in the [.travis.yaml](./.travis.yml) |
| 405 | + |
| 406 | +The same tests can be run on local using the following command. :warning: only one devbox can be running on the same host at the same time. The tests will destroy existing devbox installation. |
| 407 | + |
| 408 | +``` |
| 409 | +cd tests |
| 410 | +bash ./testsuite-basic.sh # OR bash ./testsuite-extended.sh |
| 411 | +``` |
| 412 | + |
397 | 413 | ### FAQ
|
398 |
| -<!-- |
399 | 414 | 1. To debug any CLI script in current Devbox project, set `debug:devbox_project` option in [config.yaml](etc/config.yaml.dist) to `1`
|
400 |
| - 1. Is Windows 10 supported? Yes, but you may face the same issue as described [here](https://github.com/paliarush/magento2-devbox-for-developers/issues/36) or [here](https://github.com/paliarush/magento2-devbox-for-developers/issues/173). Also Virtual box may not work on Windows 10 in headless mode, see how to [enable GUI mode](https://www.devboxup.com/docs/virtualbox/configuration.html) |
401 |
| - 1.  On OSX and \*nix hosts NFS will be used by default to sync your project files with guest. On some hosts Devbox cannot configure NFS properly, in this case it is possible to deploy project without NFS by setting `use_nfs` option in [config.yaml](etc/config.yaml.dist) to `0` <br /> |
402 |
| - 1.  On Windows hosts you might face `Composer Install Error: ZipArchive::extractTo(): Full extraction path exceed MAXPATHLEN (260)` exception during `composer install`. This can be fixed in 2 ways: decrease path length to the project directory or set `composer_prefer_source` option in [config.yaml](etc/config.yaml.dist) to `1` |
403 | 415 | 1. Make sure that you used `magento2-devbox` directory as project root in PHP Storm (not `magento2-devbox/magento`)
|
404 | 416 | 1. If project opened in PhpStorm looks broken, close PhpStorm and remove `magento2-devbox/.idea`. Run `bash magento2-devbox/scripts/host/configure_php_storm.sh`. After opening project in PhpStorm again everything should look good
|
405 |
| - 1. If code is not synchronized properly on Windows hosts (or when NFS mode is disabled in [config.yaml](etc/config.yaml.dist) explicitly), make sure that PhpStorm is running before making any changes in the code. This is important because otherwise PhpStorm will not be able to detect changes and upload them to the guest machine |
406 | 417 | 1. Please make sure that currently installed software, specified in [requirements section](#requirements), meets minimum version requirement
|
407 | 418 | 1. Be careful if your OS is case-insensitive, NFS might break the symlinks if you cd into the wrong casing and you power the devbox up. Just be sure to cd in to the casing the directory was originally created as.
|
408 |
| - 1. Cannot run unit tests from PHPStorm on Magento 2.2, see possible solution [here](https://github.com/paliarush/magento2-devbox-for-developers/issues/167) |
409 |
| - 1. [Permission denied (publickey)](https://github.com/paliarush/magento2-devbox-for-developers/issues/165) |
410 |
| - 1. If during a devbox reload, the following message appears: |
411 |
| - |
412 |
| - >There was a problem while downloading the metadata for your box |
413 |
| - to check for updates. This is not an error, since it is usually due |
414 |
| - to temporary network problems. This is just a warning. The problem |
415 |
| - encountered was: |
416 |
| - The requested URL returned error: 404 Not Found |
417 |
| - |
418 |
| - It is likely that your devbox cli is caching an old url. Perform the following cli commands: |
419 |
| - |
420 |
| - ```bash |
421 |
| - sed -i -- 's/atlas.hashicorp/devboxcloud/g' ~/.devbox.d/boxes/{name of your paliarush/ubuntu image}/metadata_url |
422 |
| - mv ~/.devbox.d/boxes/{name of your paliarush/ubuntu image}/metadata_url2 ~/.devbox.d/boxes/{name of your paliarush/ubuntu image}/metadata_url |
423 |
| - ``` |
424 |
| ---> |
| 419 | + 1. Cannot run unit tests from PHPStorm on Magento 2.2, see possible solution [here](https://github.com/paliarush/magento2-vagrant-for-developers/issues/167) |
| 420 | + 1. [Permission denied (publickey)](https://github.com/paliarush/magento2-vagrant-for-developers/issues/165) |
0 commit comments