When using FactoryGirl
to create records in tests, it is necessary to be aware that you are usually creating a lot more
records than is obvious in the code. While this is usually harmless aside from slowing down tests, it is capable of creating
some mind boggling flakiness. Some scenarios where this is probable are tests that count the number of records, tests that are
expecting a certain record and assume that only it exists. Improperly set model level validations can also contribute to this.
by Jay Baxter (circa 2009)
"This list is for people who want to become Associate Software Engineers at Blizzard. An associate should have skills at the level indicated by these books. Note that this is almost completely focused on C++ programming. This list is incomplete. I need a book on how to become a professional. I've listed several books that give examples of professional behavior, but not one on the actual training."
by Bjarne Stroustrup
- Twitter: @darkofabijan
- Company: Rendered Text - http://renderedtext.com / Semaphore - https://semaphoreapp.com
I am developer and cofounder of Rendered Text, a company that you might know by Semaphore, hosted continuous integration service. I have been working with Rails since 2008, and got pushed into distributed systems arena while trying solve problems of fault-tolerant nodes, realtime updates and fast multi-node deployments that we were facing on Semaphore. While exploring distributed systems I discovered Elixir and joined the Phoenix core team.
class User < ActiveRecord::Base | |
def forms | |
Form.where(:company => company) | |
end | |
def find_form(id) | |
forms.find(id) | |
end | |
end |
class User < ActiveRecord::Base | |
def find_form(id) | |
company.forms.find(id) | |
end | |
end |
Factory.define :application do |factory| | |
factory.attachment(:sample, "public/samples/sample.doc", "application/msword") | |
end |