mender-convert/scripts/README-run-tests.md

# Run tests

The tests utilize the provided Docker container in this repository and conversion
is done using the `docker-mender-convert` command. For this reason we first need
to build the container (commands must be run from the root directory of
`mender-convert`):

```bash
./docker-build
```

Run tests:

```bash
./scripts/run-tests.sh
```
MEN-2608: add mender-convert (version 2) The goals of the re-write was to achieve the following: 1. It should be easy to extend the tool to support other boards or distributions 2. We should not compile code in the tool (rely on binaries built elsewhere) compiling code increases complexity, due to requirement of toolchains etc. 3. The tool shall not be designed around specific hardware/platform types - This is the case today with the usage of --device-type flag 4 The tool should be to convert images without knowing anything about the hardware/platform relates to above 3. 5. Configuration interface should be simplified - command line flags -> configuration files 6. Platform specific code shall be provided trough “hooks”, and are not part of the “core” mender-convert code 7. It shall be easy to extend functionality - support for rootfs overlay to inject user applications/configurations - ability to override how the Mender Artifact is generated (to be able to sign and include state-scripts) 8. Code structure should be modular - Eases Maintenance and possibility of making isolated changes Changelog: Title Signed-off-by: Mirza Krak <mirza.krak@northern.tech> 5 years ago			`# Run tests`

README-run-tests.md: update instructions The run-tests.sh script utilizes 'docker-mender-convert`. Changelog: None Signed-off-by: Mirza Krak <mirza.krak@northern.tech> 5 years ago			`The tests utilize the provided Docker container in this repository and conversion`
			is done using the `docker-mender-convert` command. For this reason we first need
			`to build the container (commands must be run from the root directory of`
			`mender-convert`):
MEN-2608: add mender-convert (version 2) The goals of the re-write was to achieve the following: 1. It should be easy to extend the tool to support other boards or distributions 2. We should not compile code in the tool (rely on binaries built elsewhere) compiling code increases complexity, due to requirement of toolchains etc. 3. The tool shall not be designed around specific hardware/platform types - This is the case today with the usage of --device-type flag 4 The tool should be to convert images without knowing anything about the hardware/platform relates to above 3. 5. Configuration interface should be simplified - command line flags -> configuration files 6. Platform specific code shall be provided trough “hooks”, and are not part of the “core” mender-convert code 7. It shall be easy to extend functionality - support for rootfs overlay to inject user applications/configurations - ability to override how the Mender Artifact is generated (to be able to sign and include state-scripts) 8. Code structure should be modular - Eases Maintenance and possibility of making isolated changes Changelog: Title Signed-off-by: Mirza Krak <mirza.krak@northern.tech> 5 years ago
README-run-tests.md: update instructions The run-tests.sh script utilizes 'docker-mender-convert`. Changelog: None Signed-off-by: Mirza Krak <mirza.krak@northern.tech> 5 years ago			```bash
			`./docker-build`
			```
MEN-2608: add mender-convert (version 2) The goals of the re-write was to achieve the following: 1. It should be easy to extend the tool to support other boards or distributions 2. We should not compile code in the tool (rely on binaries built elsewhere) compiling code increases complexity, due to requirement of toolchains etc. 3. The tool shall not be designed around specific hardware/platform types - This is the case today with the usage of --device-type flag 4 The tool should be to convert images without knowing anything about the hardware/platform relates to above 3. 5. Configuration interface should be simplified - command line flags -> configuration files 6. Platform specific code shall be provided trough “hooks”, and are not part of the “core” mender-convert code 7. It shall be easy to extend functionality - support for rootfs overlay to inject user applications/configurations - ability to override how the Mender Artifact is generated (to be able to sign and include state-scripts) 8. Code structure should be modular - Eases Maintenance and possibility of making isolated changes Changelog: Title Signed-off-by: Mirza Krak <mirza.krak@northern.tech> 5 years ago
			`Run tests:`

README-run-tests.md: update instructions The run-tests.sh script utilizes 'docker-mender-convert`. Changelog: None Signed-off-by: Mirza Krak <mirza.krak@northern.tech> 5 years ago			```bash
			`./scripts/run-tests.sh`
			```