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

docs: describe how coutput_test.v works

pull/11005/head
Delyan Angelov 2021-07-31 12:29:22 +03:00
parent 08016ab374
commit d2e28e8fc5
No known key found for this signature in database
GPG Key ID: 66886C0F12D595ED
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
TESTS.md
View File

@ -23,6 +23,17 @@ General runnable tests for different features of the V compiler.
Test output of running a V program matches an expected .out file. Test output of running a V program matches an expected .out file.
Check the source for how to test panics. Check the source for how to test panics.
* `vlib/v/gen/c/coutput_test.v`
This tests whether the generated C source code matches all expectations,
specified in *.c.must_have files, in the folder vlib/v/gen/c/testdata/ .
Each `.c.must_have` file has to have a corresponding .vv file.
Each `.c.must_have` file, consists of multiple lines. Each of these
lines, *should* be present *at least once* in the output, when the .vv
file is compiled with `-o -` .
* `vlib/v/tests/run_project_folders_test.v` * `vlib/v/tests/run_project_folders_test.v`
Tests whether whole project folders can be compiled, and run. Tests whether whole project folders can be compiled, and run.
NB: Each project in these folders, should finish with exit code 0, NB: Each project in these folders, should finish with exit code 0,