How do YOU do integration/functional testing?

[Robert Stevenson]

I saw Gary tweet this and I'm curious to do a quick survey of the group to see what folks use for integration testing (or if you don't do it at all, etc.)?  -Rob



https://twitter.com/#!/garybernhardt/status/180038423845933056

[Jon Canady]

I'm trying to do more rspec/capybara. Cucumber never really clicked for me -- I understand the syntax, but the whole "write a story in Gherkin, then write a regex to translate it into running code" always struck me as too much work.

Although I do more unit/view testing than I do integration testing. I don't know if that's "better", it's just how I do.

--Jon C.

--
You received this message because you are subscribed to the Google Groups "Columbus Ruby Brigade" group.
To post to this group, send email to colum...@googlegroups.com.
To unsubscribe from this group, send email to columbusrb+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/columbusrb?hl=en.

[Robert Stevenson]

Hmm ... my screengrab didn't make it through. Here it is (attached, hopefully), just to save some link clicking ...

[Jonathan Hogue]

In order to save some link clicking

As a message sender

I would like to paste screengrabs into a message

[David Fisher]

Now run it and watch it fail...

[Jon Kruger]

I think it depends on the project. I've worked on web apps where it
was 98% unit tests and a few integration tests. On my current project
(back end rules engine/transaction processing), we use mostly
acceptance tests written in the gherkin format and automated using
SpecFlow (.NET Cucumber). SpecFlow works better for us because much
of our app is configurable, and unit tests won't test the
configuration.

Regardless of what tools you use, I think the important thing is to
write tests first so that you can think through what you're building
before you build it. I think the gherkin syntax lends itself to that
quite well, but you can do the same thing with rspec too. I
personally prefer the cucumber format for writing tests, but I know a
lot of people that prefer rspec instead. So I think it's a matter of
preference, there are multiple ways to succeed.

On Mar 15, 5:18 pm, Jon Canady <j...@joncanady.com> wrote:
> I'm trying to do more rspec/capybara. Cucumber never really clicked for me
> -- I understand the syntax, but the whole "write a story in Gherkin, then
> write a regex to translate it into running code" always struck me as too
> much work.
>
> Although I do more unit/view testing than I do integration testing. I don't
> know if that's "better", it's just how I do.
>
> --Jon C.
>
> On Thu, Mar 15, 2012 at 17:14, Robert Stevenson

> <robert.steven...@gmail.com>wrote:

>
>
>
>
>
>
>
> > I saw Gary tweet this and I'm curious to do a quick survey of the group to
> > see what folks use for integration testing (or if you don't do it at all,
> > etc.)?  -Rob
>

[Changpil]

Tethbbvt

Jon Canady <j...@joncanady.com> wrote:

>I'm trying to do more rspec/capybara. Cucumber never really clicked for me
>-- I understand the syntax, but the whole "write a story in Gherkin, then
>write a regex to translate it into running code" always struck me as too
>much work.
>
>Although I do more unit/view testing than I do integration testing. I don't
>know if that's "better", it's just how I do.
>
>--Jon C.
>
>On Thu, Mar 15, 2012 at 17:14, Robert Stevenson

><robert.s...@gmail.com>wrote:

[Len Jaffe]

On Fri, Mar 16, 2012 at 1:32 PM, Changpil <chan...@gmail.com> wrote:

Tethbbvt

Bill the Cat says he likes Test::Unit. 

--
lenj...@jaffesystems.com   614-404-4214
Proprietor: http://www.theycomewithcheese.com/ - An Homage to Fromage

Greenbar: Grubmaster: 2012, 2011, 2010, 2009, Grub Asst: 2008, Trained: 2007.

[Chris Nelson]

I wasn't really sold on cukes until I worked with a client where they actually had written cukes for us when started the gig.  It was a huge win and got me hooked.  The key for me is having a client/product owner that cares enough to read them (or better yet collaborate on producing them).  If it's just for developers I'm not as convinced.

--Chris

--

[Jonathan Hogue]

We aren't even writing the automated tests behind them, and seeing big wins. It gets the clients to start thinking about the app. A lot of times, they just want to hand it over the wall to the technology guy, and these stories help them realize they can't just do that. Also, it's in their language, so it's not an invite for them to start designing the app, because they're probably not going to be very good at that. 

It's cool to know that we could automate the tests if we wanted to.