Writing test cases are always a nice way for new comers to get their feet wet
in a new, large project. Then have a newbie/mentor structure. Mentor guides the
development of test cases. New comers will learn how to test their code.> From:
william_a_adams@xxxxxxxxxxx
To: luajit@xxxxxxxxxxxxx
Subject: RE: LuaJIT project governance
Date: Wed, 19 Aug 2015 19:00:29 +0000
shall we start a github issue for "test case development"?
===============================
- Shaping clay is easier than digging it out of the ground.
----------------------------------------
Date: Wed, 19 Aug 2015 21:55:35 +0300
From: turotl@xxxxxxxxx
To: luajit@xxxxxxxxxxxxx
Subject: Re: LuaJIT project governance
On Wed, 19 Aug 2015 18:40:56 +0000
William Adams <william_a_adams@xxxxxxxxxxx> wrote:
Also there are cases where a bug crashes or hangs the interpreter.
test framework?
Or at least a simple agreement on "returns 0 == success, returns '1'
== failure", or something?
There must be some kind of non-lua test harness which catches those.
There were several such bugs in the past and they should be in the test
suite to prevent their re-occurrence.
