Dear list,
I can't figure out how to use fixtures with attachment_fu. I know how
to use files with RSpec in my controllers,
BackgroundPhoto.create(:uploaded_data => fixture_file_upload("files/
some.zip", "application/x-zip")), but this does not work with
fixtures(obviously). More important
although i primarily use mercurial, bazaar (http://bazaar-vcs.org/) is
also worth a mention
On Jan 27, 2008 4:42 PM, Chad Humphries <[EMAIL PROTECTED]> wrote:
> A good thing to note is that you can run many of the distributed scm tools
> in a 'svn wrapper' mode to ease transition with existing rep
We recently started using git on our project. It still uses a svn
repository and we enjoy the use of the git-svn bridge to synchronize
things. There are a few things we haven't figured out how to do yet
with git-svn:
* create tags or branches
* commit to tags or branches
* see the filenames of fil
Yes, bazaar deserves extra props because it's the scm powering a lot of the
Ubuntu integration projects. It's open source (I think they pretty much all
are) but its development is sponsored by Canonical, which is the company
behind Ubuntu.
I can't remember why I ditched bazaar - I think it was bec
Been a month since I've rspec, I think you can place the stubs here.
@user = mock_model(User,
login => "",
email => "",
password => "",
password_confirmation => ""
)
@account = mock_model(Account,
subdomain => "",
company_name => "",
filename => ""
)
On Jan 28, 2008 2:36 PM, Chris Olsen <[EMAIL
I'm starting a new project and I want to try writing the client first. I.e. I
want to write my 'views' first and I would like to mock out all the models in
such a way that I can run the site and browse it with the mocked out models. Is
it easy to use rspec's mocking for this sort of thing and ha
awesome
Nathan Sutton
[EMAIL PROTECTED]
rspec 1.1
rspec_on_rails 1.1
rails 2.0.2
On Jan 28, 2008, at 5:24 PM, Jay Donnell wrote:
> I apologize, I oversimplified for the sake of brevity. We have most
> of the models written but there are some pieces than aren't and
> won't be written in the n
In a create controller method I am testing the else clause that occurs
when the model is unable to be saved. Sounds simple enough, but because
model is created before the save and the form has to be re-filled I now
have to stub a model and all the attributes. Since the error messages
are displaye
I apologize, I oversimplified for the sake of brevity. We have most of the
models written but there are some pieces than aren't and won't be written in
the near future. I wanted to mock them out in some form so we can implement
those portions of the views. Things like certain features of the sid
On Jan 28, 2008 12:01 PM, Jay Donnell <[EMAIL PROTECTED]> wrote:
> I'm starting a new project and I want to try writing the client first. I.e. I
> want to write my 'views' first and I would like to mock out all the models in
> such a way that I can run the site and browse it with the mocked out m
Good point. I guess it was the account.user, account.users.build and
all the validation methods that I thought may be unnecessary.
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/ma
sorry about that, I have no idea how that happened. It looked fine in yahoo
mail before I sent it :/
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.y
Along these lines, I also think that a empty spec should be failing or
at least pending.
On Jan 27, 2008, at 6:50 AM, Matt Darby wrote:
> Ah, I was unaware of this. Thanks for the pointer.
>
> On Jan 27, 2008, at 2:42 AM, Francois Wurmus wrote:
>
>> Hi Matt,
>>
>> one way of doing this is to l
On Jan 28, 2008 5:42 PM, James Deville <[EMAIL PROTECTED]> wrote:
> Along these lines, I also think that a empty spec should be failing or
> at least pending.
+1
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo
On Jan 28, 2008 3:24 PM, Jay Donnell <[EMAIL PROTECTED]> wrote:
> I guess I can use dummy methods in my models that simply return some canned
> result. Maybe even name it 'my_method_dummy' so I can easily track down the
> dummy methods. The stubbing syntax is so clean In rspec that I was hoping I
15 matches
Mail list logo