File: README.md

package info (click to toggle)
libm2k 0.9.0-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 95,580 kB
  • sloc: xml: 1,611,497; cpp: 16,278; python: 4,181; cs: 516; sh: 471; ansic: 403; makefile: 35
file content (41 lines) | stat: -rw-r--r-- 1,749 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
## Test suite for ADALM2000 based on libm2k library

The tests are launched when running [main.py](main.py).
In the current working directory, a results directory is created. This contains:
* HTML test report
* plots
* .csv files with data used to plot the signals
* .txt file with results used in the tests


Before running the test suite, make sure all required Python packages are installed: 
```pip install -r requirements.txt```

To run a single test from one of the test classes open cmd in the working directory and run:
    ```main.py TestClass.test_name```
 Ex: ```main.py A_AnalogTests.test_1_analog_objects```


To run tests without generating the report files, add the "nofiles" option when running main.py .
    ```python main.py nofiles```
 Ex: ```main.py A_AnalogTests.test_1_analog_objects nofiles```


To run the test suite for the ADALM 2000 emulator, first make sure to have installed and running the 
emulator aplication [iio-emu](https://github.com/analogdevicesinc/iio-emu).
After that run from [main.py](main.py) the emulator tests with a specific local uri. 
Ex: ```main.py --uri ip:127.0.0.1 E_EmulatorTests```

To repeat a test, add the @repeat(times) decorator before the test to be repeated.
 
 Ex: <br>
```    @repeat(50)``` <br>
```    def test_2_calibration(self):```

### iio_diff

The directory contains utilities for storing iio state in xml format: ```xml_generator.py```, as well as an utility used to compare common, new and missing attributes: ```iio_diff.py```.

### Manual tests

The `dual_board` directory contains tests requiring two ADALM2000 boards. These tests cover synchronization and interaction scenarios. Ensure the boards are connected and configured as described in the standalone Python scripts.