mirror of
https://github.com/vlang/v.git
synced 2023-08-10 21:13:21 +03:00
ab37081f02
Due to the inability to detect warnings in REPL tests, I implemented running something very similar, but with the -prod flag enabled. (See https://github.com/vlang/v/pull/2536) There is also a minor change in os.walk_ext to not add duplicated path separators: /path//file.ext -> /path/file.ext |
||
---|---|---|
.. | ||
runner | ||
.gitattributes | ||
.gitignore | ||
arr_decl.repl | ||
chained_fields.correct.repl | ||
chained_fields.repl | ||
conditional_blocks.repl | ||
default_printing.repl | ||
empty_struct.repl | ||
error_nosave.repl | ||
error.repl | ||
function.repl | ||
immutable_len_fields.repl | ||
interpolation.repl | ||
multiple_decl.repl | ||
multiple_println.repl | ||
naked_strings.repl | ||
newlines.repl | ||
nomain.repl | ||
nothing.repl | ||
println.repl | ||
README.md | ||
repl_test.v | ||
run.v | ||
var_decl.repl |
V REPL Tests Script
How to write a new test
- Create a new file named
*.repl
- Write the input to be given to REPL
- Add
===output===
- Write the output expected
Notes
Keep in mind, that the way V repl works for now, every non empty line would cause a new recompilation of the entire repl content that was collected so far.
Longer REPL files would cause measurably longer recompilation/testing times.
Also, longer repl files would be slower to debug when they fail, It is better to have several smaller files vs one huge REPL file.
Example :
a := 1
println(a)
===output===
1