History

Alexander Medvednikov 7456d556e1 fix 2 repl tests		2019-12-18 05:02:23 +03:00
..
runner	enable alpine/musl CI tests	2019-11-28 11:46:52 +03:00
.gitattributes	…
.gitignore	…
README.md	…
arr_decl.repl	…
bad_in_type.repl	parser: check types in `a in b` expressions	2019-12-04 22:17:24 +03:00
chained_fields.correct.repl	…
chained_fields.repl	fix 2 repl tests	2019-12-18 05:02:23 +03:00
conditional_blocks.repl	…
default_printing.repl	…
empty_struct.repl	…
error.repl	…
error_nosave.repl	…
function.repl	…
immutable_len_fields.repl	fix 2 repl tests	2019-12-18 05:02:23 +03:00
interpolation.repl	…
multiple_decl.repl	…
multiple_println.repl	…
naked_strings.repl	…
newlines.repl	…
nomain.repl	…
nothing.repl	…
option.repl	foo()? test	2019-11-18 12:11:25 +03:00
println.repl	…
repl_test.v	testing: support for internal module testing	2019-12-14 15:57:28 +03:00
run.v	enable alpine/musl CI tests	2019-11-28 11:46:52 +03:00
var_decl.repl	…

README.md

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