@@ -32,92 +32,37 @@ Daily builds of branches ELEVEN, TEN, NINE and master can be installed by using
These builds include the latest community contributions and may contain bugs. Therefore they are only recommended for developers and contributors involved in community testing.
For regular testing, it is highly recommended using a local OSM's tester sandbox as client to validate a given OSM build. Among other advantages, this sandbox provides all the relevant dependencies to make consistent testing, including Robot tests.
In order to create the sandbox locally, you can simply type:
# with the details of the DUT (i.e. the credentials of your local VIM environment
# and the IP address of your OSM build under test).
vagrant up
```
In case you needed to use the latest version of the OSM client (e.g. for testing non-stable builds), you can set the `OSM_CLIENT_VERSION` environment variable before creating the sandbox:
##### Release THIRTEEN daily
```bash
OSM_CLIENT_VERSION=master vagrant up
```
At the end of the build, here is the sandbox that Vagrant creates for you and the relation with the OSM build and your local VIM:

Further details to customize it for your local setup (i.e. editing your `localconfig/envconfig.rc` and `localconfig/envprovisioning.sh`) can be found in the [README.md](https://osm.etsi.org/gitweb/?p=osm/sandboxes.git;a=blob_plain;f=osm-tests/README.md;h=39ed9366aee3347b8f48a8ace42431df4a776b41;hb=HEAD) file included in the same folder.
### Testing from inside an OSM build
For casual testing you can choose to log into the OSM build and launching some tests locally. Although this is discouraged for consistent community validations or automated testing, it is feasible for an informal validation.
## (OLD) ANNEX: How to clean a prior OSM installation (not recommended for community testing)
**This procedure is highly discouraged for community testing.** Unless you are really sure about what you are doing, please use a clean Ubuntu VM instead.