Actions

icon Post
text/html Subscribe
text/html Unsubscribe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qmtest] QMTest plans


  • To: qmtest@xxxxxxxxxxxxxxxx
  • Subject: Re: [qmtest] QMTest plans
  • From: "Rodrigo Belem" <rclbelem@xxxxxxxxx>
  • Date: Mon, 2 Apr 2007 19:14:37 -0400

Rodrigo Belem wrote:
> Hello everybody,

Thanks for pointing out the ExceptionTest issue. I'll look into it more, since
I don't yet
understand what change in Python's exception handling causes it. (And yes, I
would appreciate
any solution you may already have come up with !)


I'll look deeper to code a solution :-)

> Would you like to receive patches changing the code to use some PEPs (Python
> Enhancement Proposals)?
> My suggestions are the pep-0008[0], pep-0257[1], pep-0290[2].

From looking at the PEPs you mention I take it you are most interested in
stylistic cleanup (as
opposed to new features, or fixes to open issues). Correct ?


Yes, for now just stylistic cleanup. I think doing by this way I'll
learn the code and the code maintenance will become easier. After this
I'll be ready to do another things.

> And how about changing modules to use subprocess[3] as a command
> executer, and other similar changes?

As much as I'd appreciate any cleanup, it is important to remain backward
compatible (such as with
Python 2.3, which doesn't have the subprocess module).


A python version verification could be done to select the module to
use. We can place some warning messages that qmtest will work with
python from 2.4. What do you think?

> BTW, any plans to release a new version? When?

There are no concrete plans (neither concerning any date, nor a feature set).
I'm currently working on a new GUI (still using some Zope modules) that will
hopefully be
more flexible and easy to customize.
I also have a new 'Expectation Database' type in the works that allows to more
flexibly
and conveniently handle expectations and the way they are specified and stored.
Finally, there is some efford going into API cleanup.

If you have any particular things you'd like to see enhanced in QMTest, I'm
very much interested
to know about them. (Contributions are certainly appreciated, too, though it
would be good to
coordinate first to avoid to waste anyone's effort.)


There is another interesting project[0] that you can get some ideias.
I know almost all source code.


I have another thing to ask you. Could you setup an access to the svn
via https webdav?



Thanks,


Rodrigo Belem.


[0] http://pyret.sf.net