Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Talk proposal: We buried fixtures too soon #68

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
# We buried fixtures too soon (aka fixtures on steroids)

Nothing is certain but death and taxes... and that we need data in our tests at some point. How to get it? Rails has a built in mechanism for populating database for tests called fixtures. We all know it, but don't use it... because ZOMG FACTORIES ARE BETTER, FIXTURES ARE DEAD! Is it so simple? Have you ever seen a project suffering from "Factories Madness"? Maybe.... fixtures are not dead after all? (Otherwise we are freaking necromancers!)

In this talk we will be like Sherlock and Watson tracking the roots of one of the most spectacular mistakes in rails history. And we will present a cure (and no, the cure is not "more cowbell"). Beware!

We played a little game called "be like Frankenstein". We took fixtures and using them created new creature, which is almost perfect now*. We called it "fixtures on steroids" (till somebody finds some more catchy fancy name) and successfully use it in our projects!

*Ok, You got me here, maybe it is not perfect, but we managed to eliminate most fixtures defects.

Also, if this talk is approved, you may witness (probably) first talk in ruby community presented by twin brothers. Isn't it awesome?

## Piotr Sarnacki

Ruby and rails programmer from Poland, [Rails core commiter](http://contributors.rubyonrails.org/contributors/piotr-sarnacki/commits), open source enthusiast.

![Profile picture](https://github.com/drogus/call-for-proposals/raw/master/Piotr_Sarnacki_and_Lukas_Sarnacki-We_burried_fixtures_too_soon/drogus.png)

- [Twitter](https://twitter.com/#!/drogus)
- [Github](http://github.com/drogus)
- [Past talk slides: Going beyond ruby](http://going-beyond-mvc-moscow.heroku.com)
- [Past talk slides: Rails - past, present, future](http://rails-present-past-future.heroku.com)
- [Past talk video: Everything you wanted to know about HTTP](http://blip.tv/rupy-strongly-dynamic-conference/piotr-sarnacki-everything-you-wanted-to-know-about-http-5949137)
- [Past talk video: Rails 3 mountable apps](http://confreaks.com/videos/436-rubyconf2010-ruby-summer-of-code-rails-3-mountable-apps)

## Evil Twin Brother (Lukas Sarnacki)

When not working for polish startup called Stoliczku.pl I sabotage Peter's work with some heisen bugs and other evil stuff.
Besides being passionate about Ruby on Rails (which is obvius, duh!) I love working with UI.

![Profile picture](https://github.com/drogus/call-for-proposals/raw/master/Piotr_Sarnacki_and_Lukas_Sarnacki-We_burried_fixtures_too_soon/lukas.jpg)

- [Github](https://github.com/lukesarnacki)
- [Twitter](http://twitter.com/lukesarnacki)
- [UseTheAwesomenessLuke.com](http://usetheawesomenessluke.com/) (yes, I know there is only one crappy note there, but maybe my shame will motivate me to write some more)

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.