Lib Specs and config.use_transactional_fixtures = true

Hi

We have specs in our rails project other than model/view/controller …
we have interests and lib …

using use_transactional_fixtures = true seems fine in a spec in the m/
v/c and interests directories but not in lib

Just wondered if anyone had any quick thoughts as to why that may be???

Shane M.
ELC Technologies ™
1921 State Street
Santa Barbara, CA 93101

Phone: +64 4 568 6684
Mobile: +64 21 435 586
Email: [email protected]
AIM: ShaneMingins
Skype: shane.mingins

(866) 863-7365 Tel - Santa Barbara Office
(866) 893-1902 Fax - Santa Barbara Office

+44 020 7504 1346 Tel - London Office
+44 020 7504 1347 Fax - London Office


Privacy and Confidentiality Notice:
The information contained in this electronic mail message is intended
for the named recipient(s) only. It may contain privileged and
confidential information. If you are not an intended recipient, you
must not copy, forward, distribute or take any action in reliance on
it. If you have received this electronic mail message in error, please
notify the sender immediately.

On Fri, Mar 14, 2008 at 1:31 AM, Shane M. [email protected]
wrote:

Hi

We have specs in our rails project other than model/view/controller …
we have interests and lib …

using use_transactional_fixtures = true seems fine in a spec in the m/
v/c and interests directories but not in lib

Just wondered if anyone had any quick thoughts as to why that may be???

This should answer your question:
http://rspec.info/documentation/rails/writing/.

On 14/03/2008, at 10:14 PM, David C. wrote:

v/c and interests directories but not in lib

Just wondered if anyone had any quick thoughts as to why that may
be???

This should answer your question:
http://rspec.info/documentation/rails/writing/.

Thanks, that was helpful to know. It did not seem to be the issue I
was having though, the specs in lib causing the problem were using
before(:all) to setup database records … changed to use (:each) and
all was happy in the land of nod … that was the difference between
the specs in lib and interests … so not sure what I may be losing
(and not know it) without doing something like :behaviour_type
=> :model … I do suspect that may have been why I could not use
mock_model in a spec once … will have to find that example sometime
and look.

Thanks again

Shane

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs