On Wednesday, December 3, 2014 at 18:19, Seth Morabito wrote:
> I meant unit tests in the Kent Beck sense of unit testing, i.e. code
> that is automatically run at or shortly after compile time to verify
> correctness of "units" (likely C functions, in this case).
I understand now, thanks.
> T
On Tuesday, December 02, 2014 at 8:38 PM, Phil Budne wrote:
> Mark Pizzolato wrote:
> > ... Running these needs some sort of scripting paradigm to load, start and
> examine the results of such tests.
>
> Over a decade ago I wrote a Tcl "expect" script to install ITS on a SIMH
> simulated KS-10 fro
* On Wed, Dec 03, 2014 at 02:27:33AM -0500, J. David Bryan
wrote:
> On Tuesday, December 2, 2014 at 19:54, Seth Morabito wrote:
>
> > SIMH is entirely without test suites, so of course I've had to forge
> > on ahead without that safety net.
>
> I'm not sure I understand your comment. Do you m
In article <201412030438.sb34cpyk078...@ultimate.com>,
Phil Budne writes:
> Mark Pizzolato wrote:
> > ... Running these needs some sort of scripting paradigm to load, start
> and examine the results of such tests.
>
> Over a decade ago I wrote a Tcl "expect" script to install ITS on a
> SIM
In article
<03006e3fc39b5a48ab9dbccc101090a8234493f...@redroof2.alohasunset.com>,
Mark Pizzolato - Info Comm writes:
> Well, if you're trying to 'test' a particular instruction implementation.
> You can drive that test with SCP commands which:
> 1) load some memory with the instruction to
In article <20141203015411.ga10...@loomcom.com>,
Seth Morabito writes:
> I'd love to see testing come to SIMH. It's never too late!
Me too. I have lots of experience retrofitting unit tests onto
existing code, so I can help out here.
I am very happy to see that simh is now on github! Thi
