vis - a neat vi-like editor

Age	Commit message (Collapse)	Author	Files	Lines
2017-03-04	test/lua: convert tests to busted infrastructure	Marc André Tanner	1	-3/+2

2017-03-03	test/lua: add infrastructure for busted based unit tests	Marc André Tanner	1	-13/+14

2017-02-14	Skip tests if Lua support is not compiled in	Marc André Tanner	1	-0/+5

2016-12-30	Revert "Make sure that info messages are printed before test case is run"	Marc André Tanner	1	-3/+2
	This reverts commit 8a366cebda597e960f1f49e245785f8fdedff0a6. Travis is strange.
2016-12-28	Make sure that info messages are printed before test case is run	Marc André Tanner	1	-2/+3
	Useful for hanging tests also redirect stdout to /dev/null for better output on Travis.
2016-12-19	test: ignore custom visrc.lua configuration	Marc André Tanner	1	-2/+1

2016-11-16	test/lua: redirect stdin and stderr to /dev/null	Marc André Tanner	1	-1/+1
	Redirecting stdin mimics the environment on Travis CI. Redirecting stderr should give a nicer test list output, albeit some useful messages might get lost.
2016-11-15	test/lua: make tests more robust, print Lua include paths	Marc André Tanner	1	-4/+3

2016-11-13	test/lua: print :help output and distinguish between fail/error	Marc André Tanner	1	-1/+2

2016-04-26	test/lua: make test.sh executable again	Marc André Tanner	1	-0/+0

2016-04-26	Remove .status files, just use .ref and .out pairs	Josh Wainwright	1	-9/+0

2016-04-26	Change shebang to sh and add quotes to variables in script	Josh Wainwright	1	-10/+10

2016-04-26	test.sh: silently compare files	Josh Wainwright	1	-1/+1

2016-04-21	Add test for file that does not exist	Josh Wainwright	1	-1/+1

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

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	1	-2/+1

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

2016-04-20	Split test lua code into individual test.lua files	Josh Wainwright	1	-24/+29

2016-04-20	Add first set of basic lua api tests	Josh Wainwright	1	-0/+42
	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.