You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: features/cellular/README.md
+3-14Lines changed: 3 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,6 @@ This is the Github repo for Mbed cellular connectivity:
9
9
device Implementation of cellular device and state machine
10
10
targets Vendor specific cellular module adaptations
11
11
12
-
TESTS Cellular Greentea test
13
-
14
12
**Note:** Application developers should use only the `API` folder.
15
13
16
14
## Known limitations
@@ -28,6 +26,7 @@ You can change cellular defaults in the `mbed_lib.json` configuration file.
28
26
## Debug traces
29
27
30
28
You can define the debug tracing level in the `mbed_app.json` configuration file:
29
+
31
30
```
32
31
"target_overrides": {
33
32
"*": {
@@ -48,18 +47,8 @@ You can define the debug tracing level in the `mbed_app.json` configuration file
48
47
49
48
## Greentea tests
50
49
51
-
The `TESTS` folder contains Greentea tests for cellular specific classes. You need to give relevant configuration file with `--app-config` parameter, such as:
52
-
53
-
```
54
-
mbed test -n features-cellular-tests-* --app-config features\cellular\TESTS\socket\udp\template_mbed_app.json.txt -v
55
-
```
56
-
57
-
**Note:** Greentea tests use SIM PIN, so you need to change that or your SIM card may get locked.
50
+
Cellular connectivity can be tested with generic Mbed OS netsocket and network interface tests found in Mbed OS root `TESTS` directory. For more information, see `TESTS/netsocket/README.md` and `TESTS/network/interface/README.md`.
58
51
59
52
## Unit tests
60
53
61
-
Cellular unit tests are in Mbed OS root `UNITTESTS`. Unit tests are based on the stubbing method.
62
-
63
-
You need the following applications: `cpputest`, `gcov` and `lcov` (genhtml) for running the tests.
64
-
65
-
After you run the `run_tests` script, you can find test results in `UNITTESTS/results`, and line and function coverages in `UNITTESTS/coverages`.
54
+
Cellular unit tests are in Mbed OS root `UNITTESTS/features/cellular`.
0 commit comments