webpost | 4 Mar 2009 15:19
Picon

Unit testing and Propel 1.3

Hi list,

I try to write as much unit test as possible when I develop, and this is especially true about models.

Until Propel 1.2, I could inspect the generated SQL code for the latest query via Creole. This is no more
possible in Propel 1.3, so my tests don't pass... and I can't upgrade to Propel 1.3.

I saw a fix to restore the $connection::getLastExecutedQuery() method in Trac
(http://propel.phpdb.org/trac/ticket/651), I wonder is there is any reason not to apply it?

Sylvain

------------------------------------------------------
http://propel.tigris.org/ds/viewMessage.do?dsForumId=1093&dsMessageId=1266948

To unsubscribe from this discussion, e-mail: [dev-unsubscribe <at> propel.tigris.org].

Hans Lellelid | 4 Mar 2009 21:50

Re: Unit testing and Propel 1.3

Hi Sylvain,

I think we should apply that patch; I'll raise it's priority so that it
gets applied quickly.

Hans

On Wed, 4 Mar 2009 06:19:25 -0800 (PST), webpost <at> tigris.org wrote:
> Hi list,
> 
> I try to write as much unit test as possible when I develop, and this is
> especially true about models.
> 
> Until Propel 1.2, I could inspect the generated SQL code for the latest
> query via Creole. This is no more possible in Propel 1.3, so my tests
don't
> pass... and I can't upgrade to Propel 1.3.
> 
> I saw a fix to restore the $connection::getLastExecutedQuery() method in
> Trac (http://propel.phpdb.org/trac/ticket/651), I wonder is there is any
> reason not to apply it?
> 
> Sylvain
> 
> ------------------------------------------------------
>
http://propel.tigris.org/ds/viewMessage.do?dsForumId=1093&dsMessageId=1266948
> 
> To unsubscribe from this discussion, e-mail:
> [dev-unsubscribe <at> propel.tigris.org].
(Continue reading)


Gmane