Feature | [Automation workshop] Add URL, Path helpers (#210)

* Add Routes, credentials, rest

* Practice rep add

* Change RSpec slides

* Add URL and Path helpers slides

* Fixed repositories

* Change ruby version

* Add Circle, rubocop and change capybara slides

Author: alexyndr

index.markdown

@@ -50,6 +50,9 @@ title: Ruby presentations
   <br>
   <small>Learn how to do refactoring in Ruby.</small> -->
 
+- [Refactoring](/slides/refactoring-ruby)
+  <br>
+  <small>Clean code is code that is easy to read, understand and maintain. </small>
 
 - [Rack](/slides/rack)
   <br>

slides/automation-qa/capybara.markdown

@@ -30,6 +30,7 @@ The first thing we need to do is add our gem to Gemfile in `:test` group
 group :test do
   gem "capybara"
   gem "rspec-rails"
+  gem "selenium-webdriver" # in order to use Selenium
 end
 ```
 
@@ -106,6 +107,12 @@ spec/feature/test_spec.rb <!-- .element: class="filename" -->
 visit('/') # Capybara will visit `http://www.google.com`
 ```
 
+--
+
+## Launch different browsers
+
+
+
 ---
 
 # Drivers
@@ -236,7 +243,7 @@ all('a', text: 'Home')
 all('a#person_123')
 ```
 
-More about different types of finder you can find [here](https://rubydoc.info/github/teamcapybara/capybara/master/Capybara/Node/Finders)
+More about different types of finder you can find [here](https://rubydoc.info/github/teamcapybara/capybara/master/Capybara/Node/Finders) and [here](https://gist.github.com/tomas-stefano/6652111)
 
 --
 
@@ -267,8 +274,6 @@ When you trying to find an element, it is common to have two or more matches whi
 Capybara comes with a very intuitive DSL which is used to express actions that will be executed. This is the list of basic command that are used
 
 ```ruby
-visit('page_url') # navigate to page
-
 click_link('id_of_link') # click link by id
 click_link('link_name') # click link by link text
 click_button('button_text') # click button by button text
@@ -296,6 +301,35 @@ end
 
 --
 
+## `Visit`
+
+Visit method allows you navigate to the given [**URL**](https://rubygarage.github.io/slides/qa-automation/rails-structure#/9/5) or [**Path**](https://rubygarage.github.io/slides/qa-automation/rails-structure#/9/5) Helpers
+
+```ruby
+visit("/users")   # navigate to page with users through URL
+
+visit(users_path) # navigate to page with users through Path
+
+# In both cases we will visit page with users (https://your_facebook/users)
+```
+
+Also you can provide params for visit method
+
+```bash
+user.id
+=> 1
+```
+
+```ruby
+visit("/users/#{user}")  # navigate to page with user through URL
+
+visit(user_path(user))   # navigate to page with user through Path
+
+# In both cases we will visit page with user_id = 1 (https://your_facebook/users/1)
+```
+
+--
+
 ### Advanced `DSL`
 
 For scenarios where basic the DSL cannot help, we use xpath and CSS selectors (CSS selectors will be used by default). This is very common, since modern web applications usually have a lot of JavaScript code that generates HTML elements with attributes that have generated values (like random ids, etc.)
@@ -339,6 +373,12 @@ expect(page).to have_selector(:xpath, './/table/tr')
 expect(page).to have_xpath('.//table/tr')
 expect(page).to have_css('table tr.foo')
 expect(page).to have_content('foo')
+expect(page).to have_no_content('foo')
+expect(page).to have_current_path(your_path)
+expect(page).to have_link("Foo", :href=>"googl.com")
+expect(page).to have_no_link("Foo", :href=>"google.com")
+expect(page).to have_field('#field')
+expect(page).to have_button('#submit')
 ```
 
 ---
@@ -365,4 +405,29 @@ Finally, in drivers that support it, you can save a screenshot:
 save_and_open_screenshot
 ```
 
-Screenshots are saved to `Capybara.save_path`, relative to the app directory. If you have required `capybara/rails`, `Capybara.save_path` will default to `tmp/capybara`.
+Screenshots are saved to `Capybara.save_path`, relative to the app directory. If you have required `capybara/rails`, `Capybara.save_path` will default to `tmp/capybara`.
+
+--
+
+## Again `Pry`
+
+You can remember what is pry [here](http://localhost:4000/slides/automation-qa/rails-structure#/12/1)
+
+Remember you should place `binding.pry` inside `it` block.
+
+spec/features/hello_world_spec.rb <!-- .element: class="filename" -->
+
+```ruby
+describe 'Your page', type: :feature do
+
+  before do
+    visit(your_page_path)
+  end
+
+  it 'Say hello' do
+    click_button('Hello World')
+    binding.pry
+    expect(page).to have_content('Hello!')
+  end
+end
+```

slides/automation-qa/factory-bot.markdown

@@ -19,7 +19,7 @@ group :test do
 end
 ```
 
-Then, run `bundle` to download and instal new gem
+Then, run `bundle install` to download and instal new gem
 
 ```bash
 $ bundle install

slides/automation-qa/index.markdown

@@ -40,4 +40,12 @@ title: QA Automation
 
 - [SimpleCov](simple-cov)
   <br>
-  <small>How to check coverage in RSpec? What is SimpleCov? </small>
+  <small>How to check coverage in RSpec? What is SimpleCov? </small>
+
+- [Rubocop](rubocop)
+  <br>
+  <small>What is Rubocop? How it use? </small>
+
+- [CircleCI](../circleci)
+  <br>
+  <small>CircleCI is Continuous Integration, for testing apps, which is fast, functional and flexible. </small>