ruby VS ferrum

I use https://exercism.org/ for learning elixir and it is a great tool to start IMO. It has a track for Ruby here: https://exercism.org/tracks/ruby

Once you’re done with the odin project and want to continue learning ruby, I suggest checking out Exercism ruby track too. There is a learning track, exercises are increasing in difficulty, and you get free mentoring from Rubyists on there too.

Exercism for Ruby practice.

If you want to improve your grasp of Ruby, try The Well-Grounded Rubyist and (as someone else mentioned) Exercism.

When I was first learning Ruby, I also loved Exercism for practice.

Exercism for Ruby practice.

Ruby: - The Well-Grounded Rubyist. It covers some advanced Ruby, so it's worthwhile even if you already know some Ruby. - Exercism for Ruby practice.

For getting an overview of Ruby and Rails in two weeks, here's what I would recommend: - Watch the free Rails for Beginners videos by GoRails, and code along with them if you're so inclined. - Do some exercises on Exercism, and after each exercise be sure to look at the top solutions by other people. Use The Odin Project or your favorite Ruby tutorial as a reference for the language.

Also, the Ruby track on Exercism is great for practice.

What are you using for automation? There's a relatively new gem that I heard good things of, vessel: https://github.com/rubycdp/vessel . It uses ferrum under the hood, a set of Ruby bindings to Chrome/Chromium (https://github.com/rubycdp/ferrum).

I've used https://github.com/rubycdp/ferrum as driver for automated testing with capybara for which it works great. It recommends https://github.com/rubycdp/vessel as higher level abstraction for web scraping.

require "Rubygems" require "Ferrum" def generate_card(browser, card, png, options={}) browser.go_to("http://localhost:4000/cards/#{card}") # see all the options here https://github.com/rubycdp/ferrum#screenshots browser.screenshot(path: "./images/cards/#{png}", full: true, # final image size is window_size x scale scale: 2) end browser = Ferrum::Browser.new(window_size: [800, 418]) # Check what cards we need to make Dir.glob("_posts/*").each do |post| post = File.basename(post, ".md") png = post + ".png" card = post + ".html" generate_card(browser, card, png) unless File.exists?("./images/cards/#{png}") end

That is why we were happy to find out that a new ruby testing driver approach is being developed. It is called Cuprite, it runs the Ferrum library under the hood which, in turn, is an API that directly instruments the Chrome browser using the Chrome DevTools Protocol (CDP). About a week ago, we finally made a serious attempt to make our system test suite run on Cuprite, with especially two questions in our minds:

I've used Ferrum for a couple small scripts in the past before.

Ferrum