Kay Schluehr wrote:

>>Sounds interesting. Is this code, or examples of its use, available?
>
>
> Sure, it's part of EasyExtend. See also www.fiber-space.de

OK. So the ULR for the documentation of consoletest is:
http://www.fiber-space.de/EasyExtend/doc/consoletest/console test.html

It has a recorder and a player. As does Metatest (developed later and
independently). I think that is a good concept. Other frameworks use
def test_something(...):
# assertions go here
as their recorder. Such a recorder cannot do very much at all.

> Checkout the documentation for consoletest. I guess in the current
> release recording and replaying can't be done in the same
> run. I've got a corrected version on my disk but I didn't uploaded it
> yet and corrected the docs.

<snip>

> there is no fundamental reason why it can't be separated from
> eeconsole.py.

OK. That might be a good idea.

<snip>

> How does metatest analyze the tested expression? Lets say I try to
> check this expression
>
>>>>plus( f(1) == True, f(2) != False) == plus( f(2) == True, f(1) != False)
>>>

This won't work. In fact, even though
plus(2, 2) == 4
works
4 == plus(2, 2)
won't. (Not so odd. We have (a+b) != (b+a) when a and b are distinct
strings. Metatest works by overloading the == or __eq__ operator.)

However, in practice I don't think this is a problem. And if it is,
then there should be a nice solution. I hope that the tests we want to
write are the same as the ones Metatest allows us to write.

My goal is to finding the simplest way, using Python syntax, to express
or state the test we wish to run, and to then code Metatest to give the
required meaning to he statement.

<snip>

--
Jonathan