similar to: Using RSpec to drive the design of a GUI desktop application

Hello, First of all I''m new to working with sockets, so the problems I''m having are probably because of my lack of understanding. What I''m trying to accomplish is to create a mac os x client gui to ruby-debug. When a application that includes ruby-debug is started, it starts listening for 2 connections; 8989, 8990 The connection is made by calling the connectToApp

I''m doing a redirect in one of my controller actions and somehow I can''t spec it, see this pastie: http://pastie.caboo.se/53120. When following the link from a browser I''m being redirected to the right page. -------------- next part -------------- An HTML attachment was scrubbed... URL:

I really would like to know how people are using the Story and Example runner to write their software.It would be great to get some direction on it, because I think I''m missing some points. Taking the outside-in approach in thought: At first we write a high-level customer-facing story, this story fails. Then we start using mocks at object level to use them as a design tool, and so we

Many posts on this list are about using RSpec with Rails and that''s the way I''m also using RSpec all the time. Unfortunately there isn''t that much info about using RSpec for standalone Ruby projects. I must admit I''m really having a hard time writing the very first example(s) for a fresh standalone Ruby project. I haven''t really got a clue where to

Hello, I''m scheduled to give a rspec brown bag this Wednesday (11/22) for my company (Pivotal Computer Systems, http://www.pivotalsf.com). I did see Dave Astel''s talk as well as several of my coworkers. The developers at my workplace are experienced Agile developers. What would be some good things to focus on for this brown bag? Are there slides to presentations that would be

I wanted to use ARTS to add RJS in a behaviour driven way to my application, but I''m having some trouble asserting a replace_html with a partial. I''ve created a pastie (http://pastie.caboo.se/60694) which contains the RJS I want to spec, the spec which I already wrote and its failure message. I''m currently using RSpec-0.9.2

Why can''t I use the RESTful route helpers in my specs? In my controller I''m doing a redirect: redirect_to list_path(:id => @item.list_id) Now when I write: controller.should_redirect_to list_path(:id => 2) I''m getting the following error: NoMethodError in ''POST on /lists/2/items should redirect to index on succesful POST'' You have a nil object

Behind every great release is a maintenance release. Go get it while it''s hot. We''ve also reworked the website a little - trying to scare off fewer people. Aslak

<http://www.apress.com/book/bookDisplay.html?bID=10368> Came across this as a stub page browsing Amazon UK. This is good news! I''m surprised it hasn''t been discussed on the list before. Was Chad keeping it a secret? I hope it will have plenty of BDD theory. I''m still waiting for that magic book I can give to someone and say "here - read this, it

Hi! I wonder does anybody planning to go beyond the default html formatter/report? The current html report is nice and green but what about to go a little silly and enable also user input. For example to let customer to add a new pending spec, comments etc. I feel it might be mentally easier for some customers to jump into spec world when it is possible to give input at "the same

I''ve decided that I want to use more automated tests because I''ve been intrigued by the idea of BDD. I am new to using tests, so I''m curious if there have been any writeup on using rSpec. This is one of the only ones I''ve found: http://blog.teksol.info/articles/2005/11/17/building-a-plugin-on-rspec It seems that the benefit of BDD is that it makes it

Disclaimer: The following are observations by a relatively new user (couple of weeks) of RSpec and not intended as RSpec trollbait. Also, forgive me if similar topics have been discussed elsewhere on the mailing list. I at least did the due diligence of a quick search. That said... I''ve been positively thrilled with RSpec for use outside of Rails. It has been in my attempts

Would it be desirable to have before and after take a spec name as well as :each and :all? Scott

Hello! I''m pretty new to unit testing, and have only been using RSpec for a few weeks. I found that for my controller specs, my setup methods were getting very long building mocks/stubs for all the model objects I needed to work with. I''ve started creating helpers like the following for each of my models. The "min_" methods are short for "minimum", and

Hi all ! I just started writing specs on a new project. I would just like to validate that this is the way you would write it. I know about mocks, stubs and expectations. I don''t think this is a problem for me. My question really boils down to: def index @projects = current_user.projects.active end My spec needs to return the proxy, no ? Here''s my code: context "A

I posted a quick screencast demonstrating some BDD with RSpec yesterday: http://wincent.com/a/about/wincent/weblog/archives/2007/05/ behaviourdriven.php I''m a C/Objective-C programmer who knows a bit of Ruby, almost nothing about Rails, and in BDD I can really only claim "new but interested" status. It''s not scripted, it''s totally improvised and

The RSpec Development Team is pleased to announce the release of RSpec-1.0.8. RSpec 1.0.6 is the "holy cow, batman, it''s been a long time since we released and there are a ton of bug fixes, patches and even new features" release. RSpec 1.0.7 and 1.0.8 deal with a regression introduced in 1.0.6 and a hiccup in releasing 1.0.7, respectively. == RSpec RSpec is a Behaviour Driven

While the spirit of BDD is to spec first and code second, many of us have legacy code. Worse, some of us have legacy code without very good coverage. Recognizing that *I* have such code, I created a script that grinds through your .rb files and creates placeholder specs for each public method. While it is more sensible to spec behavior of code function than of individual methods, this

I can understand that it''s easier for rspec to set up a mock in advance of the controller call. But it makes it difficult to do something like: context "The HarkController, given Louie the logged-in user" do setup do post :login, :username => ''louie'', :password => ''atest'' end specify "should redirect Louie to the home

It seems to me that the RSpec bundle''s ''it'' snippet is in need of some love. By default, a newly inserted spec passes. This seems odd as it is misleading. It also makes it harder find what specs still need to be completed if you return to an RSpec module after a break. I propose that the ''it'' snippet is changed to the following: it