Skip to content

Commit d3ece27

Browse files
authored
Merge pull request #346 from bridadan/wildcard-test-names-readme
Adding details on wildcard character for limiting tests
2 parents 96b1d10 + 60ba721 commit d3ece27

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -571,6 +571,15 @@ You can limit the scope of the tests built and ran by using the `-n` option. Thi
571571
$ mbed test -m K64F -t GCC_ARM -n TESTS-functional-test1,TESTS-functional-test2
572572
```
573573

574+
You can use the wildcard character `*` to run a group of tests that share a common prefix without specifying each test individually. For instance, if you only want to run the three tests `TESTS-functional-test1`, `TESTS-functional-test2`, and `TESTS-functional-test3` but you have other tests in your project, you can run:
575+
576+
```
577+
$ mbed test -m NUCLEO_F429ZI -t GCC_ARM -n TESTS-functional*
578+
```
579+
580+
**Note:** Some shells will try to expand the wildcard character `*` into filenames that exist in your working directory. To prevent this behavior, please see your shell's documentation.
581+
582+
574583
### Test directory structure
575584

576585
Test code exists in the following directory structure:

0 commit comments

Comments
 (0)