vieter-v
/
v
2
0
Fork 0
Code Issues Pull Requests Releases Activity

docs: cleanup the `Test files` section a little

pull/12077/head
Delyan Angelov 2021-10-05 22:49:51 +03:00
parent 6d2c1f7e2c
commit 443fa50244
No known key found for this signature in database
GPG Key ID: 66886C0F12D595ED
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/docs.md
View File

@ -3645,9 +3645,9 @@ fn main() {
``` ```
```v failcompile ```v failcompile
// hello_test.v
module main module main
// hello_test.v
fn test_hello() { fn test_hello() {
assert hello() == 'Hello world' assert hello() == 'Hello world'
} }
@ -3673,7 +3673,7 @@ just like `hello.v`, i.e. both are part of the same module. Note also that
since `module main` is a regular module like the others, internal tests can since `module main` is a regular module like the others, internal tests can
be used to test private functions in your main program .v files too. be used to test private functions in your main program .v files too.
You can also define special test functions in a test file: You can also define these special test functions in a test file:
* `testsuite_begin` which will be run *before* all other test functions. * `testsuite_begin` which will be run *before* all other test functions.
* `testsuite_end` which will be run *after* all other test functions. * `testsuite_end` which will be run *after* all other test functions.