First draft of the test guide

# Test environment for OSM testing

## OSM installation

### Latest stable release

This is the recommended installation procedure for general OSM users.

For a step-by-step procedure, please refer to this chapter of the [User Guide](https://osm.etsi.org/docs/user-guide/03-installing-osm.html) to build the latest stable release.

For the time being, Rel SEVEN 7.0.1 is the latest stable OSM release.

### Daily build

Daily builds of OSM Release SEVEN can be created by using the installer with the following options:

```bash

./install_osm.sh -R ReleaseSEVEN-daily -t releaseseven-daily -r testing -y

```

This build includes the latest community contributions and may contain bugs. Therefore it is only recommended for developers and contributors involved in community testing.

### New release candidate

TODO: To be edited when there is a new release candidate to be tested.

## Performing the tests

### Testing from OSM client sandbox (recommended)

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:

```bash

git clone "https://osm.etsi.org/gerrit/osm/sandboxes"

cd osm-tests

# Use the templates in the `localconfig` folder to create the appropriate

# `localconfig/envconfig.rc` and, optionally, `localconfig/envprovisioning.sh`

# 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:

```bash

OSM_CLIENT_VERSION=master vagrant up

```

Further details 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.

# OSM Tester Guide

This repository collects the best practices for running tests with OSM.

In particular, here is collected:

- The recommended procedure to setup your testing environment to validate a specific OSM build.

- The collection of tests created by OSM community.