Well, it's not exactly the same. I'm interested in this topic as well, as I would just like to run symfony test:all when I develop a plugin which displays a list of 'ok's and 'not ok's. Otherwise I have to manually run all 'php ...' commands every time I want to test the whole suite.
A different thing that isn't really supported very well is functional testing of plugins using 'fixture projects'. It's done like that in the symfony project, where inside the /test/functional/... directories reside projects just for the purpose of one functional test. Is this possible to do as well during plugin development?
Again, I just would like to run 'symfony test:functional' in this case.
> Well, it's not exactly the same. I'm interested in this topic as well,
> as I would just like to run symfony test:all when I develop a plugin
> which displays a list of 'ok's and 'not ok's. Otherwise I have to
> manually run all 'php ...' commands every time I want to test the
> whole suite.
+1 for this. It makes plugin testing much easier and gives you a
consistent behavior when testing plugins, your app, etc.
On 8 Aug., 15:39, "Bernhard Schussek" <bschus...@gmail.com> wrote:
> Well, it's not exactly the same. I'm interested in this topic as well,
> as I would just like to run symfony test:all when I develop a plugin
> which displays a list of 'ok's and 'not ok's. Otherwise I have to
> manually run all 'php ...' commands every time I want to test the
> whole suite.
> A different thing that isn't really supported very well is functional
> testing of plugins using 'fixture projects'. It's done like that in
> the symfony project, where inside the /test/functional/... directories
> reside projects just for the purpose of one functional test. Is this
> possible to do as well during plugin development?
> Again, I just would like to run 'symfony test:functional' in this case.
This would be easy enough to implement in a plugin if sfBaseTask didn't override the events dispatched in sfTask... Is there any chance of restoring those events for symfony core events?
Kris
On Aug 8, 2008, at 6:39 AM, Bernhard Schussek wrote:
> Well, it's not exactly the same. I'm interested in this topic as well, > as I would just like to run symfony test:all when I develop a plugin > which displays a list of 'ok's and 'not ok's. Otherwise I have to > manually run all 'php ...' commands every time I want to test the > whole suite.
> A different thing that isn't really supported very well is functional > testing of plugins using 'fixture projects'. It's done like that in > the symfony project, where inside the /test/functional/... directories > reside projects just for the purpose of one functional test. Is this > possible to do as well during plugin development?
> Again, I just would like to run 'symfony test:functional' in this > case.
> Kind regards, > Bernhard
> On Thu, Aug 7, 2008 at 5:32 PM, Carl Vondrick > <carl.vondr...@symfony-project.com> wrote:
>> I normally execute the tests by hand. It's the same thing as if you >> used the test:* tasks.
> A different thing that isn't really supported very well is functional
> testing of plugins using 'fixture projects'. It's done like that in
> the symfony project, where inside the /test/functional/... directories
> reside projects just for the purpose of one functional test. Is this
> possible to do as well during plugin development?
can you explain this a bit more? in particular what do you mean by
"fixture projects"?
Take a look at the sfPropel plugin on the symfony library.
sfPropel/test/functional/fixtures contains a whole symfony project
structure, which have a schema.xml and several modules. This is a
fixture project that will be used during the plugins functional tests.
The functional bootstrap script build models and initialize a
temporary sqlite database for this project.
This job is done in this 'fixture' project's config file. (sfPropel/
test/unit/fixtures/config/ProjectConfiguration.class.php)
All the tests are then executed in a full project-wide context, with
real objects on a real db.
I tried to use the system mechanism on my own plugins, but I
experienced some conflits beetween the real project and the plugins's
fixtures one, when I use the symfony tasks.
I think this technique have to be sharpened for it to be promoted
outside the symfony core.
On 8 août, 20:34, klemens_u <klem...@ull.at> wrote:
> > A different thing that isn't really supported very well is functional
> > testing of plugins using 'fixture projects'. It's done like that in
> > the symfony project, where inside the /test/functional/... directories
> > reside projects just for the purpose of one functional test. Is this
> > possible to do as well during plugin development?
> can you explain this a bit more? in particular what do you mean by
> "fixture projects"?
