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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This is the Github repo for Mbed cellular connectivity:
11
11
12
12
TESTS Cellular Greentea test
13
13
14
-
**Application developers should only use API folder.
14
+
**Note:**Application developers should use only the `API` folder.
15
15
16
16
## Known limitations
17
17
@@ -47,16 +47,16 @@ You can define the debug tracing level in the `mbed_app.json` configuration file
47
47
48
48
## Greentea tests
49
49
50
-
The `TESTS` folder contains Greentea tests for cellular specific classes. You need to give relevant configuration file with `--app-config` parameter, e.g.:
50
+
The `TESTS` folder contains Greentea tests for cellular specific classes. You need to give relevant configuration file with `--app-config` parameter, such as:
51
51
52
52
mbed test -n features-cellular-tests-* --app-config features\cellular\TESTS\socket\udp\template_mbed_app.json.txt -v
53
53
54
-
Note that Greentea tests use SIM PIN so you need to change that or your SIM card may get locked.
54
+
**Note:**Greentea tests use SIM PIN, so you need to change that or your SIM card may get locked.
55
55
56
56
## Unit tests
57
57
58
58
Cellular unit tests are in Mbed OS root `UNITTESTS`. Unit tests are based on the stubbing method.
59
59
60
60
You need the following applications: `cpputest`, `gcov` and `lcov` (genhtml) for running the tests.
61
61
62
-
After you have run the `run_tests` script, you can find test results under`UNITTESTS/results` folder and line and function coverages under the `UNITTESTS/coverages` folder.
62
+
After you run the `run_tests` script, you can find test results in`UNITTESTS/results`, and line and function coverages in `UNITTESTS/coverages`.
0 commit comments