It’s been too hard to deal with file uploads in Rails. There’s been a lot of fine plugins available, but it was overdue that we incorporated something right into the framework. Finally, we have one, in the form of Active Storage. This release includes Active Storage, a new framework provided by Rails to make it easier to upload and process files. With this new framework, we’ve solved for the modern approach of uploading files straight to the cloud. Out of the box, there’s support for Amazon’s S3, Google’s Cloud Storage, and Microsoft Azure Cloud File Storage. If you’re dealing with images, you can create variants on the fly. If you’re dealing with videos or PDFs, you can create previews on the fly. And regardless of the type, you can analyze uploads for metadata extraction asynchronously. This framework is not only used in production, but it is born for production.

There’s a sparkling new Redis Cache Storage that incorporates general partial, fragment, and other Rails caching jobs into a cohesive unit that anyone can use.

Rails 5.2.0 has Added support for PostgreSQL operator classes to add_index. The operator classes identify database operators to be used by the index for the columns. You can assign the same operator to all columns, or not. It currently only supports PostgreSQL.

Added ability to create PostgreSQL foreign keys without validation. Normally, PostgreSQL verifies that all rows in a table satisfy its foreign keys constraints. With this option, you can create these constraints without the overhead of checking if they are valid.

Rails 5.2.0 also has embraced the cherry of HTTP/2 with early hints. This means we can automatically instruct the web server to send required style sheet and JavaScript assets early. This means a faster page delivery.

On the topic of performance, Rails now ships with Bootsnap in the default Gemfile. This generally reduces application boot times by over 50%.

 CSRF and XSS have enhanced that further in Rails 5.2 with the addition of a new DSL that allows you to configure a Content Security Policy for your application. We can configure a global default policy and then override it on a per-resource basis and even use lambdas to inject per-request values into the header such as account subdomains in a multi-tenant application.

In Rails 5.2, we’ve rectified the mess by deprecating the two different kinds of secrets and introduced a new shared concept called Credentials. Credentials, like AWS access keys and other forms of logins and passwords, were the dominant use case for secrets. Credentials are always encrypted. This means they’re safe to check into revision control, as long as you keep the key out of it. This means atomic deploys and there is no need to mess with environment variables.

Since Rails 5.1, we’ve also made great strides with Webpacker. So Rails 5.2 is meant to pair beautifully with the new Webpacker 3.0 release. Rails have fully embraced modern JavaScript with a pre-configured build pipeline run by Webpack. We keep strengthening that relationship.

Thanks again to everyone who continue to pour their love and support into Ruby on Rails! Happy Coding.

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?

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