Entrepreneurship: Life Long Learning

Reject Conf

No RSpec

Steven Baker
Why should you use RSpec.
Use RSpec if you want to, if you don’t, don’t.
10 Reasons why you shouldn’t use RSpec

• 10 I was drunk when I wrote It
• 9 Documentation is overratted, because
• 8 Nobody ever flips the arguments to assert_equal
• 7 Runing Testing::Unit provides for a perfect coffee break
• 6 You like evaluating Mock frameworks.
• 5 Tightly couplling your test to production code prevents anyone else from modifying it
• RSpec helps teach BDD
• 4 Testing state satifies the overriding need to micromanage every part of you life.
• 3 The tests are already concide and precisely define some small piece of the software behavior
• 2 Test that don’t read anything like English prevent customers from pointing out glaring errors in business logic.
• 1 Explaing to new memebers of your team that you really can test something that doesn’t exit is a fun
• 0 Nobody needs good stack traces anyways ( RSpecs

Testing implies verification. BDD Implies specification

That Microsoft Gal

• The only reasons you should not buy Vista.
• It has a sucky version of quicksilver.
• Microsoft office Toolbars are gone they are now ribbons.
• Review tab in word, you can translate into foriegn languages, and look up news on companies.
• Microsoft Excel has graphs in individual cells. Excel has ODBC data sources.
• Vista has Xgl and it has spotlight, and a dock.
• Microsoft help can help your parents.

RSpec in unittest

• I’m married to rails so I desided to embed RSpec into TestUnit and I support nested contexts.
• RSpec SVN has nested contexts. Tear downs run from the inside out.
• assert_kind_of gets blown-up into a full blown test or spec.
• These can be put into a module and the module can be included in multiple contexts where the same behavior
• Spec-unit.rubyforge.net it has
• SimplyBDD
• This is namespace safe and wont crash if the context is empty.

OS X Windows and RoR monkey patches

• Resizes windows when you go from a big window at work to a smaller monitor at home.
• Redirect emails during testing and stops leaking of emails during development.
• chunky
• array to hash, other things besides hash should have a to_hash
• “maybe”.one_of “yes”, “no” returns “yes”

Eric Hodel

• Refactor Your Tests
• Add assertions
• assert_empty
• assert_tag
• Fake URL Open, easier than mock and flack mock. Many mock frameworks are overkill.

Aaron Bedra

• rock_solid_rails
• rake rock_solid_rails deploy
• I now have have a rails app
• It will be a post deploy hook for capistano.

Charles Nutter

• Sun and JRuby
• Showed constructing a JFrame and a button in the frame from IRB.
• Inplace ruby variable rename refactoring in netbeans.
• Java readline library can be used in Ruby.

Tom Werner

• Chronic
• Uses Ranges of posibilities and then uses matches to associated parsed natural language tokens.
• There is Perl
• look at the Remind command programline
• chronic.rubyforge.org

Ryan Davis

• Heckle?
• Jester Java bytecode manipulator for test verification.
• Modifies the code under test changing branching logic return values etc.
• Turns ifs into unlesses, a form of fuzzing for code.

Extremely halarious StarTrek parody based on Ruby, Python, and Smalltalk

GRATR

• Graph algorithms on rubyforge.
• Supports dotty (graphviz)
• gratr.rubyforge.org port/fork of tgl

Rameau

• Vaporware for this holiday season.
• Literate Programing compendiums
• Ruby needs a better mathematical number crunching support.
• ATLAS and FFTW
• FFTW has ruby bindings,
• ATLAS does not bindings.

OpenID

• Early cross site and single site sign-on
• What is ID?
• What is Digital ID?
• Current use case, Submit User name, password, email address, verify reciept of email, wash, rinse, repeat.

This entry was posted on Sunday, October 22nd, 2006 at 8:04 am and is filed under Lecture/Talk Notes, Ruby. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.