-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
8 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,18 +1,20 @@ | ||
Module Tests | ||
------------ | ||
# Module Tests | ||
|
||
To test module `foo`, create a directory `foo`, and put a file `all.mk` into it, e.g. | ||
|
||
foo/all.mk | ||
``` | ||
foo/all.mk | ||
``` | ||
|
||
All of the tests for the module should go here. The tests will be run | ||
*only* if the module is available, and has been built correctly on the system. | ||
|
||
The file should contain a target "MODULE.test". This is the main | ||
The file should contain a target `MODULE.test`. This is the main | ||
target used to test the module. The framework automatically makes the | ||
tests depend on the module (i.e. library). So if the module source | ||
changes, you can just do `make MODULE.test`. The module will be | ||
re-built, and the tests will be run. | ||
|
||
Note: all SQL tests share the same tests definitions (see sql directory). | ||
The modules themselves simply link to the actual tests files. | ||
Note: all SQL tests share the same tests definitions (see the `sql` | ||
directory). The modules themselves simply link to the actual tests | ||
files. |