| class NestedAttributesForStrategy | |
| def association(runner) | |
| runner.run | |
| end | |
| def result(evaluation) | |
| evaluation.object.tap do |instance| | |
| evaluation.notify(:after_build, instance) | |
| return attributes(instance) | |
| end |
| # This is a skeleton for testing models including examples of validations, callbacks, | |
| # scopes, instance & class methods, associations, and more. | |
| # Pick and choose what you want, as all models don't NEED to be tested at this depth. | |
| # | |
| # I'm always eager to hear new tips & suggestions as I'm still new to testing, | |
| # so if you have any, please share! | |
| # | |
| # @kyletcarlson | |
| # | |
| # This skeleton also assumes you're using the following gems: |
| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
| if has("autocmd") | |
| " remove trailing white spaces | |
| autocmd BufWritePre * :%s/\s\+$//e | |
| endif |
its isn't core to RSpec. One the of the focuses of RSpec is on the documentation aspects of tests. Unfortunately, its often leads to documentation output that is essentially lies. Consider this spec:
User = Struct.new(:name, :email)
describe User do
subject { User.new("bob") }
its(:name) { should == "bob" }
end
| 1. Enable git templates: | |
| git config --global init.templatedir '~/.git-templates' | |
| This tells git to copy everything in ~/.git-templates to your per-project .git/ directory when you run git init | |
| 2. Create a directory to hold the global hooks: | |
| mkdir -p ~/.git-templates/hooks | |
| 3. Write your hooks in ~/.git-templates/hooks | |
| 4. Make sure the hook is executable. |
This list is based on aliases_spec.rb.
You can see also Module: RSpec::Matchers API.
| matcher | aliased to | description |
|---|---|---|
| a_truthy_value | be_truthy | a truthy value |
| a_falsey_value | be_falsey | a falsey value |
| be_falsy | be_falsey | be falsy |
| a_falsy_value | be_falsey | a falsy value |
Dear Rubyists,
I just lost a contract because of my code in a Rails project.
The specific code in question is related to a "posting a comment" feature. Here are the details:
In this project, "posting a comment" does not simply entail inserting a row into the database. It involves a procedure to yes, insert a row, but also detect its language, check for spam, send emails, and "share" it to Twitter and Facebook. I believe this algorithm should be encapsulated. I do not believe it belongs in a controller or a model. I do not believe Active Record callbacks should be used.
The "senior developer", whom is the stake holder's right hand man, said this:
| # RSpec matcher for validates_with. | |
| # https://gist.github.com/2032846 | |
| # Usage: | |
| # | |
| # describe User do | |
| # it { should validate_with CustomValidator } | |
| # end | |
| RSpec::Matchers.define :validate_with do |expected_validator, options| | |
| match do |subject| | |
| @validator = subject.class.validators.find do |validator| |
| Call: | |
| Set custom options: | |
| = link_to talk, method: :delete, class: 'icon-close', data: {confirm: "Вы действительно хотите удалить всю переписку с данным пользователем?", confirm_options: {title: 'Удалить все сообщения', yes: 'Да', no: 'Нифига'}}, remote: true | |
| or standart rails way | |
| = link_to talk, method: :delete, class: 'icon-close', data: {confirm: "Вы действительно хотите удалить всю переписку с данным пользователем?"}, remote: true |