Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Icetea added #659

Merged
merged 51 commits into from
Sep 4, 2018
Merged
Changes from 1 commit
Commits
Show all changes
51 commits
Select commit Hold shift + click to select a range
2132ceb
Icetea added
May 30, 2018
fa8de42
Copy edit testing_intro.md
Aug 13, 2018
5bdfb85
Complete initial copy edits of testing_icetea.md
Aug 13, 2018
df471aa
Copy edit icetea.md
Aug 20, 2018
8988382
Updated link, will work after the integration PR is merged
Aug 22, 2018
e1e3903
Fix instruction for running MAC tester testcases in driver creation g…
Aug 23, 2018
9d0c80f
Copy edit MeshInterface.md
Aug 24, 2018
97bee7d
Remove icetea.md because not ready
Aug 27, 2018
62958a8
Add icetea.md content
Aug 28, 2018
fcc26d1
Fixes according to comments
Aug 28, 2018
f0eab0a
Update cli-test-debug.md
jen3andruska Aug 28, 2018
f746f54
Update cli-test-debug.md
jen3andruska Aug 28, 2018
781f4e7
Update cli-test-debug.md
jen3andruska Aug 28, 2018
87a423d
Update cli-test-debug.md
jen3andruska Aug 28, 2018
bcc22cf
Change cli-test-debug according to comments
Aug 28, 2018
5b2cb15
Update cli-test-debug.md
jen3andruska Aug 28, 2018
42e2015
Update cli-test-debug.md
jen3andruska Aug 28, 2018
5db3026
Update cli-test-debug.md
jen3andruska Aug 29, 2018
dde79f8
Update icetea.md
jen3andruska Aug 29, 2018
f34bd81
Update icetea.md
jen3andruska Aug 29, 2018
a08ee50
Update icetea.md
jen3andruska Aug 29, 2018
e979e11
Update icetea.md
jen3andruska Aug 29, 2018
94997d1
Updating Icetea.md.
Aug 29, 2018
48737b4
Updating Icetea.md
Aug 29, 2018
495d484
Updating Icetea.md
Aug 29, 2018
f102a1b
Update icetea.md
jen3andruska Aug 29, 2018
61cab4c
Update cli-test-debug.md
Aug 29, 2018
622ff0f
Update icetea.md
jen3andruska Aug 29, 2018
ff04613
Update icetea.md
jen3andruska Aug 29, 2018
46897ac
Update icetea.md
jen3andruska Aug 29, 2018
881ccbd
Update icetea.md
jen3andruska Aug 29, 2018
f2b6db3
Update icetea.md
jen3andruska Aug 29, 2018
59a858f
update cli-test-debug.md
Aug 29, 2018
95a9aac
Update testing_icetea.md
Aug 29, 2018
8d1b6a3
Updated Icetea.md
Aug 29, 2018
ef3e502
Update testing_greentea.md
jen3andruska Aug 30, 2018
03b9602
Update testing_greentea.md
jen3andruska Aug 30, 2018
f329c00
Update testing_greentea.md
jen3andruska Aug 30, 2018
60908f4
Update testing_greentea.md
jen3andruska Aug 30, 2018
5f59df6
Update testing_greentea.md
jen3andruska Aug 30, 2018
8c973fa
Update testing_greentea.md
jen3andruska Aug 30, 2018
d7ebf45
Update testing_greentea.md
jen3andruska Aug 30, 2018
e0d4907
Update testing_greentea.md
jen3andruska Aug 30, 2018
90ef9e3
Update testing_greentea.md
jen3andruska Aug 30, 2018
0e826d8
Update testing_greentea.md
jen3andruska Aug 30, 2018
2c47f44
Update testing_icetea.md
jen3andruska Aug 30, 2018
12bf038
Update testing_icetea.md
jen3andruska Aug 30, 2018
e05475e
Copy edit icetea.md
Aug 31, 2018
8411229
Copy edit cli-test-debug.md
Aug 31, 2018
f2a2532
Make changes from comments in icetea.md
Aug 31, 2018
2bc593c
Make changes from comments to cli-test-debug.md
Aug 31, 2018
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update testing_icetea.md
jen3andruska authored and Olli-Pekka Puolitaival committed Sep 4, 2018
commit 12bf038f49b53c2c81c02728be476e1c23a02ac1
16 changes: 8 additions & 8 deletions docs/tools/testing/testing_icetea.md
Original file line number Diff line number Diff line change
@@ -38,7 +38,7 @@ The full build process is:

You can run automated tests through Mbed CLI with the `--icetea` option. You can find more information about this in the [Mbed CLI test documentation](/docs/tools/offline/cli-test-debug.md).

The testing process requires tests to be built and that a test specification JSON file exist that describes these available tests. See the [test specification format](https://github.com/ARMmbed/greentea#test-specification-json-formatted-input).
The testing process requires that tests be built and that a test specification JSON file that describes these available tests exists. See the [test specification format](https://github.com/ARMmbed/greentea#test-specification-json-formatted-input).

The test specification JSON is similar for the Greentea and Icetea tests.

@@ -48,11 +48,11 @@ The Icetea tool handles the actual testing process. To read more about this tool

##### Writing test cases

For writing your own Python test scripts, you can read further information from [Icetea Test Case API](https://github.com/ARMmbed/icetea/blob/master/doc/tc_api.md).
To write your own Python test scripts, please read the further information in [Icetea Test Case API](https://github.com/ARMmbed/icetea/blob/master/doc/tc_api.md).

##### Writing CLI applications

To be able to run the commands given to the DUT, you need to provide a CLI application that runs on the DUT. There is a library that you can use to create your own CLI application; it is called [mbed-client-cli](https://github.com/ARMmbed/mbed-client-cli). You can also find example Mbed CLI applications from the `mbed-os` repository [test applications](https://github.com/ARMmbed/mbed-os/tree/master/TEST_APPS/device).
To be able to run the commands given to the DUT, you need to provide a CLI application that runs on the DUT. There is a library that you can use to create your own CLI application, called [mbed-client-cli](https://github.com/ARMmbed/mbed-client-cli). You can also find example Mbed CLI applications in the `mbed-os` repository [test applications](https://github.com/ARMmbed/mbed-os/tree/master/TEST_APPS/device).

### Debugging tests

@@ -62,7 +62,7 @@ Debugging tests is a crucial part of the development and porting process. This s

The most straightforward way to export a test is to copy the test application's source code from its test directory to your project's root. This way, the tools treat it like a normal application.

You can find the path to the test application you wish to export by running the following command:
You can find the path to the test application that you want to export by running the following command:

```
mbed test --compile-list -n <test name> --icetea
@@ -78,18 +78,18 @@ You can find your exported project in the root project directory.

#### Running a test while debugging

After you export your test to your IDE, build the project, and load it onto your target using your debugger.
After you export your test to your IDE, build the project and load it onto your target by using your debugger.

Bring the target out of reset, and run the program. Your target waits for a command over serial line.
Bring the target out of reset, and run the program. Your target waits for a command over the serial line.

You can now use Icetea commands to run the test:

```
icetea -m <target> -t <toolchain> --tc <path to testcase>
```

This detects your attached target and drives the test. If you need to rerun the test, reset the device with your debugger, run the program and run the same command.
This detects your attached target and drives the test. If you need to rerun the test, then reset the device with your debugger, run the program and run the same command.

For an explanation of the arguments used in this command, please run `icetea --help`.

Note that instead of running the test you can also open a serial connection to the target and give the Mbed CLI commands manually.
Note that instead of running the test, you can also open a serial connection to the target and give the Mbed CLI commands manually.