vis - a neat vi-like editor

Age	Commit message (Collapse)	Author	Files	Lines
2016-04-21	Add test for file that does not exist	Josh Wainwright	2	-1/+16

2016-04-21	Use dofile() rather than require() to run lua test code	Josh Wainwright	1	-3/+3

2016-04-21	Add executable permission to test.sh	Josh Wainwright	1	-0/+0

2016-04-21	Update tests README and add lua tests README files	Josh Wainwright	1	-0/+21

2016-04-21	Show vis version when running tests	Josh Wainwright	1	-0/+3

2016-04-21	Quit vis from within test visrc.lua	Josh Wainwright	2	-8/+4

2016-04-21	Use .status files instead of .true files and write error to .err file	Josh Wainwright	5	-12/+13

2016-04-20	Allow running individual tests from makefile	Josh Wainwright	1	-0/+5

2016-04-20	Split test lua code into individual test.lua files	Josh Wainwright	10	-145/+133

2016-04-20	Remove stackdump reference from makefile and make name uppercase	Josh Wainwright	1	-1/+1

2016-04-20	Add first set of basic lua api tests	Josh Wainwright	13	-0/+368
	There are two types of lua tests here: 1. Tests are formed from a <test>.in, <test>.ref and <test>.out triplet. The <test>.in file is opened by vis, some operatations are performed and the modified file is written to <test>.out. The new <test>.out is compared to <test>.ref and the test passes if they are identical. 2. Tests are formed from a single <test>.true file. This file is created by the lua code in the test. It contains a single line per test case, this single line should be `true` if the test case passed. The <test>.true file is checked to ensure it contains only `true` lines and if so, the test passes.