vis - a neat vi-like editor

Age	Commit message (Collapse)	Author	Files	Lines
2017-03-03	test/lua: add infrastructure for busted based unit tests	Marc André Tanner	1	-6/+21

2017-01-12	tests: make :help output actually visible	Marc André Tanner	1	-1/+1
	The problem is that :qall in the win open event would immediately close the window before anyting gets executed.
2016-11-17	test: use :qall! to terminate tests	Marc André Tanner	1	-1/+1
	This should make sure that vis always terminates and never hangs waiting for further input. Lua errors in particular cause a new window/file to be displayed showing a detailed error message. Previously only this internal file was closed but the original file remained open and prevented vis from exiting.
2016-11-15	test/lua: make tests more robust, print Lua include paths	Marc André Tanner	1	-4/+6

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

2016-04-21	Quit vis from within test visrc.lua	Josh Wainwright	1	-6/+3

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

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