diff --git a/docs/configure_device.md b/docs/configure_device.md new file mode 100644 index 000000000..ad58521a4 --- /dev/null +++ b/docs/configure_device.md @@ -0,0 +1,41 @@ +# Device Configuration + +The device configuration file allows you to customize the testing behavior for a specific device. This file is located at `local/devices/{Device Name}/device_config.json`. Below is an overview of how to configure the device tests. + +## Device Information + +The device information section includes the manufacturer, model, and MAC address of the device. These details help identify the specific device being tested. + +## Test Modules + +Test modules are groups of tests that can be enabled or disabled as needed. You can choose which test modules to include for your device. The device configuration file contains the following test module: + +- DNS Test Module + +### Enabling and Disabling Test Modules + +To enable or disable a test module, modify the `enabled` field within the respective module. Setting it to `true` enables the module, while setting it to `false` disables the module. + +## Individual Tests + +Within the DNS test module, there are individual tests that can be enabled or disabled. These tests focus on specific aspects of network behavior. You can customize the tests based on your device and testing requirements. + +### Enabling and Disabling Tests + +To enable or disable an individual test, modify the `enabled` field within the respective test. Setting it to `true` enables the test, while setting it to `false` disables the test. + +> Note: The example device configuration file (`resources/devices/template/device_config.json`) provides a complete usage example, including the structure and configuration options for the DNS test module and its tests. You can refer to this file to understand how to configure your device tests effectively. + +## Customizing the Device Configuration + +To customize the device configuration for your specific device, follow these steps: + +1. Copy the default configuration file provided in the `resources/devices/template` folder. + - Create a new folder for your device under `local/devices` directory. + - Copy the `device_config.json` file from `resources/devices/template` to the newly created device folder. + +This ensures that you have a copy of the default configuration file, which you can then modify for your specific device. + +> Note: Ensure that the device configuration file is properly formatted, and the changes made align with the intended test behavior. Incorrect settings or syntax may lead to unexpected results during testing. + +If you encounter any issues or need assistance with the device configuration, refer to the Test Run documentation or ask a question on the Issues page. diff --git a/docs/get_started.md b/docs/get_started.md new file mode 100644 index 000000000..7b8cf9e13 --- /dev/null +++ b/docs/get_started.md @@ -0,0 +1,53 @@ +# Getting Started + +## Prerequisites + +### Hardware + +Before starting with Test Run, ensure you have the following hardware: + +- PC running Ubuntu LTS (laptop or desktop) +- 2x USB Ethernet adapter (one may be a built-in Ethernet port) +- Internet connection + +### Software + +Ensure the following software is installed on your Ubuntu LTS PC: + +- Python 3 (already available on Ubuntu LTS) +- Docker - Installation Guide: [https://docs.docker.com/engine/install/](https://docs.docker.com/engine/install/) +- Open vSwitch ``sudo apt-get install openvswitch-common openvswitch-switch`` + +## Installation + +1. Download Test Run from the releases page or the appropriate source. + +2. Run the install script. + +## Configuration + +1. Copy the default configuration file. + +2. Open the `local/system.json` file and modify the configuration as needed. Specify the interface names for the internet and device interfaces. + +## Test Your Device + +1. Attach network interfaces: + + - Connect one USB Ethernet adapter to the internet source (e.g., router or switch) using an Ethernet cable. + - Connect the other USB Ethernet adapter directly to the IoT device you want to test using an Ethernet cable. + +2. Start Test Run. + + - To run Test Run in network-only mode (without running any tests), use the `--net-only` option. + + - To skip network validation before use and not launch the faux device on startup, use the `--no-validate` option. + +# Troubleshooting + +If you encounter any issues or need assistance, consider the following: + +- Ensure that all hardware and software prerequisites are met. +- Verify that the network interfaces are connected correctly. +- Check the configuration in the `local/system.json` file. +- Refer to the Test Run documentation or ask for further assistance from the support team.