I have redone the sfPropelTestPlugin, and it is now sfModelTestPlugin, with support for Doctrine and Propel 1.3! Also new - you can now specify the test data file/directory at runtime, allowing for more flexibility with your tests. I want to thank Anders Betnér and my readers for bug reports and patches!
6 Comments Add your own
1. rpsblog.com » A wee&hellip | November 19th, 2007 at 8:41 am
[...] sfModelTestPlugin – Simple unit tests for any ORM! [...]
2. Ben XO | November 19th, 2007 at 10:02 am
Hi Rob,
I've patched sfModelTestPlugin to support lime colours etc.
The patch is at http://trac.symfony-project.com/ticket/2554
3. Ben XO | November 21st, 2007 at 11:38 am
I've also patched sfModelTestPlugin to allow much more flexible fixture handling. See http://trac.symfony-project.com/ticket/2564
That patch sits on top of my lime colours patch.
4. Symfony.es » Blog A&hellip | December 3rd, 2007 at 5:30 am
[...] sfModelTestPlugin – Simple unit tests for any ORM! [...]
5. megazlo | January 18th, 2008 at 7:19 am
I think this is good idea to add in your module next class:
class sfModelTestBrowser extends sfTestBrowser
{
/**
* Initializes the browser tester instance.
*
* @param string Hostname
* @param string Remote IP address
* @param array Options
*/
public function initialize($fixturesFileOrDir = null, $hostname = null, $remote = null, $options = array())
{
sfBrowser::initialize($hostname, $remote, $options);
$this->test = new sfPropelTest($fixturesFileOrDir);
}
};
It's will replace standart sfTestBrowser for functional test with database access.
6. jason rowe | August 30th, 2008 at 12:21 pm
Hi, looks like this is exactly what i need but wont install in v1.1. Any plans to update the plugin to support symfony 1.1?
Thanks
Jae.
Leave a Comment
Please: No emoticons or excessive punctuation.Trackback this post | Subscribe to the comments via RSS Feed