Rake tasks for running plugin tests - fixtures clash with other plugins
Reported by Gary Taylor | August 21st, 2008 @ 11:01 PM
I have a few plugins installed in my application (betternestedset is one of them) which have a 'test/fixtures' dir which they use themselves. They are not engines plugins, therefore engines should not try to use these fixtures. Perhaps have the rake tasks so that the setup_plugin_fixtures could be passed an argument to specify which plugin to work on ? Alternatively, could the code work out which plugins are engines plugins and which are normal ?
Cheers
Gary
Comments and changes to this ticket
-
James Adam August 22nd, 2008 @ 12:03 AM
There's no way of distinguishing an "engines" plugin from any other - this is by design - so I'm not sure how we'd prevent interaction.
What's the actual problem you're experiencing?
-
Gary Taylor August 22nd, 2008 @ 12:10 AM
When I try to run the tests from the rake command, it goes away and creates the fixtures in the temp directory. But it includes the fixtures which I dont want from these other plugins. There are no migrations for the tables that these fixtures need, therefore the fixtures loading fails as a result.
If that makes sense ?
I have done a frig now in my test, where I change the temp directory for these fixtures, then I ask the Engines::Test module to generate the fixtures just for my plugin. This works fine, but it means I will never be able to use the rake commands
Cheers
Gary On 22 Aug 2008, at 11:03, Lighthouse wrote:
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
The rails engines plugin itself
