Re: [rspec-users] RSpec-2.0.0 is released!

What Aslak said. A lot. Good job indeed. Cheers, Dan On 11 October 2010 16:14, aslak hellesoy wrote: > > ## RSpec-2.0.0 has been released! >> >> > David, I'm so impressed how you have managed to manage a half-rewrite, > updating the RSpec book (which now soon goes to print) and coordinating >

Re: [rspec-users] RSpec makes me want to write better code

2008/9/26 David Chelimsky <[EMAIL PROTECTED]> > On Fri, Sep 26, 2008 at 12:18 PM, Mark Wilden <[EMAIL PROTECTED]> wrote: > > On Fri, Sep 26, 2008 at 9:47 AM, Ashley Moran > > <[EMAIL PROTECTED]> wrote: > > > > To me, spec'ing attributes is a red flag. It is not always a bad thing > or wrong, but i

Re: [rspec-users] RSpec makes me want to write better code

k Wilden <[EMAIL PROTECTED]> wrote: > >> On Sat, Sep 27, 2008 at 11:26 AM, Dan North <[EMAIL PROTECTED]> wrote: > >> > >>> It seems these conversations come up time and again because Rails > >>> overloads the idea of "model". In a Rails ap

Re: [rspec-users] What's the best way to test inherited behavior?

Another approach would be to prefer composition over inheritance, and either inject the server in a constructor (with a suitable name for the class) or mix it in as a module. Then you could describe the common server behavio

Re: [rspec-users] Rspec @ UC Berkley

That's actually a pretty awesome endorsement. We should put something on the website: Who is using rspec? 2008/10/9 Pat Maddox <[EMAIL PROTECTED]> > Scott Taylor <[EMAIL PROTECTED]> writes: > > > I find it sort of interesting that they are using RSpec in one of the > > courses @ UC Berkley: > >

Re: [rspec-users] features and form filling - going declarative?

Bit of a ramble, but see inline comments. Cheers, Dan 2008/11/7 Joseph Wilk <[EMAIL PROTECTED]> > David Chelimsky wrote: > >> On Fri, Nov 7, 2008 at 9:58 AM, David Chelimsky <[EMAIL PROTECTED]> >> wrote: >> >> >>> On Fri, Nov 7, 2008 at 9:54 AM, Matt Wynne <[EMAIL PROTECTED]> wrote: >>> >>>

Re: [rspec-users] cucumber feature description

2008/10/26 aslak hellesoy <[EMAIL PROTECTED]> > On Sun, Oct 26, 2008 at 3:56 PM, Stephen Eley <[EMAIL PROTECTED]> wrote: > > On Sat, Oct 25, 2008 at 7:19 PM, Ben Mabey <[EMAIL PROTECTED]> wrote: > >> > >> A more qualified person may want to answer your question, but my short > >> explanation of th

Re: [rspec-users] Musical Cucumber

2008/12/1 aslak hellesoy <[EMAIL PROTECTED]> > > > On Mon, Dec 1, 2008 at 11:00 PM, Joseph Wilk <[EMAIL PROTECTED]>wrote: > >> http://www.youtube.com/watch?v=U3OxKdDxkpg >> >> Sorry, I had to share that :) > > > Thank you! Fantastic. And for those who missed the kitten: > > http://aimee.mychores.c

Re: [rspec-users] Where to start after writing feature

Hooray! I've been looking for a reference for that quote for years! Thanks Andrew. 2008/12/7 Andrew Premdas <[EMAIL PROTECTED]> > "There are two ways of constructing a software design: One way is to make > it so simple that there are no obvious deficiencies, and the other way is to > make it so

Re: [rspec-users] [cucumber] Cucumber and CI

2009/2/24 aslak hellesoy > On Tue, Feb 24, 2009 at 10:30 AM, Rob Holland > wrote: > > On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne wrote: > > > >> You can even use git commit --amend to commit on red (e.g at the end of > the > >> day) and then change that commit later. > > > > While I think comm

Re: [rspec-users] Depot app, Demeter's law and troubles cleanly spe cing

2009/4/24 Stephen Eley > On Thu, Apr 23, 2009 at 2:19 PM, Fernando Perez > wrote: > > [...] > > # Assume an article with no comments and a params structure > # have already been set up in before(:each) > > it "should make a new comment belonging to the article" do > post :create, :comment => @m

Re: [rspec-users] BDD for C#?

Hi Brandon. I already replied on the BDD list but can I suggest you give the nbehave guys a poke, or even get involved in helping them out? If they started getting some releases out it would really help build some momentum around it. Cheers, Dan 2009/4/28 Brandon Olivares > > > > > -Origi

Re: [rspec-users] [cucumber] Setting a constant in step definition

2009/4/28 Andrew Premdas > I guess I'll just have to use a global, perhaps trying to freeze them in > production. Just thought there might be something that might be an > alternative. Might have a look at using a stub if that doesn't work. Thanks > for your input You could pass the value as a c

Re: [rspec-users] blog post on story runner

Pat, if you update from trunk and re-run the formatter, you'll get Given ... And ... instead of Given ... Given ... in the output. Great write-up - thanks for taking the time. Cheers, Dan Pat Maddox wrote: On 9/2/07, David Chelimsky <[EMAIL PROTECTED]> wrote: Here's an excellent blog pos

Re: [rspec-users] blog post on story runner

ven...And...And" would be more natural. Pat On 9/3/07, Dan North <[EMAIL PROTECTED]> wrote: Pat, if you update from trunk and re-run the formatter, you'll get Given ... And ... instead of Given ... Given ... in the output. Great write-up - thanks for taking the time. Ch

Re: [rspec-users] blog post on story runner

.And...And" would be more natural. Pat On 9/3/07, Dan North <[EMAIL PROTECTED]> wrote: Pat, if you update from trunk and re-run the formatter, you'll get Given ... And ... instead of Given ... Given ... in the output. Great write-up - thanks for taking the time. Cheers,

Re: [rspec-users] Reason for _spec.rb convention

Ashley Moran wrote: On 3 Sep 2007, at 15:37, David Chelimsky wrote: But it is an interesting idea that we should stay open to. Perhaps more compelling reasons for such a change will appear in the future. I like the sound of .spec in a way. It shortens the filenames which is always

Re: [rspec-users] Content assist for spec files

I'd like to try it too. I'd like an ide with half-decent ruby refactoring support. Geoffrey Wiseman wrote: On 9/5/07, *Tor Norbye* <[EMAIL PROTECTED] > wrote: I'm working on Ruby support for NetBeans, and we're bundling RSpec (along with JRuby). Would be pl

Re: [rspec-users] Standardize environment between specs containing class defs

Although it would be nice (and not too difficult) to have the example runner intercept any class creation (and perhaps other global/constant definitions) and undef them after each example. It certainly seems reasonable to have any defined classes go away after an example. aslak hellesoy wrot

Re: [rspec-users] given_it

I have to agree with David. (It's in the contract ;) Scenarios are reusable as steps in order to chain multiple scenarios together (to describe the various coarse-grained stages of a workflow, state machine or wizard, for example). At an example level it is just confusing. I've noticed that i

Re: [rspec-users] Getting Started with Story Runner

Hi James. James Hughes wrote: Your code looks correct. My interpretation of the workflow that derives from this tool is that you write a high level story like you have here, run it, and let it tell you what to do next. The stack trace is telling you that you need an Account class. So now you wo

Re: [rspec-users] Posted this in "dev" last night but I'm not sure that anyone reads it

Hi Jonathan. The pending method uses an exception to fail fast out of the step, but the runner knows it's a special case so it treats it accordingly. That's why pending steps or scenarios are reported differently from failures in the runner. It would be easy to reimplement pending using Ruby's thr

Re: [rspec-users] simple story, extract link

Hi Jonathan. You can think of the What's in a Story article as trainer wheels. The point is to start thinking in givens, events and outcomes (ie. which activities in this scenario are setting up context, which are the "interesting bits" and which are verification). Once you are comfortable with t

Re: [rspec-users] Story Runner: Readability of output with multiple params

Or even: And "the user", "Joe", "works for", "Acme", "as a", "janitor" so the params are inline. On 10/13/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > > On 10/13/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > > On 10/12/07, Tasty <[EMAIL PROTECTED]> wrote: > > > > > > Fistly, many, many

Re: [rspec-users] Story Runner: Readability of output with multiple params

Of the options on the table, I prefer "using $placeholder values" because then it tells me the role the value plays in the sentence. Even Pat's version works by defining the $placeholders outside of the step. In a "library" somewhere (we still need to define what a story/step library is or looks l

Re: [rspec-users] plain text stories

Haha - brilliant! I was just putting something together myself based on the original thread but it looks like Pat has a) beaten me to it and b) made it look really elegant. Nice work. I love it when a community discussion turns into something as cool as this. And so quickly too :) Cheers, Dan On

Re: [rspec-users] plain text stories

Of course when I said "Pat", I in fact meant "David and his monkey" :) On 10/22/07, Pat Maddox <[EMAIL PROTECTED]> wrote: > > On 10/22/07, Dan North <[EMAIL PROTECTED]> wrote: > > Haha - brilliant! I was just putting something together myself based on

Re: [rspec-users] How is everyone structuring stories?

For some reason I heard that reply in Eric Cartman's voice. "beh... you guys" fwiw I prefer separate directories - stories and specs - because they are targeted (intentionally) at different audiences. I started off trying behaviour/specs and behaviour/stories but then I thought about who would a

Re: [rspec-users] Plain Text Story example

gt; wrote: > >> David Chelimsky wrote: > > > > > > > >>> ... the philosohy that Dan is > >>> espousing: expressing stories in the business domain rather than the > >>> UI domain (btw Dan, that was brilliantly put). > >> What ex

Re: [rspec-users] Plain Text Stories Chaining Scenarios

Hi Nathan. You can reuse a scenario as a given in another scenario: Scenario "passing go" Given "I am not in jail" When "I pass go" Then "I collect $200" Scenario "landing on someone's hotel after passing go" * GivenScenario* "passing go" *# matches the scenario name* When "I land on s

Re: [rspec-users] helper methods starting with should

+1 for keeping should prefix given the number of people who write helper methods starting with "should" (at last count, one person) versus the number of people who find it useful starting test methods with the word "should" in xunit testing frameworks (nearly everyone I know). Obviously my world is

Re: [rspec-users] Mocks? Really?

I prefer the mantra "mock roles, not objects", in other words, mock things that have behaviour (services, components, resources, whatever your preferred term is) rather than stubbing out domain objects themselves. If you have to mock domain objects it's usually a smell that your domain implementati

Re: [rspec-users] Mocks? Really?

ut in Java MVC web apps I would *want* the controller examples failing if the model's behaviour changed in a particular way, so I can't think of a reason why I would want fake domain objects. Like I said, I'll have a proper think and get back to you. Cheers, Dan On Dec 15, 2007

Re: [rspec-users] OT local version control?

I can see this descending into a mercurial vs git religious war :) Hi Corey. I'm using mercurial for both home and work use (supplementing some of subversion's shortcomings, mainly around merging). I looked (briefly) at git and - less briefly - at darcs. I settled on mercurial for purely non-scien

Re: [rspec-users] OT local version control?

h 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 > repositories. That > > made

Re: [rspec-users] Textmate RSpec Bundle 'it' snippet

Warning - bit of a ramble below! On 29/01/2008, Edvard Majakari <[EMAIL PROTECTED]> wrote: > > > Not if you fill it out...and the BDD way is to write one example at a > > time, not a complete spec beforehand. > > I've done it this way too (being lazy), but is it really good thing? > Often I get mo

[rspec-users] outside-in BDD vs writing examples up front

ge in the original thread. -- Forwarded message -- From: Dan North <[EMAIL PROTECTED]> Date: 29 Jan 2008 23:35 Subject: Re: [rspec-users] Textmate RSpec Bundle 'it' snippet To: rspec-users Warning - bit of a ramble below! On 29/01/2008, Edvard Majakari <[EMAIL PROTECTED

Re: [rspec-users] OT local version control?

Hi Corey. I recently discovered a rather excellent online book: http://hgbook.red-bean.com/ It's about mercurial but it's a) largely scm-agnostic and b) really well written, with some useful diagrams about how changesets work in the small and collaboration models in the large (i.e. exactly what y

Re: [rspec-users] What is your workflow? Or how to use the story runner the right way.

Thanks Chris. This is a really nice description of how I think of BDD. I call it "we should fix that" after Liz Keogh's blog post: http://sirenian.livejournal.com/42871.html (Check the comments for the myriad ways you can misinterpret this!) Cheers, Dan On 04/03/2008, Chris Parsons <[EMAIL PROTE

Re: [rspec-users] My argument constraints are not working.

Devs, can we update the website and change all references to "David Chelimsky" to be "Chelim-baby" please? Should I post a ticket? On 30/03/2008, David Beckwith <[EMAIL PROTECTED]> wrote: > > Well, it turns out I was right. it was a newbie error. > > As soon as I wrote the test that you sugge

Re: [rspec-users] Welcome Pat Maddox

Let me join everyone else in welcoming you to the rspec developer team. As a notorious non-completer-finisher I can't begin to tell you how pleased I am to see you joining the team, especially given the clarity and high quality of your contributions on this list. Cheers, Dan On 05/04/2008, Zach D

Re: [rspec-users] newbq: Organizing your stories

I like this. It's pretty much one folder per stakeholder. If you have a question about a story or if a scenario starts failing, you immediately know who to ask whether it matters. I'm more and more coming round to this model on an ideological level. It seems a more natural grouping (and more tangi

Re: [rspec-users] rspec + github == !submodules

With mercurial I nearly did a similar thing, working on my own but committing from two different machines. Luckily mercurial gave me a warning that allowed me to make sense of what I was doing. Not sure how this works with git but here goes. 1. I push from laptop1 to my central server. All is good

Re: [rspec-users] BDD/Rails/Shoulda

Hi Matthew. I don't think it's off-topic at all. I would estimate around 80% of the traffic on this list is about "how do I test such-and-such with rails?". Rails is designed for a particular subset of web applications, namely ones that look a lot like basecamp. They mostly involve capturing, upd

Re: [rspec-users] Date comparisons

The (pretty much universal) problem with dates and times is that people use "date" and "time" to mean different things. There's a java library called joda that provides a really clean vocabulary around this. An *instant* is a point in time. You shouldn't be able to ask for two instants and get the

Re: [rspec-users] Reusing story snippets

The bottom line here is in understanding who is the stakeholder for this story - i.e. who cares about it, who will read it and who wants to know when it goes wrong. It seems to me you are using the construct of scenarios to describe machine interactions: the request and response of service invocat

Re: [rspec-users] Any news on the rSpec books?

>> >> On Fri, Aug 15, 2008 at 3:59 AM, Martin Bernd Schmeil >>> <[EMAIL PROTECTED]> wrote: >>> >>>> Any news on this? >>>> >>> >>> We've enlisted the help of three more authors: Dan North, Bryan >>> Helmkamp and Zach D

Re: [rspec-users] Do you remember RSpactor?

The runtime environment for OSX GUI apps is controlled by an (optional) file called ~/.MacOSX/environment.plist, which you can edit using the Property List Editor. Under the Root node you create key-value pairs like: GEM_HOME => /Users/Dan/Library/gems. Property List Editor won't let you create a

Re: [rspec-users] Documentation for Plain-Text Stories

As the author of the original scenario runner, if Aslak has come up with a nicer implementation - both in terms of design and hackability - then I say chuck my one out and use his :) As long as it is an easy adjustment (i.e. transparent or with an easy migration) for users of the current scenario

Re: [rspec-users] story vs feature (was Documentation for Plain-Text Stories)

At the risk of being a bit controversial... 2008/8/24 David Chelimsky <[EMAIL PROTECTED]> [...] > Sadly, "spec" has just as much baggage, if not more, as "test" does. > These days we're calling these things "code examples," (tongue > pressing into cheek) so maybe we should change the name to > rc

Re: [rspec-users] I want RSpec for CSS layout.

ooh, that would be lovely. LayoutBehave anyone? 2008/8/20 Matt Wynne <[EMAIL PROTECTED]> > +1 > > cheers, > Matt > > http://blog.mattwynne.net > http://songkick.com > > In case you wondered: The opinions expressed in this email are my own and > do not necessarily reflect the views of any f

Re: [rspec-users] BDDish rspecish question

This is one of the tiny-but-amazing details that makes me excited about cucumber. (That's one of those sentences you don't want blogged... "No, I meant cucumber the *framework*") Aslak has done some really cool stuff here - I don't think we've started to realise the power of combining tables and G

Re: [rspec-users] Four Question From an RSpec Baby - Give me something to chew

I think that's one of the nicest descriptions of the value of outside-in I've seen. Thanks Zach. 2008/9/5 Zach Dennis <[EMAIL PROTECTED]> > On Thu, Sep 4, 2008 at 7:14 PM, Nick Hoffman <[EMAIL PROTECTED]> wrote: > > On 2008-08-27, at 15:25, Mark Wilden wrote: > >> > >> The other thing I would sa

Re: [rspec-users] scenarios on production data

2008/9/8 Jonathan Linowes <[EMAIL PROTECTED]> > On 4 Sep 2008, at 18:55, Jonathan Linowes wrote: >> >> I'm just thinking out loud here... >>> It could be useful to have a way to run scenarios on a copy of a fully >>> populated production database, as an alternative to normal use. >>> Not sure how

Re: [rspec-users] Best practices for sharing state between story steps?

Hi Jim. I guess I'm not a purist then - that looks fine to me, and it's probably something I would consider doing too. The thing to bear in mind is that there is magic going on when you run steps. Each step in a scenario is run in the context of the same object instance (which you don't get to se

Re: [rspec-users] What does a skilled BDD-/RSpec-er want in a job?

I know a while back Google used to request python skills when they were hiring java folks. They didn't actually need python to do their job - it just meant they attracted the kind of developers who venture outside their regular programming world, which is what they were really after. Mind you they