### From an environment identical to OSM CICD
-````bash
+```bash
git clone https://osm.etsi.org/gerrit/osm/devops
git clone https://osm.etsi.org/gerrit/osm/IM
git clone https://osm.etsi.org/gerrit/osm/osmclient
- For helping in the migration tests and other scenarios in which you don't want
to destroy the deployments immediately, the following tags are used:
- - prepare: for the tests that are used to deploy the network
+ - `prepare`: for the tests that are used to deploy the network
services under test
- - verify: for the tests that perform the actual testing, or changes for
+ - `verify`: for the tests that perform the actual testing, or changes for
additional verifications (e.g. scaling).
- - cleanup: already described above.
+ - `cleanup`: already described above.
So, for instance, you could first deploy a number of network services executing
the tests with "prepare" tag, migrate to another OSM version, and then
check_spaces_eol robot-systest/lib
echo "No presence of spaces at EOL in robot files. Correct!"
+# Other policies to be added here:
+# - Blank lines used to separate main sections (Settings, Variables, Test Cases, Keywords)
+# - Blank lines used to separate parts of eah section:
+# - Variables: max 1 blank line to separate each one
+# - Settings: 1 blank line to separate each kind of setting (all LIbrary together, all Resource together, etc.)
+# - Test cases: 2 blank lines between test cases, max 1 blank line inside Test case, no blank line after Test Case Keyword
+
echo "SUCCESS"
exit 0