1. No more before_filter

undefined method 'before_filter' before_filter has been deprecated in Rails 5.0 and removed in 5.1.

2. halt_callback_chains_on_return_false is deprecated

ActiveSupport.halt_callback_chains_on_return_false= is deprecated and will be removed in Rails 5.2.

3. Passing a class to the class_name is deprecated

Passing a class to the 'class_name' is deprecated and will raise an ArgumentError in Rails 5.2.
It eagerloads more classes than necessary and potentially creates circular dependencies. Please pass the class name as a string:

This warning message was due to passing a class to `class_name` option when specifying associations – this is no longer recommended‘

- has_one :contact, class_name: UserContact
+ has_one :contact, class_name: 'UserContact

Whats new in Spree 3.3

Rails 5.1 support

Ruby 2.4 support

Segment tracker integration

Bug fixes and performance enhancements

Whats next?

group :development, :test do
  gem "jasmine"
end

bundle install

rails generate jasmine:install

Run tests

1. In your browser
2. Continuous Integration Mode (CI)

Browser Mode

rake jasmine

http://localhost:8888/

rails generate jasmine:examples

Configurable Settings

Raise Exceptions

Stop Spec on Expectation Failure

Run Tests in Random Order

Continous Integration Mode

rake jasmine:ci

Jasmine.configure do |config|
   config.ci_port = 1234
end

Configuration

• jasmine.yml
• jasmine_helper.rb

Sample configuration:

# spec/javascripts/support/jasmine.yml
random: true
show_console_log: false
stop_spec_on_expectation_failure: true

# spec/javascripts/support/jasmine_helper.rb
Jasmine.configure do |config|
  config.random = false
  config.show_console_log = false
  config.stop_spec_on_expectation_failure: false
  config.show_full_stack_trace = false
  config.prevent_phantom_js_auto_install = false
end

Testing

Testing JavaScript

Plugins worth considering

• Jasmine-Jquery – this plugin provides a lot of jquery related matchers. Download it here
• Jasmine-Matchers – a tool to provide additional matchers. Download it here
• Jasmine-Fixture – a plugin that provides DOM creation using CSS selectors, therefore you can interact with the DOM much easier. Download it here

Write Beautiful Unit tests

Importance of Test Discipline

• Writing tests first gives you a clearer perspective on the ideal API design.
• Does the developer understand the problem enough to articulate in code all critical component requirements?
• Manual QA is error-prone. In my experience, it’s impossible for a developer to remember all features that need testing after making a change to refactor, add new features, or remove features.
• Continous Integration prevents failed builds from getting deployed to production.

Bug Report vs plain Unit Test

• What are you trying to test?
• What should it do?
• What is the real-time output (actual behavior)?
• What is the expected output (expected behavior)?

describe("CalculatorAddMethod", function() {
  var calculator = new Calculator();
  it("should return number", function() {
    const actual = typeof Calculator.add(5,10);
    const expected = 'number'
    expect(actual).toEqual(expected);
  });
});

• What are you trying to test?
  • -> Go for the test description. It is testing for the return type of the add method of Calculator().
• What should it do?
  • -> Again, look at the test description. It clearly says that it is testing for the return type of add method.
• What is the actual output?
  • -> There is a dedicated variable which holds the actual result and how you got the actual result. TWO FOR ONE!
• What is the expected output?
  • -> Again, there is a dedicated variable which holds the actual result. Straight as a ruler!

Make your tests even better

Easter Egg

Conclusion

• What are you trying to test?
• What should it do?
• What is the real-time output (actual behavior)?
• What is the expected output (expected behavior)?
• How can be the test reproduced?

• Authentication: Checks whether the login details are correct or not when the request arrives.
• Authorization:  It performs role-based security. i.e. checks whether the user is authorized to perform the particular task.
• Caching: Return a cached result if the request is already processed.
• Decoration: Enhance the request to make downstream processing better.
• Performance & Usage Monitoring: Status get from the request and response.
• Execution: actually handle the request and provide a response.

Building your own Rack middleware

use Rack::Lint # gives more descriptive error messages when responses aren't valid
class Example
  def initialize(app)
    @app = app
  end
  def call(env)
    status, headers, body = @app.call(env)
    body.map { |msg| p "Example: #{msg}" }
    [status, headers, body]
  end
end
use Example # Does nothing with uppercase'd response, just logs it to stdout
run -> env {[200, {"Content-Type" => "text/html"}, ["<h1>Hello Redpanthers</h1>"]]}

Finally, run the server with rackup. It will find config.ru and boot up on the specified port.

$ rackup -s Puma -p 9293
Puma starting in single mode...
Version 3.6.2 (ruby 2.3.1-p112), codename: Sleepy Sunday Serenity
Min threads: 5, max threads: 5
Environment: development
Listening on tcp://localhost:9293
Use Ctrl-C to stop
"Example: <h1>Hello Redpanthers</h1>"
127.0.0.1 - - [05/Jan/2017:17:48:43 +0530] "GET / HTTP/1.1" 200 - 0.0035
"Example: <h1>Hello Redpanthers</h1>"
127.0.0.1 - - [05/Jan/2017:17:48:43 +0530] "GET /favicon.ico HTTP/1.1" 200 - 0.0022

Adding it to Rails

config.middleware.use Example

• config.middleware.use(new_middleware, args) – Adds the new middleware at the bottom of the middleware stack.

• config.middleware.insert_before(existing_middleware, new_middleware, args) – Adds the new middleware before the specified existing middleware in the middleware stack.

• config.middleware.insert_after(existing_middleware, new_middleware, args) – Adds the new middleware after the specified existing middleware in the middleware stack.

config.middleware.insert_before Rails::Rack::Lint, Example
config.middleware.insert_after Rails::Rack::Lint, Example

 References

1. https://www.amberbit.com/blog/2011/07/13/introduction-to-rack-middleware/
2. http://www.integralist.co.uk/posts/rack-middleware.html
3. http://ieftimov.com/writing-rack-middleware
4. https://blog.engineyard.com/2015/understanding-rack-apps-and-middleware
5. http://www.cise.ufl.edu/research/ParallelPatterns/PatternLanguage/AlgorithmStructure/Pipeline.htm

• Storing data in JSON and JSONB format
• Generating JSON results from the query itself

Getting Started

How to generate JSON

select row_to_json(users) from users where id = 1;

{"id":1,"email":"hsps@redpanthers.co","encrypted_password":"iwillbecrazytodisplaythat",
"reset_password_token":null,"reset_password_sent_at":null,
"remember_created_at":"2016-11-06T08:39:47.983222",
"sign_in_count":11,"current_sign_in_at":"2016-11-18T11:47:01.946542",
"last_sign_in_at":"2016-11-16T20:46:31.110257",
"current_sign_in_ip":"::1","last_sign_in_ip":"::1",
"created_at":"2016-11-06T08:38:46.193417",
"updated_at":"2016-11-18T11:47:01.956152",
"first_name":"Super","last_name":"Admin","role":3}

select row_to_json(results)
from (
  select id, email from users
) as results

{"id":1,"email":"hsps@redpanthers.co"}

select row_to_json(result)
from (
  select id, email,
    (
      select array_to_json(array_agg(row_to_json(user_projects)))
      from (
        select id, name
        from projects
        where user_id=users.id
        order by created_at asc
      ) user_projects
    ) as projects
  from users
  where id = 1
) result

{"id":1,"email":"hsps@redpanthers.co", "project":["id": 3, "name": "CSnipp"]}

array_to_json(array_agg(row_to_json(user_projects)))

json_agg(user_projects)

json_build_object('foo',1,'bar',2)

{"foo": 1, "bar": 2}

References

require 'irb'
# all the codes before the binding
binding.irb
# all the codes after the binding

match 'profiles', to: 'users#index', via: 'get'

match 'profiles', to: 'users#index', via: 'get'
get 'profiles', to: 'users#index', via: 'get'
resources :users
resource :users, path: 'profiles'

  resources :saved_filters
  match "/404" => "errors#error404", via: [ :get, :post, :patch, :delete ], as: 'error404'
  devise_for :saas_admins
  mount RailsAdmin::Engine => '/saas_admin', :as => 'rails_admin'
  %w(about privacy benefits compliance onboarding payroll time_off terms contact aca-compliance).each do |page|
    get page => "content##{page.underscore}"
  end
  get "/not_authorized", to: 'errors#not_authorized'
  post '/broker_sign_in_path', to: 'application#broker_sign_in_domain', as: 'broker_sign_in_domain'
  post '/employer_sign_in_path', to: 'application#employer_sign_in_domain', as: 'employer_sign_in_domain'
  post '/messages/reply_from_external_user',to: 'messages#reply_from_external_user',as: '/messages/reply_from_external_user'
  # Routes for the public site

resources :users

resource :users, only: [:create, :update, :show, :destroy]

resources :posts do
  resources :comments
end

resources :users do
  member do
    match 'de_activate', to: 'user#de_activate', via: 'get'
  end
  collection do
    match 'search', to: 'user#search', via: 'post'
  end
end

module NewFeature
  def to_do_something
    puts "I am doing something new which Active Record coudln't do before"
  end
end
ActiveRecord::Base.include(NewFeature)

after_create do
  Rails.logger.info "[DataEntry] A new record has been created"
end

CREATE INDEX index_name
ON prices (user_id);

add_index :prices, :user_id

CREATE INDEX index_name
ON user_views (user_id, article_id);

add_index :user_views, [:user_id, :article_id]

scope :articles, where(:spam => 'true')

CREATE INDEX index_name
on articles (spam is true);

add_index :articles, :spam, name: "index_articles_on_spam", where: "(spam IS true)"

DROP INDEX index_name;

remove_index :books, :created_at

• Index Primary key
• Index Foreign key
• Index all columns you would be passing into where clause
• Index the keys used to Join tables
• Index the date column (if you are going to call it frequent, like rankings of a particular date)
• Index the type column in an STI or polymorphism.
• Add partial index to scopes
• Do not index tables with a lot of read, write
• Do not index tables you know that will remain small, all through out its life time
• Do not index columns where you will be manipulating lot of its values.

after_create Is called after Base.save on new objects that haven‘t been saved yet (no record exists) after_save Is called after Base.save (regardless of whether it‘s a create or update save) after_commit Is called after the database transaction is completed.

User.transaction do
    # update company
    # update hr_department
    # update user_table
end