1
0
mirror of https://github.com/vlang/v.git synced 2023-08-10 21:13:21 +03:00
v/vlib/compiler/tests/repl
2019-10-27 10:03:15 +03:00
..
runner compiler/vlib: replace substr/left/right with [start..end] everywhere 2019-10-27 10:03:15 +03:00
.gitattributes
.gitignore
arr_decl.repl
chained_fields.correct.repl
chained_fields.repl
conditional_blocks.repl
default_printing.repl
empty_struct.repl
error_nosave.repl parser: undefined error 2019-10-20 20:47:27 +03:00
error.repl parser: undefined error 2019-10-20 20:47:27 +03:00
function.repl
immutable_len_fields.repl
interpolation.repl
multiple_decl.repl
multiple_println.repl
naked_strings.repl
newlines.repl
nomain.repl tests: no main fn 2019-10-13 17:50:55 +03:00
nothing.repl
println.repl
README.md
repl_test.v escape os.exec('"$vexec"') to support directories with spaces 2019-10-16 02:49:51 +03:00
run.v tools: new tool to extracts function names declared in V files 2019-10-21 14:14:28 +03:00
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