From: Robert Dober <robert.dober@...>
Date: 2006-08-29T00:21:23+09:00
Subject: Re: Readline and StringIO

------=_Part_174067_24718721.1156778480301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 8/28/06, David Vallner <david@vallner.net> wrote:
>
> Eero Saynatkari wrote:
>   > I was merely wondering if there is any reason for the
> > T_FILE check in Readline (as opposed to a more permissive
> > one) since that would be the easier solution.
>
> Change the check and see if there is a reason?
>
> Personally, I'd avoid unit-testing with simulating interactive input.
> Unless you're unit-testing the readline library / binding. Maybe you're
> missing an abstraction layer between user input and your program logic?
>
> At least I thought unit testing was supposed to test the core logic
> modules, where you can just feed them with your specific data or
> environment. Testing at the interface level doesn't seem like
> unit-testing to me, and you probably want tools like expect to get
> decent coverage from that approach.
>
> David Vallner
>
>
I am afraid that this comes from the difficulties to automate testing at
that level ( and OP is just fighting with one of the many problems to
solve),
but certainly interactive input treatement is a very worthy unit to test.

Cheers
Robert

--=20
Deux choses sont infinies : l'univers et la b=EAtise humaine ; en ce qui
concerne l'univers, je n'en ai pas acquis la certitude absolue.

- Albert Einstein

------=_Part_174067_24718721.1156778480301--